CAPM Business Analysis Frameworks Practice Question
A business analyst is evaluating the performance of a business analysis framework after project completion. Which metric best indicates the effectiveness of the requirements management process?
⚠ Common exam trap
Candidates often confuse traceability (Option C) with quality, assuming that if a requirement is traced to a test case, it must be well-managed, but traceability only proves coverage, not correctness or completeness.
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
✓
Number of requirements defects found post-implementation
The number of requirements defects found post-implementation directly reflects the quality and completeness of the requirements management process. A high number of defects indicates that requirements were poorly defined, ambiguous, or missed during elicitation and validation, making it the most relevant metric for evaluating the effectiveness of that process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Schedule variance
Why it's wrong here
Schedule variance measures delivery timing against the baseline, not how well requirements were elicited, documented or controlled. It is tempting because variance reporting is a standard performance metric, and it would be the right indicator when the question concerns whether the project finished ahead of or behind its planned dates.
- ✓
Number of requirements defects found post-implementation
Why this is correct
Post-implementation requirements defects directly measure how well requirements were elicited, documented and managed, since each defect traces back to a missed, ambiguous or unvalidated requirement. This satisfies the stem's demand for an effectiveness metric by quantifying escaped errors rather than activity volume, giving the analyst concrete evidence of process performance after project completion.
- ✗
Number of requirements traced to test cases
Why it's wrong here
Traceability coverage counts requirements linked to test cases, evidencing that each requirement was verified, but it measures test coverage rather than the management process itself. It is tempting because traceability is central to requirements management, and it would be correct where the question asks whether requirements were validated by testing.
- ✗
Stakeholder satisfaction survey results
Why it's wrong here
Stakeholder satisfaction reflects overall project outcomes and delivery experience, not specifically how requirements were elicited, baselined or controlled. It is tempting because satisfaction surveys are common post-project evaluations, and they would be the right metric when judging whether the delivered solution met stakeholder expectations rather than the requirements process.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.