CAPM Business Analysis Frameworks Practice Question
A business analyst is verifying that all requirements have corresponding test cases. They find a requirement that has no linked test case. What should the BA do first?
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
✓
Request a test case to be created for that requirement.
Request a test case to be created for that requirement. In business analysis, traceability ensures every requirement has a corresponding test case to verify it is implemented correctly. When a requirement lacks a test case, the BA should first request one to maintain coverage. Option A is incorrect because the project manager does not typically authorize test cases; the BA or QA team handles them. Option B is incorrect because ignoring the issue violates traceability best practices. Option D is incorrect because removing the requirement is premature without analysis; the BA should first try to create a test case.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the project manager to approve the missing test.
Why it's wrong here
Approval cannot manufacture a test case; the BA owns requirements traceability and should raise the gap with the tester or developer who can actually write one. Escalating to the project manager is tempting because they own scope sign-off, but this is a traceability defect, not a change request.
- ✗
Ignore it as it may not be critical.
Why it's wrong here
Ignoring the gap leaves a requirement unverified, so defects surface in production instead of testing. Deferring is tempting when the requirement looks low priority, but criticality is judged by the business, not assumed by the BA, and the traceability matrix must stay complete regardless.
- ✓
Request a test case to be created for that requirement.
Why this is correct
Raising a request for the missing test case closes the traceability gap identified during verification, ensuring the requirement gains coverage. This is the immediate corrective step; escalating or altering the requirement comes only after the coverage shortfall is formally addressed.
- ✗
Remove the requirement if it cannot be tested.
Why it's wrong here
Deleting the requirement destroys scope the stakeholders approved, and untestability often signals vague wording rather than redundancy. Removing requirements is tempting because it cleans the traceability matrix, but that is a change control decision for the sponsor, not a first response to a missing link.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.