PMI-PBA (Professional in Business Analysis) Practice Exam
Cover all five PMI-PBA domains — needs assessment, planning, analysis, traceability and monitoring, and evaluation — with scenario-based questions, instant feedback in Learn mode, and a full timed simulation in Exam mode. Start with a 24-hour free trial.
Start 24-hour free trial →PMI-PBA exam at a glance
- Vendor
- Project Management Institute (PMI)
- Exam name
- PMI Professional in Business Analysis (PMI-PBA)®
- Blueprint
- PMI-PBA Examination Content Outline, supported by the PMI Guide to Business Analysis and Business Analysis for Practitioners: A Practice Guide; verify edition before publish
- Format
- 200 multiple-choice questions, knowledge- and scenario-based, including unscored pretest items
- Duration
- 240 minutes (4 hours)
- Delivery
- Pearson VUE test center or online proctored
- Passing standard
- PMI does not publish a fixed passing score; results are determined by psychometric analysis and reported as pass or fail
- Prerequisites
- One of: secondary diploma + 60 months of business-analysis experience + 35 contact hours; OR a four-year degree + 36 months of business-analysis experience + 35 contact hours; OR a GAC-accredited degree + 24 months experience (GAC coursework can credit toward the hours). Experience must be within the last 8 years.
- Validity
- 3 years; renew with 60 PDUs
Source: PMI — PMI-PBA Certification Handbook & Exam Content Outline. Verify current details with PMI before applying.
About the PMI-PBA (Professional in Business Analysis) certification
The PMI-PBA is PMI’s credential for business analysis — the discipline of uncovering business needs, eliciting and managing requirements, and making sure the solution a project delivers actually solves the right problem. Where the PMP is about leading and delivering the project, the PMI-PBA is about defining what should be built and proving it delivers value. It is firmly requirements-centric: the exam leans heavily on elicitation, analysis, traceability, and evaluation rather than on schedule or budget. For foundational reading on the delivery discipline business analysis supports, see the Program & Project Management Fundamentals guide.
PowerKram’s PMI-PBA practice exam mirrors the scenario style of the real test and maps every question to one of the five domains, so your score report tells you exactly which area — needs assessment, planning, analysis, traceability, or evaluation — to strengthen.
PMI-PBA exam domains and weights
The PMI-PBA exam splits questions across five domains, and one dominates: Analysis at 35% — more than a third of the exam. Combined with Planning (22%), the front half of the requirements lifecycle accounts for well over half of all questions, signaling that the exam rewards depth in eliciting and analyzing requirements above all else.
Understanding the business problem or opportunity: problem and opportunity analysis, valuation, defining solution scope, identifying stakeholders, and contributing to the business case.
Preparing to manage business analysis: the requirements management plan, traceability strategy, change control, document control, and acceptance criteria.
The core domain: eliciting, analyzing, decomposing, and specifying requirements; evaluating product options; prioritizing and baselining; and obtaining sign-off. By far the most heavily weighted.
Tracking requirements across the lifecycle with a requirements traceability matrix, managing changes against the baseline, and keeping requirements linked to business objectives.
Validating that the delivered solution meets the requirements and business need: assessing solution performance against acceptance criteria and the expected value.
Weights are domain-level item percentages from the official outline. Source: PMI-PBA Examination Content Outline.
Who the PMI-PBA is for
The PMI-PBA is a specialist credential requiring substantial business-analysis-specific experience — and despite the name, it is not limited to people with the title “business analyst.” Anyone whose work includes defining needs, managing requirements, and evaluating solutions can qualify.
- Business analysts and systems analysts formalizing deep expertise across the full requirements lifecycle.
- Product owners and product managers who own requirements, backlogs, and value alignment.
- Project and program managers who perform business analysis as part of their role and want to prove that depth.
- Consultants and requirements engineers who bridge stakeholders and technical teams across projects.
If you want the broad project-management foundation alongside it, the PMP pairs naturally with the PMI-PBA — the two are complementary, with the PMP covering delivery leadership and the PMI-PBA covering requirements. For role-by-role salary ranges and the business-analysis and product career paths the PMI-PBA supports, see the Career Hub — Product Manager role guide.
What this PMI-PBA practice exam delivers
Learn mode
Get the correct answer, the explanation, and why the other choices were wrong — immediately after each question. Built for the close-call BA judgment the PMI-PBA tests, where several answers look reasonable.
Exam mode
A timed, full-length simulation on the real 4-hour, 200-question clock — build the pacing and stamina the actual PMI-PBA exam, one of PMI’s longest, requires.
Source-linked explanations
Every answer cites the PMI source it derives from (the Exam Content Outline or the PMI Guide to Business Analysis) so you can verify and dig deeper.
Score by PMI-PBA domain
Your results break down across all five domains — with the dominant 35% Analysis domain weighted as on the real exam — so practice shows exactly where to focus.
Sample PMI-PBA practice questions
Ten free questions across the five domains, with full explanations. The complete bank is available with the 24-hour trial.
A business analyst needs to capture detailed stakeholder needs for a new CRM system. Which elicitation technique is most appropriate for in-depth, one-on-one understanding?
- Stakeholder interviews
- Quantitative risk analysis
- A PERT chart
- Test case creation
Show answer & explanation
Correct: A — Stakeholder interviews. Interviews are a primary elicitation technique for drawing out detailed, nuanced requirements directly from individual stakeholders — ideal early in analysis when understanding needs deeply matters most.
Why not the others: risk analysis (B) addresses threats, not requirements elicitation; a PERT chart (C) is a scheduling tool; test cases (D) come later, to verify a built solution — none elicits requirements.
Source: PMI-PBA Exam Content Outline — Analysis (elicitation) → Further reading: PowerKram — Requirements Elicitation →During a workshop a stakeholder gives vague, ambiguous feedback about a requirement. What should the analyst do?
- Ask clarifying, probing questions to remove the ambiguity
- Document the feedback exactly as stated and move on
- Disregard the feedback
- Fill the gap with the analyst’s own assumptions
Show answer & explanation
Correct: A — Ask clarifying questions. Ambiguous input must be resolved at the source. Probing questions turn vague statements into clear, testable requirements and prevent costly misalignment downstream.
Why not the others: documenting ambiguity as-is (B) bakes in confusion; ignoring it (C) loses a real need; substituting assumptions (D) risks building the wrong thing — the classic cause of rework.
Source: PMI-PBA Exam Content Outline — Analysis →A team must prioritize a backlog of competing requirements into must-haves and nice-to-haves. Which technique supports this?
- MoSCoW prioritization
- Monte Carlo simulation
- A Gantt chart
- A RACI matrix
Show answer & explanation
Correct: A — MoSCoW. MoSCoW sorts requirements into Must have, Should have, Could have, and Won’t have — a standard, fast technique for prioritizing competing requirements against value and constraints.
Why not the others: Monte Carlo (B) models risk/uncertainty; a Gantt chart (C) schedules work; a RACI matrix (D) assigns responsibilities — none prioritizes requirements.
Source: PMI-PBA Exam Content Outline — Analysis (prioritization) → Further reading: PowerKram — Requirements Prioritization →Before a project begins, an analyst must clearly define what the solution will and will not include. Which artifact captures these boundaries?
- The solution scope statement
- The risk register
- The issue log
- The communication plan
Show answer & explanation
Correct: A — The solution scope statement. A scope statement defines what is included and excluded from the solution, setting the boundaries that guide requirements work and prevent scope creep — a Needs Assessment deliverable.
Why not the others: a risk register (B) tracks risks; an issue log (C) tracks current problems; a communication plan (D) governs information flow — none defines solution boundaries.
Source: PMI-PBA Exam Content Outline — Needs Assessment → Further reading: PowerKram — Defining Solution Scope →A stakeholder requests a feature that falls outside the approved requirements baseline. What is the analyst’s correct first action?
- Evaluate the request and submit it through the change control process
- Implement it immediately to keep the stakeholder happy
- Reject it outright without review
- Quietly add it to the backlog with no assessment
Show answer & explanation
Correct: A — Evaluate and submit a change request. Changes to a baselined requirement must go through formal change control so their impact on scope, value, and constraints is assessed and approved — protecting the baseline while still considering legitimate needs.
Why not the others: implementing immediately (B) invites scope creep; rejecting without review (C) may discard a valuable need; adding without assessment (D) bypasses governance.
Source: PMI-PBA Exam Content Outline — Traceability and Monitoring (change control) → Further reading: PowerKram — Requirements Change Control →A team needs to confirm that documented requirements are correct and complete before development. Which activity supports this validation?
- Requirements walkthroughs (reviews) with stakeholders
- Open-ended brainstorming
- Risk identification
- Sprint planning
Show answer & explanation
Correct: A — Walkthroughs / reviews. Structured walkthroughs and reviews with stakeholders confirm that requirements are understood, correct, and complete — a core validation technique before committing to build.
Why not the others: brainstorming (B) generates ideas rather than validating them; risk identification (C) finds threats; sprint planning (D) organizes upcoming work — none validates requirement correctness.
Source: PMI-PBA Exam Content Outline — Evaluation (validation) →An analyst needs to model how a current business process flows from step to step. Which tool is most appropriate?
- A process flow diagram (flowchart)
- A stakeholder register
- A test plan
- A responsibility (RACI) matrix
Show answer & explanation
Correct: A — A process flow diagram. A flowchart visualizes the sequence of steps, decisions, and handoffs in a process, making it the standard tool for modeling current- and future-state business processes during analysis.
Why not the others: a stakeholder register (B) lists people; a test plan (C) is a quality artifact; a RACI matrix (D) maps responsibilities — none models process flow.
Source: PMI-PBA Exam Content Outline — Analysis (modeling) →A stakeholder wants to track each requirement from its origin through design, build, and testing. Which artifact provides this?
- A requirements traceability matrix (RTM)
- A risk matrix
- The project schedule
- The issue log
Show answer & explanation
Correct: A — The requirements traceability matrix. An RTM links each requirement to its origin and forward through design, development, and test, so you can confirm every requirement is addressed and assess the impact of any change — the heart of the Traceability and Monitoring domain.
Why not the others: a risk matrix (B) ranks risks; the project schedule (C) tracks time; the issue log (D) tracks problems — none traces requirements end to end.
Source: PMI-PBA Exam Content Outline — Traceability and Monitoring →A team is choosing among several solution options. Which factor should weigh most heavily in the decision?
- Alignment with the business goals and the value the solution delivers
- The lowest upfront cost, regardless of fit
- Whichever can be delivered fastest
- The most popular vendor in the market
Show answer & explanation
Correct: A — Alignment with business goals and value. Solution options are evaluated primarily on how well they meet the business need and deliver the expected value. Cost and speed matter, but only in service of a solution that actually solves the right problem.
Why not the others: lowest cost (B), fastest delivery (C), and vendor popularity (D) optimize a single factor and can produce a cheap, fast, or trendy solution that fails to meet the need.
Source: PMI-PBA Exam Content Outline — Evaluation →A project spans several departments with competing interests. How should the analyst manage the complexity of aligning their requirements?
- Facilitate cross-functional requirements workshops to surface and reconcile needs
- Hand all requirements decisions to the project manager
- Ignore the conflicts and proceed
- Focus only on the IT department’s needs
Show answer & explanation
Correct: A — Facilitate cross-functional workshops. Facilitated workshops bring competing stakeholders together to surface, compare, and reconcile requirements, building shared understanding and alignment — a core BA planning and facilitation skill for multi-department work.
Why not the others: handing it to the PM (B) abdicates the analyst’s role; ignoring conflicts (C) lets them resurface later; focusing only on IT (D) ignores other legitimate stakeholders.
Source: PMI-PBA Exam Content Outline — Planning (stakeholder engagement) → Further reading: PowerKram — Facilitated Workshops →Keep going: Learning & Career resources
A business analysis credential earns its return when paired with the broader delivery fundamentals and a clear sense of the BA and product roles it opens up. Two PowerKram hubs back this exam up.
Deep dive: PMI-PBA exam structure, eligibility, study path & recertification
Exam structure and how it’s scored
The PMI-PBA is one of PMI’s longest exams: 200 multiple-choice questions in 240 minutes (4 hours), including unscored pretest items mixed in randomly, so treat every question with equal effort. Questions are knowledge- and scenario-based, asking you to choose the best BA action, artifact, or next step in a given situation. PMI does not publish a fixed passing percentage; the result is determined by psychometric analysis and reported as pass or fail, with a performance breakdown by domain. Read the business-analysis fundamentals guide →
Eligibility paths
The PMI-PBA has three eligibility paths, all requiring business-analysis-specific experience earned within the last eight years plus 35 contact hours of BA education. With a secondary diploma you need 60 months of BA experience; with a four-year degree, 36 months; with a GAC-accredited degree, 24 months (and the GAC coursework can also count toward the 35 contact hours). Document your BA experience carefully — PMI audits a share of applications. Read the business-analysis-career guide →
Realistic study path
The core references are the PMI Guide to Business Analysis and Business Analysis for Practitioners: A Practice Guide. Because Analysis (35%) and Planning (22%) together are well over half the exam, weight your study toward elicitation, requirements analysis and decomposition, prioritization, and the requirements management plan. Be comfortable choosing the best technique for a scenario rather than just defining terms — the exam is heavily applied. PowerKram’s domain-level scoring surfaces your weakest domain early. Read the business-analysis study guide →
Cost, scheduling, and retake policy
The PMI-PBA exam fee is reduced for PMI members, and membership includes access to the PMI Guide to Business Analysis and other resources. The exam is delivered at Pearson VUE centers or online with a proctor. You may attempt the exam up to three times within your one-year eligibility period. Verify current fees and policies on PMI’s site before applying. PMI’s official PMI-PBA page →
Recertification (PDUs)
The PMI-PBA is valid for three years. To renew, you earn 60 Professional Development Units (PDUs) per cycle — notably, PMI groups the PMI-PBA with the PMP at 60 PDUs, double the 30 required by its specialist scheduling and risk credentials. Business analysis work, courses, webinars, and BA communities all count. PMI’s CCR Handbook is the authoritative reference. Read the PDU and recertification guide →
Career outlook for PMI-PBA holders
Poor requirements are one of the most common root causes of failed projects, which makes proven business-analysis expertise valuable across virtually every industry. The PMI-PBA signals depth in requirements work that a generalist credential does not, helping practitioners stand out for business analyst, requirements lead, product owner, and product manager roles. For salary ranges and role-specific paths, see the Career Hub. Career Hub — Product Manager role →
Start your free 24-hour PMI-PBA practice trial
Full access to the question bank, both study modes, and domain-level scoring across all five PMI-PBA domains. No credit card required.
Start free trial →