Practice PMI-PBA with free sample questions, timed mock exams, and detailed explanations in PM Mastery.
PMI-PBA is PMI’s business-analysis certification for practitioners who turn business needs into decision-ready requirements, traceability, and measurable outcomes. If you are searching for PMI-PBA sample exam questions, a practice test, mock exam, or exam simulator, this is the main PM Mastery page to start on web and continue on iOS or Android with the same PM Mastery account.
Start a practice session for PMI Professional in Business Analysis (PMI-PBA) below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.
Open Full App in a New TabA small set of questions is available for free preview. Subscribers can unlock full access by signing in with the same app-family account they use on web and mobile.
Use on iPhone or Android too: PM Mastery on the App Store or PM Mastery on Google Play using the same PM Mastery account you use on web. The same PM Mastery subscription works across web and mobile.
Free diagnostic: Try the 200-question PMI-PBA full-length practice exam before subscribing.
PMI-PBA questions usually reward the option that clarifies the need, improves decision quality, and keeps requirements testable and traceable instead of jumping straight to a solution.
| Domain | Weight |
|---|---|
| Needs Assessment | 18% |
| Planning | 22% |
| Analysis | 35% |
| Traceability and Monitoring | 15% |
| Evaluation | 10% |
Use these filters when an answer sounds organized but may not improve business-analysis quality. PMI-PBA usually rewards the option that clarifies the business need, tests assumptions, preserves traceability, and supports value-based decisions.
| Scenario signal | First check | Strong answer usually… | Weak answer usually… |
|---|---|---|---|
| Stakeholders disagree on scope | What business objective, value measure, or constraint should decide priority? | Reframes the discussion around goals, options, trade-offs, and decision criteria. | Keeps all requests in scope until delivery is forced to decide. |
| Requirements are vague | What acceptance, test, model, or example would make the requirement verifiable? | Clarifies, decomposes, validates, and makes requirements testable. | Documents the wording as-is because stakeholders already approved it. |
| The solution is being chosen early | Has the underlying need and value case been confirmed? | Separates need from solution and evaluates alternatives before commitment. | Starts detailed design because one stakeholder proposed a preferred tool. |
| A requirement changes | What upstream objective and downstream design, test, or release item are affected? | Uses traceability and impact analysis before approving or rejecting the change. | Accepts the change because it is small in isolation. |
| Delivered functionality is questioned | What outcome, acceptance criterion, or benefit measure proves fit? | Evaluates whether the solution meets the original need and value target. | Measures completion only by whether the feature shipped. |
Use this map after each timed run. Most PMI-PBA misses come from skipping a business-analysis step, not from forgetting a term.
| Domain | What the exam is really testing | What PM Mastery practice should force you to decide | Common wrong-answer trap |
|---|---|---|---|
| Needs Assessment | Whether the business problem, opportunity, and value case are clear | Which objective, measure, constraint, or stakeholder conflict controls scope | Treating every stakeholder request as a requirement |
| Planning | Whether analysis work is tailored to risk, life cycle, and stakeholder needs | How much documentation, governance, elicitation, and validation is enough | Overbuilding a heavyweight plan for a small adaptive effort |
| Analysis | Whether requirements are complete enough to make decisions | How to model, decompose, prioritize, validate, and resolve ambiguity | Jumping from vague need to solution design |
| Traceability and Monitoring | Whether requirement status and change impact remain controlled | What source of truth, status rule, impact check, or trace link is needed | Updating artifacts manually until they drift apart |
| Evaluation | Whether delivered work actually solves the business problem | Which benefit, outcome, acceptance result, or performance measure matters | Calling delivery complete because scope was implemented |
| Window | What to do | What not to do |
|---|---|---|
| Days 7-5 | Complete a mixed timed set or the full-length diagnostic, then classify misses by needs assessment, planning, analysis, traceability, evaluation, or timing. | Do not only reread terms; write the skipped business-analysis step. |
| Days 4-3 | Drill analysis and planning first if your misses involve vague requirements, poor tailoring, or weak elicitation choices. | Do not spend the final week memorizing artifact names if scenario sequencing is weak. |
| Days 2-1 | Review recurring traps: solution-first thinking, stakeholder wish lists, untestable requirements, manual status drift, and delivery without benefit evidence. | Do not start a large new run if fatigue will make requirement wording hard to parse. |
| Exam day | Identify the business need, decision point, traceability impact, and validation evidence before choosing the answer. | Do not choose an answer because it creates more documentation without improving decision quality. |
The goal is not to memorize every business-analysis prompt. The goal is to recognize the missing analysis step and choose the action that improves clarity, traceability, and value.
If you can complete several varied timed attempts at 75% or higher, explain why your missed answers skipped a need, requirement, traceability, or evaluation step, and consistently avoid solution-first distractors, it is usually time to sit the exam rather than repeating questions you already recognize.
If you want concept-first reading before heavier simulator work, use the companion guide at PMExams.com .
These sample questions are original PM Mastery practice items aligned to PMI-PBA-style business analysis decisions. They are not PMI exam questions and are not copied from any exam sponsor. Use them to check your readiness here, then continue in PM Mastery with mixed sets, topic drills, and timed mocks.
Topic: Domain 2: Planning
A BA is planning requirements work for a 6-week enhancement to an internal sales portal. One scrum team will deliver it, the product owner is available daily, and there is no new regulatory impact.
Draft requirements management note:
- Create a full BRD, detailed use cases, and separate workflow models
- Obtain formal signatures from Sales, Compliance, IT Operations, and the steering committee before Sprint 1
- Submit a change request for any requirement added or revised after sign-off
- Maintain a separate weekly traceability spreadsheet
What is the most important improvement before approving this plan?
Best answer: C
Explanation: The main issue is not missing detail but poor tailoring. For a short, low-risk agile enhancement with a readily available product owner, a heavyweight BRD, broad pre-sprint sign-offs, and formal change requests for every update create unnecessary overhead and slow value delivery.
Topic: Domain 4: Traceability and Monitoring
A BA supports a hybrid compliance program. Requirement R-27 was approved yesterday to move from validated to ready for build. Today, the traceability matrix shows ready for build, the weekly status report still shows validated, and the test readiness log shows pending review. The sponsor wants one approach that will keep future status information consistent across related artifacts and reports. Which approach is the best fit?
Best answer: A
Explanation: The best fit is to maintain one authoritative requirement status in the traceability tool and have dependent reports use that same approved value. When multiple artifacts are updated separately, status drift is likely and lifecycle tracking becomes unreliable.
Topic: Domain 1: Needs Assessment
A business analyst is supporting a customer-service modernization initiative. The executive sponsor wants a premium self-service feature set, operations managers want faster handling time, and the organization’s strategy emphasizes cost reduction through platform standardization. During needs assessment, which action should the business analyst AVOID to align goals, objectives, and solution scope?
Best answer: A
Explanation: When stakeholder priorities conflict, the BA should make trade-offs explicit by clarifying the business need, success measures, and scope boundaries. Keeping every request in scope to avoid conflict is an anti-pattern because it delays alignment instead of supporting it.
Topic: Domain 5: Evaluation
A BA is preparing Release 1 deployment of a supplier onboarding solution. The requirements management plan states that deployment may proceed only after every in-scope Release 1 requirement in the current baseline has passed validation and has sign-off from its approval owner in the traceability matrix. Baseline v3.2 is approved. A dashboard enhancement was approved through change control for Release 2.
Exhibit: Traceability matrix excerpt
| ID | Release | Approval owner | Validation | Sign-off |
|---|---|---|---|---|
| BR-07 Tax ID rule | 1 | Compliance manager | Passed | Pending |
| FR-14 Supplier request entry | 1 | Procurement director | Passed | Signed |
| TR-05 Service desk routing update | 1 | Support operations manager | Passed | Pending |
| FR-19 Analytics dashboard | 2 | Finance controller | Not in Release 1 | N/A |
Which stakeholders must sign off before deployment can proceed?
Best answer: D
Explanation: Deployment approval should follow the traceability matrix and the current approved baseline. The only Release 1 requirements still pending sign-off are the compliance rule and the service desk transition requirement, so both approval owners must sign before deployment.
Topic: Domain 4: Traceability and Monitoring
A business analyst is preparing weekly requirements status updates for a hybrid customer onboarding project. The project manager needs information to manage scope, schedule, and risk, while the compliance manager and test lead need updates tailored to their own decisions. Which reporting approach is INCORRECT?
Best answer: B
Explanation: Requirements status should be tailored to each stakeholder’s decision needs. The project manager needs concise, actionable status elements such as baseline state, change impacts, risks, and decisions required, so replacing that with raw notes is an anti-pattern.
Topic: Domain 3: Analysis
A business analyst is helping a bank choose between two approved change options after the requirements baseline was signed off. A regulator requires each interest-rate exception to trace to the business rule, approver, test case, and audit report. One option meets the marketing launch date but uses a manual override that breaks several trace links and requires manual reconciliation. The other delays launch by two weeks but preserves end-to-end traceability and controlled versioning. Which tradeoff should drive the option decision?
Best answer: D
Explanation: The deciding tradeoff is schedule versus preserving required traceability for a regulated requirement. Because the faster option breaks links to rules, approvals, tests, and audit evidence, it weakens impact analysis and controlled change after baseline.
Topic: Domain 3: Analysis
A company is replacing a legacy service portal. The compliance reporting module follows a predictive plan with formal phase-gate reviews, but the customer self-service portal is delivered in two-week sprints. After Sprint 3, stakeholders want evidence that portal requirements are being validated early enough to adjust the backlog before more work is committed. Which artifact provides the best validation evidence for this iterative workstream?
Best answer: B
Explanation: For iterative delivery, the strongest validation evidence is stakeholder review of a working increment against agreed acceptance criteria. That confirms requirement quality and acceptance at the right time, while backlog changes are still inexpensive and fast to make.
Topic: Domain 5: Evaluation
User acceptance testing is complete for a claims-processing solution. The operations manager gives approval only if end-user training is completed before go-live, and the compliance officer withholds approval until an audit-log defect is fixed. The sponsor wants the business analyst to document the sign-off decision for the deployment review. Which action is INCORRECT?
Best answer: A
Explanation: Sign-off documentation must reflect the actual decision state, including conditional approval, rejection, and exceptions. Converting mixed decisions into a simple approval hides deployment risk and misrepresents stakeholder authorization.
Topic: Domain 2: Planning
A business analyst is planning requirements work for a hybrid claims-platform project. Internal BAs, a vendor, QA, and compliance will share one repository. Compliance requires approved requirements and change records to be retained for 7 years. Elicitation starts next week, but no rules exist for who can create, edit, approve, archive, or delete artifacts. What should the business analyst do next?
Best answer: D
Explanation: The best next step is to define document control rules before requirements work begins. Because multiple parties will use the same repository and compliance has a stated retention requirement, the BA should establish who owns each artifact, who may access or change it, and how long records must be kept.
Topic: Domain 4: Traceability and Monitoring
During weekly requirements status reporting for a claims platform release, the BA dashboard shows 48 of 52 requirements as approved and on track. While preparing the report, the BA finds that five approved claim-routing requirements depend on fraud-vendor rules that are still unresolved, and the linked test scenarios cannot be completed without them. The project manager expects a green summary for the steering committee. What should the BA do next?
Best answer: C
Explanation: The BA should not let a high approval percentage hide a material dependency. Requirements status reporting must communicate issues that affect readiness, validation, or downstream delivery, even when items appear approved.
Topic: Domain 4: Traceability and Monitoring
A business analyst is updating the requirements communication approach for a hybrid project. The steering committee meets monthly and wants decision-focused status on requirement changes, risks, and business impact. The delivery team works in weekly iterations and needs prompt clarification of detailed requirement issues. Which communication practice should the business analyst AVOID?
Best answer: D
Explanation: Requirements status communication should be tailored to the audience. Governance stakeholders typically need summarized, decision-oriented information at a lower frequency, while working teams need more frequent, detailed updates to resolve issues quickly.
Topic: Domain 1: Needs Assessment
During needs assessment for a bank’s digital account-opening initiative, stakeholders suggest branch staffing changes, marketing offers, fraud-policy updates, and workflow automation. Problem analysis shows the business issue is delays between application intake, document verification, and account setup. The sponsor says phase 1 may change workflow and system handoffs but not staffing, marketing, or fraud policy. Which artifact is the best evidence for the scope boundary to include in the solution scope statement?
Best answer: D
Explanation: A solution scope statement needs clear boundary evidence: what is inside scope, what is outside scope, and which interfaces connect to external actors or systems. A context diagram is the strongest artifact because it visualizes those boundaries directly against the stated problem and exclusions.
Topic: Domain 5: Evaluation
A business analyst is reviewing user acceptance test results for a new invoice approval workflow before deployment. The documented acceptance criteria are: correct routing for at least 95% of invoices, approval history visible within 2 seconds, and mandatory reason codes for rejected invoices. The test report shows 97% routing accuracy, 3.1-second history loading, and 100% reason-code enforcement. The sponsor asks for immediate sign-off because most tests passed. What should the business analyst do next?
Best answer: A
Explanation: The next step is to validate the actual test evidence against every documented acceptance criterion, not to rely on an overall pass impression. Because the response-time criterion was missed, the BA should document that gap and support a decision on remediation before sign-off.
Topic: Domain 3: Analysis
A business analyst is elaborating a baselined mobile approval requirement for a CRM replacement. The requirement is traced to the objective of reducing quote turnaround time and to related API, audit logging, and UAT acceptance criteria. Interface analysis with the vendor shows the product can save approvals offline but cannot submit approvals until connectivity is restored. The sales director still wants full offline approval. What should the business analyst do next?
Best answer: C
Explanation: Analysis has revealed a gap between the stakeholder request and what the product can actually do. Because the requirement is already baselined and traced to downstream artifacts, the BA should use controlled change, assess impacts, and present feasible alternatives for decision.
Topic: Domain 2: Planning
A business analyst is drafting the requirements management plan for a claims portal project that will be delivered in 2-week iterations.
Draft note:
- Elicitation: interviews and monthly workshops
- Documentation: user stories with acceptance criteria and process flows
- Approval: sponsor signs off on the full requirements set before build starts
- Change control: any change after sign-off requires a formal change request
- Delivery approach: sprint reviews will be held every 2 weeks
Which improvement is most important?
Best answer: B
Explanation: The draft note describes elicitation and documentation, but its approval and change approach is still phase-gated. For iterative delivery, the requirements management plan must explain how backlog items will be refined, reprioritized, and approved during each iteration.
Topic: Domain 1: Needs Assessment
A business analyst has two days to assemble stakeholders for initial workshops on a claims process redesign. The sponsor wants broad representation, but only one representative from each area can attend at first. The analyst has approved business objectives, a solution scope baseline, and a draft set of high-level requirements with known dependencies to underwriting, compliance, billing, and the call center. What should the analyst do first to prioritize outreach?
Best answer: B
Explanation: When time is limited, the best approach is to prioritize outreach using traceability, not hierarchy or document convenience. Linking objectives and requirements to impacted areas and dependencies helps the analyst select representatives who provide the broadest useful coverage early.
Topic: Domain 3: Analysis
A business analyst has evaluated three product options for a customer returns process. The steering committee must choose one option tomorrow to approve the scope baseline. The agreed decision criteria are business value, compliance fit, operational disruption, and delivery within one 6-month release. Stakeholders are split, and the sponsor asks the BA to communicate the results so the committee can decide quickly. What is the best BA action?
Best answer: A
Explanation: The best communication supports a decision, not just information sharing. A concise decision package should synthesize the option evaluation into business-relevant trade-offs, show impacts on requirements, and provide a justified recommendation aligned to the agreed criteria and governance timing.
Topic: Domain 3: Analysis
A BA is performing impact analysis on a baselined warehouse system release after a change request is approved. The new requirement states: “Before go-live, inventory clerks must be trained on the new handheld process, and existing item-location data must be converted from the legacy system.” To maintain correct trace links and lifecycle status, how should this requirement be classified?
Best answer: C
Explanation: This is a transition requirement because it covers training and data conversion needed for cutover to the new solution. In a change-controlled environment, classifying it correctly helps the BA trace it to deployment activities, readiness work, and implementation status rather than to permanent product behavior.
Topic: Domain 2: Planning
A BA is defining traceability for a hybrid customer-portal project. Delivery teams manage epics, stories, defects, and test cases in one ALM tool and release every 2 weeks. Only payment and privacy features require audit evidence from business objective through test result.
Draft requirements package note:
Traceability approach
- Maintain a master spreadsheet for all requirements.
- Update links from business need -> requirement -> design -> test case monthly.
- Use the spreadsheet as the source for status reporting.
What is the most important improvement before this note is approved?
Best answer: A
Explanation: The traceability approach should fit the delivery environment and the level of control actually needed. In this scenario, a separate spreadsheet updated monthly is a poor fit for a fast-moving hybrid team already using an ALM tool, especially when only certain features need full audit traceability.
Topic: Domain 1: Needs Assessment
A business analyst is supporting a lender that wants to improve its consumer loan application process. In an early needs assessment workshop, the sponsor says the “goal” is to launch a new mobile portal with e-signature and status alerts by the fourth quarter. Operations leaders say the real concern is that too many applicants abandon the process and approved loans take too long to fund. No goals or objectives have been documented yet.
What should the business analyst do next?
Best answer: B
Explanation: The best next step is to clarify the business need into measurable product goals, such as reducing abandonment or shortening funding time, before treating portal capabilities as scope. In needs assessment, outcomes come first and features are evaluated against those outcomes.
Topic: Domain 2: Planning
An organization reused the requirements management plan from a two-year regulatory program for a 10-week internal workflow enhancement. The plan requires a full BRD, three levels of approval, and baseline updates for every user story. The delivery team works in one-week iterations, and several ready-for-build stories miss iteration start while waiting for approval. Which metric would best validate that the plan is too heavy for this project?
Best answer: B
Explanation: A requirements management plan is too heavy when its control steps slow delivery without adding proportionate value. Comparing approval turnaround with the one-week iteration cadence, and tracking stories delayed only by pending sign-off, directly tests whether the plan is obstructing requirements readiness.
Topic: Domain 2: Planning
A company is delivering a hybrid CRM enhancement with a fixed compliance release in 6 weeks. A sales director requests a new customer-segmentation rule that could increase campaign revenue, but the product owner says backlog changes are approved in refinement while the project manager says any scope change must go to the change control board. The vendor team says it needs one authorized decision path by Friday to avoid rework. What is the best action for the business analyst?
Best answer: C
Explanation: The key issue is not the change itself but the conflicting decision rights for approving it. The business analyst should first establish who approves which kinds of changes, how requests are routed, and how decisions are communicated so the team can apply a consistent control process under time pressure.
Topic: Domain 4: Traceability and Monitoring
A business analyst is preparing a weekly requirements status update for a project manager and steering committee. The audience has 10 minutes and wants the most important signals on change, risk, and readiness across 180 requirements. Which reporting approach is NOT appropriate?
Best answer: D
Explanation: Requirements status communication should be tailored to the audience and emphasize high-value signals such as exceptions, trends, risks, and readiness. A complete dump of every requirement comment and history makes it harder for stakeholders to quickly understand overall status and act on issues.
Topic: Domain 3: Analysis
A retailer is building a new internal returns-processing screen using two-week sprints. The product owner, operations leads, and developers refine backlog items together each sprint, and the screen flow is expected to change after the first demo. The BA needs requirements that are actionable for immediate development without wasting effort on details likely to change. Which requirements package is the best fit?
Best answer: C
Explanation: The best choice is the lightweight package that still makes requirements measurable and actionable. In an iterative context with frequent stakeholder access and expected UI change, user stories plus acceptance criteria, key rules, and a simple workflow provide enough detail for development and testing without over-specifying.
Use this map after the sample questions to connect individual items to needs assessment, stakeholder analysis, requirements elicitation, traceability, solution evaluation, and change decisions these PM Mastery samples test.
flowchart LR
S1["Business analysis scenario"] --> S2
S2["Identify problem opportunity and stakeholders"] --> S3
S3["Elicit analyze and prioritize requirements"] --> S4
S4["Trace requirements to value and solution scope"] --> S5
S5["Validate solution and manage change"] --> S6
S6["Evaluate outcome and lessons"]
| Cue | What to remember |
|---|---|
| Needs assessment | Start from business problem, opportunity, context, and expected value. |
| Elicitation | Choose techniques based on stakeholder type, uncertainty, and information needed. |
| Requirements | Good requirements are clear, testable, prioritized, traced, and aligned to objectives. |
| Traceability | Trace requirements to objectives, design, tests, changes, and acceptance. |
| Evaluation | Assess whether the solution delivers value, not just whether it was built. |
Use these child pages when you want focused PM Mastery practice before returning to mixed sets and timed mocks.