CBAP® · IIBA · Requirements Analysis and Design Definition · Bank updated 2026-10-12
CBAP® practice questions: Requirements Analysis and Design Definition
5 free questions from 43 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Requirements Analysis and Design Definition section of our CBAP® bank (43 questions on this area, which carries 30% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 43 Requirements Analysis and Design Definition questions and the full CBAP® bank: $15 one-time.
1/5 · Requirements Analysis and Design Definition · easy
During a review, a business analyst checks that each requirement statement is unambiguous, complete, consistent, testable, and feasible, and that the requirements documentation meets the team's quality standards. Which BABOK v3 task is the analyst performing?
AVerify Requirements
BDefine Requirements Architecture
CApprove Requirements
DValidate Requirements
Answer: A. Verify Requirements is the quality-checking task: it confirms the requirements and designs are well-written and meet quality characteristics (atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, understandable). Validate Requirements, by contrast, confirms the requirements deliver business value. The distinction 'verify = built right / validate = right thing' is heavily tested.
Source: BABOK v3 — Requirements Analysis and Design Definition
2/5 · Requirements Analysis and Design Definition · hard
On a large transformation program, multiple analysts have produced requirements across several workstreams. The lead BA finds that some requirements contradict each other, others are duplicated across teams, and stakeholders cannot see how the pieces fit into a coherent whole that supports the business need. To resolve this systemically rather than statement-by-statement, the lead BA should primarily focus on which task?
APrioritize Requirements — ranking the requirements against the business need so that the most contradictory ones are deferred to a later release of the program
BValidate Requirements — confirming that each requirement delivers value against the business need before the whole set is approved
CDefine Requirements Architecture — structuring the requirements into a cohesive whole that shows interrelationships and completeness against the business need
DVerify Requirements — checking each requirement's wording for clarity and atomicity so that the requirements set reads as one coherent document
Answer: C. Duplication, contradiction, and lack of a coherent whole are problems of the requirements set, not of individual statements. Define Requirements Architecture organizes requirements into a structure that shows how they relate, ensures the set is complete and consistent, and exposes gaps and conflicts so they can be reconciled — addressing the issue systemically. Verification and validation work at the individual-requirement level and prioritization merely reorders.
Source: BABOK v3 — Requirements Analysis and Design Definition
3/5 · Requirements Analysis and Design Definition
A business analyst is documenting requirements for a claims-processing system. Stakeholders have agreed on the data entities involved and the rules governing how a claim moves between statuses, but they keep arguing during workshops about exactly when a claim is 'eligible for fast-track payout.' The BA decides the most effective way to remove this ambiguity is to capture the precise conditions, the inputs each condition relies on, and the resulting outcome in a structured form that can be tested for completeness. Which modelling approach best fits this need?
AA state model showing each claim status and the transitions between them
BA decision model (such as a decision table) expressing the conditions and corresponding outcomes
CAn entity relationship diagram refining the claim and payout data entities
DA data flow diagram tracing claim data through the processing system
Answer: B. The dispute concerns conditional logic (which combinations of inputs lead to which outcome), not statuses, data movement, or data structure. A decision model—commonly a decision table—captures conditions and outcomes in a structured representation that can be checked for completeness and consistency, making it the right specification approach.
Source: BABOK v3 — Requirements Analysis and Design Definition
4/5 · Requirements Analysis and Design Definition · hard
Stakeholders in an agile context push back on a BA's intricate UML models, saying they slow the team down and few people read them. However, the team has repeatedly mis-implemented a complex pricing rule, causing defects. The BA must decide what to model and at what level of abstraction. Which principle from Specify and Model Requirements should guide the decision?
AAvoid models altogether in agile contexts and rely on conversation, since the stakeholders say few people on the team read the UML diagrams
BSelect the model types and level of abstraction by the audience, the complexity of what is communicated, and the value the model adds
CUse the same standardized model set and level of abstraction on each project, so that the team's artifacts stay consistent over time
DModel everything formally at the most detailed level of abstraction to ensure full coverage of the pricing rule, regardless of audience
Answer: B. Models should be chosen and detailed according to audience, the complexity of the information, and the value they provide. Here that means investing in a precise model of the troublesome pricing rule while keeping low-value artifacts lightweight—not modelling everything formally nor abandoning models.
Source: BABOK v3 — Requirements Analysis and Design Definition
5/5 · Requirements Analysis and Design Definition
A BA receives peer-review feedback on a requirements specification. One reviewer writes: 'Requirement R-14 says the system shall display the report "quickly" and reflect the "most relevant" KPIs.' The reviewer flags this as a defect. The requirement is correctly traced, agreed by the sponsor, and clearly within solution scope. Which quality characteristic of requirements is the reviewer most directly objecting to?
AUnambiguous — the wording can be interpreted in more than one way and is not measurable
BFeasible — the requirement cannot be delivered within current constraints
CPrioritized — the requirement lacks an assigned priority relative to others
DEndorsed — the requirement has not been approved by an authorized stakeholder
Answer: A. Verify Requirements assesses quality characteristics including being unambiguous, complete, consistent, concise, testable, feasible, and atomic. Words like 'quickly' and 'most relevant' permit several readings and cannot be objectively tested, which is the unambiguous characteristic failing here. Feasibility, prioritization, and endorsement address different concerns and are not what the reviewer flagged.
Source: BABOK v3 — Requirements Analysis and Design Definition
Other CBAP® areas
The same kind of free sample for every other section of the CBAP® bank:
Practise CBAP® with instant feedback
6 free questions in study mode · no card · full CBAP® bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start CBAP® free →
Read next
How Hard Is the CBAP Exam? Pass Rate, Failure Points, and a 6-Week Plan (2026)
An honest look at CBAP difficulty: what the (unpublished) pass rate really means, the five reasons experienced BAs fail, and a realistic 6-week study plan.
PMI-PBA vs CBAP: The Business Analysis Certification Decision, Settled with Data
PMI-PBA ($405-555, 36 months of experience) vs CBAP ($495-650 all-in, 7,500 hours plus references): eligibility, exam mechanics, three-year cost, salary data.
ExamDeck is an independent study tool, not affiliated with IIBA®. CBAP® and BABOK® are trademarks of the International Institute of Business Analysis. Exam facts checked against official IIBA materials (as of October 2026); confirm current details on iiba.org.