Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by PMI
Exam Format
Registration
Validity
Skills this practice test covers
- Identify stakeholders and determine what each group values in the planned product.
- Plan how requirements will be traced, changed, controlled and accepted on a project.
- Elicit requirements, then analyze and decompose them into clear, testable statements.
- Prioritize requirements by value, risk and dependencies, and set their acceptance criteria.
- Track requirement status and assess change requests against the baseline.
- Validate the delivered solution and evaluate whether it meets the business need.
Explore related topics
PMI-PBA exam content
5 domains · 6 topics · 44 of 278 questions sorted by domain
Needs Assessment18%44 questions
This domain comes before any requirement is written. Candidates define or review the business problem or opportunity, gather and analyze information, set the product scope, and identify stakeholders and what they value.
Skills tested
- Review a business problem or opportunity and describe the scope of a solution.
- Collect information from several sources and judge what it means for the initiative.
- Identify stakeholders and assess their influence and interests.
- Determine stakeholder values so that they can guide requirement priorities later.
Questions by topic
- Identify Stakeholders2
- Assess Current State14
- Define Future State11
- Determine Solution Approach9
- Assess Risks5
- Identify Problem or Opportunity3
Planning22%
Planning prepares the business analysis work for the whole project. It sets the tools, policies and procedures for requirements management, traceability, change management, document control and acceptance criteria.
Skills tested
- Build a business analysis plan that fits the project plan and its estimates.
- Set the traceability approach and the change control procedure for requirements.
- Plan document control, version control and the storage of business analysis information.
- Define the acceptance criteria and business metrics used to judge the solution.
Analysis35%
The largest domain is the core requirements work. Candidates elicit requirements, analyze and decompose them, write them, set acceptance criteria, verify and validate them, and prioritize them.
Skills tested
- Choose an elicitation technique, such as interviews, focus groups or JAD sessions, for a situation.
- Decompose a requirement and model it with a context diagram or a data flow diagram.
- Write requirements that are clear, complete and testable.
- Verify that requirements are consistent and feasible, then validate them with stakeholders.
- Prioritize requirements with a technique such as MoSCoW or the Kano model.
Traceability and Monitoring15%
Approved requirements still have to be followed to the end. This domain covers tracing each requirement, monitoring and updating its status, reporting that status, and managing changes against the baseline.
Skills tested
- Trace requirements in both directions to check coverage and judge the impact of a change.
- Update requirement status and report it to each stakeholder group.
- Take a change request through change control, including a change control board.
Evaluation10%
The last domain checks the delivered solution against the need that started the work. Candidates validate the solution, evaluate its performance and obtain stakeholder acceptance.
Skills tested
- Validate the solution against its requirements and acceptance criteria.
- Track solution performance metrics and judge whether the expected value arrived.
- Obtain formal acceptance from stakeholders and record lessons learned.
Requirements
- Required with a secondary degree: 60 months of business analysis work earned in the last eight years.
- Required with a bachelor's degree or higher: 36 months of business analysis work earned in the last eight years.
- Required with a degree from a GAC-accredited program (PMI's Global Accreditation Center): 24 months of business analysis experience.
- Required on every route: 35 contact hours of formal training in business analysis.
About the PMI-PBA exam
PMI-PBA is the Project Management Institute's certification for practitioners who discover, analyze and manage the requirements that shape a project's results. PMI based the exam on a role delineation study of real business analysis work, and it covers five domains, from needs assessment to evaluating the delivered solution. PMI checks each application first, because candidates need years of business analysis experience and formal training in business analysis practices. Passing earns the PMI Professional in Business Analysis certification, which renews on a three-year cycle.
The PlanetCert practice test gives many of its questions to hands-on requirements work: conducting elicitation, specifying and modeling requirements, and tracing and prioritizing them. The explanations show why one technique fits a case better than another, for example when a requirements traceability matrix supports impact analysis. Study Mode suits the planning questions, where governance, change control and information management are easy to mix up. Brainy AI Assistant can compare verification with validation, or walk a change request through change control.
How to earn the certification
- Earns
- PMI Professional in Business Analysis (PMI-PBA)Professional
The certification runs on a three-year cycle. Holders renew it with professional development units (PDUs) under PMI's Continuing Certification Requirements program.
- Before
- CAPM Certified Associate in Project Management
Optional. PMI's entry-level certification, for people early in their project careers.
- CAPM Certified Associate in Project Management
How to prepare for PMI-PBA
- 1
Confirm eligibility before studying
PMI reviews each application before the exam can be scheduled. Match the business analysis experience to the right education route, and keep proof ready in case the application is audited.
- 2
Read PMI's two business analysis guides
Work through the PMI Guide to Business Analysis and Business Analysis for Practitioners: A Practice Guide with the exam content outline open. Note where each outline task is explained.
- 3
Give Analysis the most hours
Analysis is the largest domain. Practise eliciting, decomposing and writing requirements for one small project, then verify, validate and prioritize them with MoSCoW.
- 4
Build a traceability matrix by hand
Trace a handful of requirements back to business needs and forward to test cases. Then push one change request through the matrix and record its impact.
- 5
Build stamina for a long sitting
The exam is long, so take the PMI-PBA practice test in Timed Mode in full sittings. Review every missed question with Brainy AI Assistant, and note which task each miss belongs to.
Start a timed PMI-PBArun
PMI's own references for this exam are the PMI Guide to Business Analysis and its companion, Business Analysis for Practitioners: A Practice Guide.
Who PMI-PBA is for
- Business analysts who lead requirements work on projects and programs.
- Project managers who also carry the business analysis role on their teams.
- Product owners, systems analysts and requirements engineers who work closely with stakeholders.
Typical job titles: Business analyst · Business systems analyst · Requirements analyst · Product owner · Process analyst
PMI-PBA glossary
18 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Acceptance criteria
- The conditions a requirement or a solution must meet before stakeholders accept it.
- Bidirectional tracing
- Tracing a requirement back to the business need behind it and forward to the work that delivers it.
- Business case
- A document that justifies an initiative by comparing its expected benefits with its costs and risks.
- Change control board (CCB)
- A group with authority to review proposed changes to the requirements baseline and approve or reject them.
- Context diagrams
- Scope models that show a solution as one process, with the people and systems that exchange information with it.
- Data flow diagrams
- Models that show how information moves between processes, data stores and outside parties.
- Focus groups
- Elicitation sessions in which a moderator leads a small group of stakeholders through a topic to gather their views.
- Functional decomposition
- Breaking a process, function or requirement into smaller parts until each one can be understood and measured.
- Impact analysis
- Assessing how a proposed change would affect other requirements, the schedule, the cost and the solution.
- JAD sessions
- Joint application design workshops, in which business and technical stakeholders define requirements together.
- Kano model
- A model that sorts product features by their effect on customer satisfaction, from basic expectations to delighters.
- MoSCoW
- A prioritization technique that sorts requirements into must have, should have, could have and won't have.
- Product scope
- The features and functions that describe the product, service or result a project delivers.
- Professional Development Units (PDUs)
- The credits that PMI-PBA holders earn through learning, teaching or volunteering, and report to renew the certification.
- Requirements baseline
- The approved set of requirements at a point in time, against which later changes are controlled.
- Requirements traceability matrix
- A table that links each requirement to its business source and to the design and test items that depend on it.
- Role Delineation Study
- PMI's study of the tasks, tools and skills of business analysis practitioners. It is the basis of the PMI-PBA exam.
- Stakeholder register
- A list of the people and groups affected by an initiative, with their interests, influence and roles.