If you work with stakeholders to define what a project should deliver, the Professional in Business Analysis (PMI-PBA)® certification from the Project Management Institute (PMI) is a way to prove it. The exam is long and scenario-heavy, so it can feel intimidating at first. The good news is that PMI publishes exactly what it tests, and a plan built around that blueprint makes the exam very passable on your first try.

In this guide, we’ll walk you through the exam format, each of the five domains and their weights, the official resources worth downloading, and the questions candidates ask most often.

What Is the PMI-PBA Exam?

The PMI-PBA is PMI’s credential for business analysis practitioners. PMI describes these professionals as people who work with stakeholders “to define an organization’s business requirements in order to shape the output of projects and ensure they deliver the expected business benefit.”

The exam tests how you apply business analysis practices in realistic situations, from spotting the real business problem to confirming that a deployed solution delivered value. It is not a vocabulary test. Most questions describe a project scenario and ask what the business analyst should do next or which technique fits best.

What Is the PMI-PBA Exam Format?

Here is the exam at a glance, based on the PMI-PBA Handbook and the PMI-PBA certification page:

  • Questions: 200 multiple-choice questions.
  • Scored vs. unscored: 175 scored questions and 25 unscored pretest questions mixed in at random. You won’t know which are which, so treat every question as if it counts.
  • Time: 4 hours (240 minutes).
  • Delivery: Computer-based through Pearson VUE, at a test center or online proctored.
  • Languages: English and Chinese (Simplified).
  • Results: You receive a score report right after you finish, showing pass/fail plus diagnostic feedback on your performance by domain.
  • Passing score: PMI does not publish a fixed passing percentage or cut score.

With 240 minutes for 200 questions, you have about 72 seconds per question. That is enough time if you practice reading scenarios efficiently, but not enough to reread every long stem twice.

What Content Outline Does the PMI-PBA Exam Use?

The current exam is based on the PMI-PBA Examination Content Outline, effective May 24, 2022, as published in the PMI-PBA Handbook. It divides the exam into five domains containing 28 task statements, supported by a list of 40 knowledge and skills areas such as elicitation, prioritization, traceability, valuation, and verification techniques.

Here is how the 175 scored questions break down. The approximate question counts are calculated from PMI’s percentages.

  • Domain 1, Needs Assessment: 18% (about 32 questions)
  • Domain 2, Planning: 22% (about 38 questions)
  • Domain 3, Analysis: 35% (about 61 questions)
  • Domain 4, Traceability and Monitoring: 15% (about 26 questions)
  • Domain 5, Evaluation: 10% (about 18 questions)

Domain 1: Needs Assessment (18%)

This domain is about understanding the business problem or opportunity before anyone jumps to a solution. You gather information, clarify goals, and identify stakeholders and what they value.

  • Define or review a business problem or opportunity to develop a solution scope statement or provide input to a business case.
  • Collect and analyze information using valuation tools and techniques to help determine the initiative’s value proposition.
  • Help develop project goals and objectives by clarifying business needs and solution scope.
  • Identify stakeholders so the right parties are represented, informed, and involved.
  • Determine stakeholder values using elicitation techniques to create a baseline for prioritizing requirements.

What questions look like: A sponsor asks for a specific new system. The best answer usually involves stepping back to confirm the underlying problem (for example, with root cause analysis) rather than documenting the requested solution right away.

Domain 2: Planning (22%)

Planning covers how you will run the business analysis work itself. Think of it as designing the rules of the road for requirements before the traffic starts.

  • Review the business case and project goals to provide context for business analysis activities.
  • Define a traceability strategy that sets the level of traceability needed to monitor and validate requirements.
  • Develop a requirements management plan covering stakeholders, roles and responsibilities, communication protocols, and methods for eliciting, analyzing, documenting, managing, and approving requirements.
  • Select requirements change control methods and document control methods, including versioning.
  • Define business metrics and acceptance criteria with stakeholders.

Study tip: Know what belongs in a requirements management plan and how it relates to the project’s change management plan. Questions often test whether you set up a process before you need it.

Domain 3: Analysis (35%)

Analysis is the largest domain by far, and it centers on the requirements themselves: eliciting, analyzing, decomposing, prioritizing, approving, specifying, and validating them.

  • Elicit requirements using individual and group techniques, capturing details such as origin and rationale.
  • Analyze and decompose requirements using dependency analysis, interface analysis, and data and process modeling.
  • Evaluate product options with decision-making and valuation techniques to accept, defer, or reject requirements.
  • Allocate requirements by balancing scope, schedule, budget, and resources against the value proposition to create a requirements baseline.
  • Obtain sign-off on the requirements baseline.
  • Write requirements specifications (for example, use cases and user stories) that are measurable and actionable.
  • Validate requirements using reviews, prototypes, and demos, and specify detailed metrics and acceptance criteria.

What questions look like: Expect to choose the right elicitation technique for a situation (a focus group vs. observation vs. a facilitated workshop) or the right prioritization approach, such as MoSCoW, when stakeholders disagree.

Domain 4: Traceability and Monitoring (15%)

This domain covers managing requirements across their life cycle. You track each requirement’s status, sources, and relationships, keep stakeholders informed, and manage changes against the baseline.

  • Track requirements with a traceability artifact or tool to provide evidence they are delivered as stated.
  • Monitor requirements so supporting artifacts (models, documentation, test cases) are produced, reviewed, and approved at each stage.
  • Update requirement status as it moves through life cycle states.
  • Communicate requirements status, issues, conflicts, changes, and risks to the project manager and other stakeholders.
  • Manage changes by assessing impacts, dependencies, and risks per the change control plan.

Study tip: Many candidates find this domain the trickiest. When a change request appears in a question, the best first step is almost always impact analysis, not implementing or rejecting the change.

Domain 5: Evaluation (10%)

Evaluation asks whether the delivered solution meets the requirements and the business need. It connects test results back to the acceptance criteria you defined earlier.

  • Validate test results and other evidence against the requirements acceptance criteria.
  • Analyze and communicate gaps between solution scope, requirements, and the developed solution.
  • Obtain stakeholder sign-off on the developed solution before deployment.
  • Evaluate the deployed solution to determine how well it meets the business case and value proposition.

Study tip: Be clear on the difference between verification (was it built correctly?) and validation (does it meet the need?).

How Should You Use the PMI-PBA Blueprint to Build a Study Plan?

The outline is your master checklist. Here’s a practical way to turn it into a plan:

  1. Take a baseline. Answer a mixed set of practice questions before you start reviewing so you know where you stand.
  2. Weight your time. Analysis alone is over a third of the exam, and Analysis plus Planning is 57%. Give those domains the most hours, but don’t skip Evaluation, since roughly 18 questions is still a lot to leave on the table.
  3. Map every miss to a task. When you get a question wrong, note which of the 28 tasks it tests. Patterns show up fast.
  4. Study the flow, not just the pieces. The domains follow a life cycle: needs assessment feeds planning, planning sets the rules for analysis, and acceptance criteria from analysis are what you evaluate against later.
  5. Finish with timed, mixed practice. In the final weeks, practice at exam pace so 72 seconds per question feels normal.

What Official Resources Should You Use?

  • PMI-PBA Handbook: Exam format, eligibility, domain weights, and the application and audit process.
  • PMI Certification Handbook: Policies that apply to all PMI exams, including scheduling, rescheduling, retakes, and testing options.
  • PMI-PBA certification page: Current requirements and pricing.
  • Commonly used references: The PMI Guide to Business Analysis, Business Analysis for Practitioners: A Practice Guide (Second Edition), A Guide to the Project Management Body of Knowledge (PMBOK® Guide), and Business Analysis: Best Practices for Success by Steven Blais.

Frequently Asked Questions About the PMI-PBA Exam

What is the passing score for the PMI-PBA?
PMI does not publish a passing score or percentage. Your score report shows pass/fail and diagnostic feedback by domain.

How soon will I get my results?
You receive your score report as soon as you finish the computer-based exam.

How many times can I take the exam?
Once your application is approved, you have a one-year eligibility period to take the exam up to three times. If you don’t pass in three attempts, you must wait one year from your last attempt before reapplying, according to the PMI Certification Handbook.

Has the PMI-PBA content outline changed recently?
The current exam follows the content outline effective May 24, 2022. The five domains and their weights (18%, 22%, 35%, 15%, and 10%) are unchanged in that version. PMI announces outline updates on the certification page, so check it before you schedule.

Are all 200 questions scored?
No. 175 are scored, and 25 are unscored pretest questions that PMI uses to evaluate future items.

How do I keep the certification?
You earn 60 professional development units (PDUs) every three years through PMI’s Continuing Certification Requirements (CCR) program.

Start Preparing for the PMI-PBA Exam With Pocket Prep

Pocket Prep’s PMI-PBA practice questions give you 500 exam-style questions across all five domains, each with a detailed answer explanation so you learn the reasoning behind the best answer. Use Weakest Subject quizzes to target your lowest-scoring domain, then build stamina with Timed Quiz sessions. With a clear blueprint and steady practice, you can walk into exam day ready.