CAPM Business Analysis Frameworks Practice Question
After a change request is approved, a business analyst must update the requirements documentation. What is the most important step to ensure traceability?
⚠ Common exam trap
CAPM often tests the confusion between updating the RTM (the traceability artifact) and other valid but non-traceability actions like scheduling, communication, or archiving.
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
✓
Update the requirements traceability matrix
The requirements traceability matrix (RTM) is the artifact that links each requirement to its source, design, code, and test cases, so updating it after an approved change is what preserves end-to-end traceability. Without updating the RTM, the change would be invisible to downstream verification and impact analysis. This is the BA's primary mechanism for maintaining traceability across the requirements lifecycle.
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 requirements traceability matrix
Why this is correct
Updating the requirements traceability matrix directly satisfies the traceability constraint by linking the approved change to its originating requirement, affected deliverables and test cases. The matrix is the designated artefact for recording these relationships, so revising it after approval keeps the audit trail complete and verifiable.
- ✗
Revise the project schedule to reflect the change
Why it's wrong here
Revising the schedule addresses timelines, not the linkage of requirements to their sources, designs and tests. It is tempting because change requests often affect schedules, but traceability requires updating the requirements traceability matrix to reflect the approved change.
- ✗
Communicate the change to the development team
Why it's wrong here
Communication informs the team but creates no recorded link between the changed requirement and its origin, design or test artefacts. It is tempting because stakeholder communication is a core business-analysis activity, yet traceability demands updating the requirements traceability matrix instead.
- ✗
Archive the previous version of the requirements document
Why it's wrong here
Archiving preserves history but establishes no forward or backward links between the changed requirement and related artefacts, so traceability is not achieved. It is tempting because version control is good practise, yet the traceability matrix must be updated to record the relationships.
Go deeper
Related to this question
About these practice questions
One of 451 original CAPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
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.