10 free sample questions from a bank of 156, with the correct answers and explanations. No signup required — start practising right now.
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.
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.
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.
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.
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.
When government, law or market shifts mid-project, choose business case alignment before traceability, schedule or sign-off answers.
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.
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.
When you see rationale, think why plus what we assumed — reasons and assumptions travel together as the memory hook for approval and change review.
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.
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.
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.
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.
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-
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.
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.
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
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
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.
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.
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.
Scope creep after baselining always points to change control process, not to more planning documents or one-time sign-off.
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.
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.
For constant communication plus expose issues as they develop, choose Agile — think owner in the room, not just cycles on a calendar.
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.
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.
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.
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
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.
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.
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.
When the consumer is a database administrator, pick the entity relationship diagram over process, flow or object views.
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.
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
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.
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
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.