Sign in
Home/PMI/PMI Professional in Business Analysis (PMI-PBA)/Free questions

PMI Professional in Business Analysis (PMI-PBA) — Free Practice Questions

10 free sample questions from a bank of 156, with the correct answers and explanations. No signup required — start practising right now.

1A business analyst is developing a traceability matrix to determine whether or not any gaps exist and to identify any discrepancies. Which critical field is needed to ensure that the traceability matrix is usable?
PMI Professional in Business Analysis (PMI-PBA) question 1
  • Hierarchy
  • Requirements description
  • Status
  • Owner
Answer: B

The short version

B — Requirements description makes the traceability matrix usable. Without a clear statement of what each requirement means, the matrix is only a list of IDs that cannot reveal gaps or conflicts. The description gives every traced link a testable meaning.

Key concepts in this question

  • Requirements traceability matrix: a table linking each requirement to its source, design, build and test coverage so gaps and orphans become visible.
  • Requirements description: the plain statement of what is required, including constraints and intent, that lets a reader judge coverage.
  • Gap and discrepancy analysis: comparing required coverage against actual links to find missing, duplicate or inconsistent items.
  • Auxiliary attributes: owner, status and hierarchy help manage work, but they do not define what must be satisfied.

Why B is correct

The purpose in the stem is to determine gaps and discrepancies, which requires understanding the substance of every row. The description supplies the context needed to tell whether two linked items truly satisfy each other or only appear linked. Source, target and type fields locate a requirement, yet only the description lets the analyst judge completeness and correctness. PMI business analysis practice therefore treats the description as the critical usability field.

Why the others are wrong

  • A. Hierarchy shows parent-child structure but says nothing about what each item requires, so gaps stay hidden.
  • C. Status shows progress such as proposed or approved, yet a status value cannot explain intent or coverage.
  • D. Owner shows accountability for an item, but knowing who owns it does not make the matrix interpretable.

PMI-PBA exam tip

If the stem asks what makes a matrix usable for gap analysis, look for the field that states meaning: description beats status, owner and hierarchy every time.

2A company is developing a new e-commerce platform to enter a new market segment. Development is well under way when the government issues a new set of regulations. Which course of action should the business analyst take?
  • Check the traceability matrix to identify affected use cases.
  • Evaluate if the new set of regulations is aligned with the business case.
  • Evaluate the impact of the change on the project schedule.
  • Obtain management sign-off on the new set of regulations.
Answer: B

The short version

B — New regulations must first be checked against the business case. A mid-build regulatory change can alter viability, market scope, cost and benefits, so alignment comes before detailed impact work. Only after the business case still holds does detailed replanning make sense.

Key concepts in this question

  • Business case: the justification linking objectives, benefits, costs, risks and constraints that governs go or no-go and direction changes.
  • Regulatory constraint: an externally imposed must-comply condition that can invalidate assumptions about features, data, launch and operating cost.
  • Needs assessment: confirming the problem, opportunity and value proposition before committing further build effort.
  • Trace and schedule analysis: useful downstream steps once continued viability and strategic fit are confirmed.

Why B is correct

The e-commerce platform is well under way, so sunk effort tempts the team to jump straight to traceability or schedule fixes. PMI guidance places the business case first when external conditions change, because a regulation can remove the market opportunity, add prohibitive cost or force a pivot. Evaluating alignment protects value, informs sponsors whether entry still makes sense, and scopes all later change work. Traceability, schedule and sign-off follow that decision.

Why the others are wrong

  • A. Checking the traceability matrix finds affected use cases, but that tactical step assumes the venture remains worth pursuing.
  • C. Evaluating schedule impact quantifies delay without asking whether the product should proceed at all.
  • D. Obtaining management sign-off on the regulations confuses acknowledging an external mandate with assessing its business consequence.

PMI-PBA exam tip

When government, law or market shifts mid-project, choose business case alignment before traceability, schedule or sign-off answers.

3The business analysts have concluded a requirements elicitation workshop. They now need to define rationale for each requirement. Which of the following pairs of items would be important to include in the rationale?
  • Reasons and assumptions
  • Functional relationships and work breakdown structure code
  • Product vision and operational relationships
  • Stakeholder impact and design decisions
Answer: A

The short version

A — Reasons and assumptions form the rationale. After elicitation, the analyst must record why each requirement exists and what beliefs underpin it, so future reviewers can judge validity and impact.

Key concepts in this question

  • Requirements rationale: the recorded justification that explains why a requirement is needed and how it connects to business value or stakeholder need.
  • Assumptions: beliefs treated as true for planning that shape requirement content and must be surfaced so they can be validated or retired.
  • Elicitation follow-through: workshops collect raw needs, then analysis turns notes into specified requirements with attributes such as rationale, source and priority.
  • Traceability support: rationale plus source lets change control assess whether a change preserves intent or breaks an assumption.

Why A is correct

A rationale captures reasons and assumptions behind each requirement. Reasons tie it to a goal, driver or stakeholder problem, while assumptions record beliefs accepted during elicitation. Together they let approvers and testers grasp intent, challenge logic and judge changes. PMI guidance treats rationale as a core attribute alongside source, status and priority.

Why the others are wrong

  • B. Functional relationships plus work breakdown structure code describe design linkages and delivery organization, not the justification for a requirement.
  • C. Product vision plus operational relationships describe high level direction and system interactions, not the specific why behind one requirement.
  • D. Stakeholder impact plus design decisions describe consequence analysis and solution choices, which follow rationale rather than constituting it.

PMI-PBA exam tip

When you see rationale, think why plus what we assumed — reasons and assumptions travel together as the memory hook for approval and change review.

4A business analyst has captured all of the requirements from the various stakeholders within the organization and has compiled them into a complete list. After reviewing the list of requirements with the stakeholders, it is determined that the list of requirements is too large and will exceed the allotted budget. Which tool or technique should the business analyst use with the stakeholders to prioritize the requirements to determine which requirements are approved, deferred, or rejected?
  • SMART Goals
  • MoSCoW Analysis
  • SWOT Analysis
  • Timeboxing Analysis
Answer: B

The short version

The list is too large for the budget, so the team must prioritize with stakeholders to decide what is approved, deferred, or rejected, and MoSCoW is the PMI prioritization technique built for exactly that triage.

Key concepts in this question

This question tests Domain 4 traceability and monitoring plus prioritization under constraints like budget, schedule, and value. Approved means funded for now, deferred means valid but moved to a later release, and rejected means formally excluded with rationale.

Why B is correct

B is correct because MoSCoW directly produces the three outcomes asked for by forcing explicit trade-offs with stakeholders. Must-haves enter the baseline, should-haves and could-haves are candidates for deferral if funds run short, and will-not-haves are recorded as rejected or out of scope for now.

Why the others are wrong

A SMART Goals is wrong because specific, measurable, achievable, relevant, and time-bound criteria improve goal clarity but do not rank one requirement against another. A team can write perfect SMART goals and still have an unaffordable list.

PMI-PBA exam tip

When the stem says too many requirements, over budget, or must trim scope, look for a prioritization answer first. Map MoSCoW to must versus should versus could versus will-not-have, weighted ranking to scored criteria, multivoting to stakeholder votes, and time-

5Which tool provides combined functionality for business analysis and quality assurance activities?
  • Functional specification tool
  • Solution quality assurance tool
  • System use case modeling tool
  • Requirements traceability tool
Answer: D

The short version

The tool that bridges business analysis and quality assurance is the requirements traceability tool, so D is the best choice here. It records links among sources, requirements, designs, builds, and tests, then tracks status, changes, and verification through the life cycle.

Key concepts in this question

This question tests tool selection for traceability and monitoring across the life cycle. Business analysis defines, prioritizes, and approves needs, while quality assurance verifies that the built solution satisfies those needs.

Why D is correct

D is correct because only a requirements traceability tool is defined as providing combined functionality for both disciplines. It documents relationships and dependencies among requirements, sources, and deliverables, monitors status and change, and supports analysis, validation, and testing of quality and performa

Why the others are wrong

A Functional specification tool is wrong because it authors and stores specifications well but does not by itself manage QA linkage, test coverage, and change verification across the life cycle. B Solution quality assurance tool is too narrow because it focuses on test execution and defect handling without owning requirements def

PMI-PBA exam tip

When the stem asks for combined BA and QA value, think traceability first. Link source to requirement to design to build to test, then use that chain for impact, coverage, and status questions.

6Company A is working on implementing a new platform with multiple stakeholders. The business analyst has gathered the requirements and established a baseline. However, scope creep is a persistent problem. What could the business analyst have established to help manage this situation?
  • Configuration management system
  • Sponsor signoff
  • Change control process
  • Communication plan
Answer: C

The short version

C — A change control process tames persistent scope creep. Baselines alone freeze scope at a moment, while a governed review and approval path disciplines every later addition. That is the missing capability when creep recurs across many stakeholders.

Key concepts in this question

  • Scope creep: uncontrolled growth of requirements without corresponding adjustment to schedule, budget or quality expectations.
  • Requirements baseline: the approved version of scope that all later changes are measured against.
  • Change control process: submission, impact analysis, decision, communication and baseline update for each proposed change.
  • Configuration management: version and audit discipline for artifacts, which supports but does not judge scope changes.

Why C is correct

The analyst already gathered requirements and baselined them, yet additions keep leaking in from multiple stakeholders. A defined change control process forces each request to be described, analyzed for benefit, cost, risk and dependency, then explicitly approved or rejected by authorized parties. That visibility and governance directly counteracts informal additions. Sponsor sign-off, configuration tools and communications help, but only change control decides what enters scope.

Why the others are wrong

  • A. A configuration management system versions artifacts cleanly, yet it does not evaluate or authorize scope additions.
  • B. Sponsor signoff gives authority at a point in time, but without a repeatable review path creep returns.
  • D. A communication plan spreads information, yet it cannot approve, defer or reject a scope request.

PMI-PBA exam tip

Scope creep after baselining always points to change control process, not to more planning documents or one-time sign-off.

7Which of the following is the best approach to enable developers and product owners to be in constant communication so that changes or issues that occur during development are exposed and discussed as they develop?
  • Iterative
  • Waterfall
  • Agile
  • Linear
Answer: C

The short version

C — Agile keeps developers and product owners in constant communication. Frequent collaboration with rapid feedback exposes changes and issues while work is in progress, rather than at a late handoff.

Key concepts in this question

  • Agile collaboration: product owner embedded with the team, daily interaction, reviews and backlog refinement that surface needs early.
  • Iterative versus Agile: iterative delivers in cycles but can still separate business from builders, while Agile adds continuous business engagement as a principle.
  • Waterfall and linear: sequential phases with gated handoffs that delay feedback until design or build is largely complete.
  • Emergent change: agile assumes requirements evolve, so exposure of issues during development is treated as normal input to reprioritization.

Why C is correct

Agile frameworks explicitly require close, ongoing partnership between business representatives and developers through practices such as daily standups, sprint reviews, demos and continuous backlog grooming. The product owner clarifies intent, reprioritizes and accepts increments, so impediments and scope shifts are discussed as they emerge. That constant loop is why Agile is prescribed when the goal is exposure of changes during development rather than after a phase gate. Iterative alone does not guarantee this business-team intimacy.

Why the others are wrong

  • A. Iterative delivers incrementally but without mandated continuous product owner presence, so communication can still be periodic.
  • B. Waterfall isolates development behind upfront requirements and formal change control, delaying discussion of issues.
  • D. Linear follows a single straight sequence with no feedback loops, the opposite of constant exposure and discussion.

PMI-PBA exam tip

For constant communication plus expose issues as they develop, choose Agile — think owner in the room, not just cycles on a calendar.

8A business analyst is trying to determine which analysis technique will be best suited to elicit information from a large number of users in a short period of time. Which elicitation technique is best suited for this purpose?
  • Group brainstorming
  • Facilitated workshop
  • Ongoing observation
  • Questionnaire
Answer: D

The short version

When you must hear from a very large group quickly, the questionnaire or survey is the right elicitation choice, so D wins. It distributes the same standardized questions to many people at once, collects responses in parallel, and can be analyzed fast.

Key concepts in this question

This question tests elicitation strategy under constraints of volume, time, geography, and availability. Large populations need parallel, asynchronous, and standardized collection with sampling and clear closed or open questions.

Why D is correct

D is correct because a questionnaire can reach many users simultaneously, is cost-effective to administer, allows anonymity that improves honesty, and yields comparable data for prioritization. It avoids scheduling bottlenecks that cripple workshops and observation for large groups.

Why the others are wrong

A Group brainstorming is wrong because it generates ideas well in small interactive groups but cannot efficiently include very large populations in limited time and suffers from dominant voices and logistics. B Facilitated workshop is wrong because it builds consensus deeply but requires co-location or coordination, skilled facilitation, and small enough grou

PMI-PBA exam tip

Memorize elicitation fit rules by constraint. Large plus dispersed plus fast equals survey or questionnaire. Deep plus consensus plus conflict equals facilitated workshop. Creative plus divergent equals brainstorming.

9A type of requirements document that would be the most valuable to a database administrator would be:
  • an object diagram.
  • an entity relationship diagram.
  • a business process diagram.
  • a data flow diagram.
Answer: B

The short version

B — An entity relationship diagram serves the database administrator best. It shows entities, attributes, keys and relationships that directly drive schema design, storage and integrity rules. No other listed model speaks the language of tables and constraints.

Key concepts in this question

  • Entity relationship diagram: entities, attributes, primary and foreign keys plus cardinality that define a relational schema.
  • Object diagram: a snapshot of instances and links at a point in time, useful for object design rather than database structure.
  • Business process diagram: sequence of activities and decisions, silent on tables, keys and normalization.
  • Data flow diagram: movement of data between processes and stores, without key and relationship rigor.

Why B is correct

A database administrator designs, builds, secures and tunes persistent storage, so the decisive artifact is the one that specifies tables, columns, keys and referential rules. The entity relationship diagram provides exactly that blueprint and supports normalization, indexing and integrity decisions. It also becomes the shared contract between analysts, modelers and administrators. The other diagrams aid analysis but do not define the schema.

Why the others are wrong

  • A. An object diagram illustrates specific instances, which helps developers validate behavior rather than design enterprise tables.
  • C. A business process diagram explains workflow order, giving the administrator no entity or key definition.
  • D. A data flow diagram traces inputs and outputs across processes, lacking cardinality, keys and constraints.

PMI-PBA exam tip

When the consumer is a database administrator, pick the entity relationship diagram over process, flow or object views.

10Which of the following is an example of a functional requirement?
  • The system can be accessed from multiple locations.
  • The system can handle 3,000 user requests concurrently.
  • The system provides a user-friendly interface.
  • The system is able to require passwords.
Answer: D

The short version

The only functional requirement listed is the ability to require passwords, so D is correct. Functional needs describe system behavior or capability, what it does, while performance, usability, and access qualities describe how well it does it.

Key concepts in this question

This question tests classification that drives design, testing, and acceptance. Functional requirements state actions, rules, and interactions such as authenticate, calculate, synchronize, or enforce. Nonfunctional requirements constrain performance, scalability, availability, security strength, usability, and portability with measurable thresh

Why D is correct

D is correct because the system is able to require passwords describes a security behavior the system performs, not a measure of speed or ease. It can be verified by attempting access with and without passwords and observing enforcement.

Why the others are wrong

A The system can be accessed from multiple locations is wrong because it constrains portability and availability, a where and how-well quality, not a discrete behavior. B The system can handle 3000 concurrent requests is wrong because throughput under load is the textbook performance NFR, even though it sounds important and

PMI-PBA exam tip

Use the what versus how-well test on every classification question. If you can phrase it as the system shall allow or perform an action, lean functional. If you see numbers for speed, volume, uptime, or vague words like fast, friendly, and accessible, lea

Want the full bank of 156 questions for PMI Professional in Business Analysis (PMI-PBA)? See all practice exams.