CBAP® practice questions: Requirements Analysis and Design Definition

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?

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?

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?

A BA inherits a requirements repository from a previous analyst. The requirements are individually well-written, but stakeholders complain they cannot find related requirements, cannot tell which business goal a given requirement supports, and cannot see how detailed requirements roll up to higher-level objectives. The BA decides to apply a recognized template that organizes requirements into related views. What is the BA primarily using, and what does it provide?

On a large transformation program, the security team, the data-governance team, and the operations team each insist on receiving requirements documentation laid out in the conventions and level of detail their discipline expects, and they refuse to read the BA's single monolithic specification. The underlying requirements are the same; only the way each audience needs them organized and presented differs. Within Define Requirements Architecture, which concept most directly addresses this situation?