Business Analysis Frameworks →mediumMultiple Choice

CAPM Business Analysis Frameworks Practice Question

Exhibit

{
  "stakeholders": ["Sales", "IT", "Marketing"],
  "requirements": [
    {"id": "REQ01", "description": "User login", "status": "Approved"},
    {"id": "REQ02", "description": "Auto-save", "status": "Draft"}
  ]
}

Refer to the exhibit. A business analyst is reviewing the requirements status in a JSON export from a requirements management tool. The analyst notices that REQ02 is still in 'Draft' while REQ01 is 'Approved'. What should the analyst do next?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Facilitate a review meeting for REQ02

A requirement in draft status needs to be reviewed and approved by stakeholders before proceeding, so facilitating a review meeting is the appropriate action.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Update the traceability matrix
Why it's wrong here
Traceability links requirements to their sources, tests and deliverables; it does not resolve a requirement still sitting in Draft, so updating it leaves the actual gap untouched. Updating the matrix is tempting because it is a routine analyst task, and it is correct after REQ02 is approved and needs linking.
✓
Facilitate a review meeting for REQ02
Why this is correct
REQ02 remains in Draft, so it cannot progress until stakeholders validate it. Convening a review meeting moves it toward Approved status, resolving the inconsistency with REQ01. Editing status directly or proceeding to design would bypass the approval gate the requirements tool is enforcing.
✗
Approve REQ02 immediately
Why it's wrong here
A business analyst cannot unilaterally approve a requirement; approval requires the authorised stakeholder sign-off that moves it out of Draft. Approving immediately is tempting because it clears the status mismatch quickly, and it is correct once the analyst has obtained that formal stakeholder approval.
✗
Request closure for REQ02
Why it's wrong here
Closure applies to requirements that have been implemented and verified, not to one still in Draft awaiting approval; requesting it skips the approval gate entirely. Requesting closure is tempting because it tidies the status, and it is correct once REQ02 has been approved, built and validated.

Go deeper

CAPM Business Analysis Frameworks Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question