PK0-005 Practice Question: Basics of IT Infrastructure and IT Project Management
A company is migrating from on-premise email to a cloud-based solution. The vendor changes the migration tool mid-project. Which project management document should be updated to track the impact on requirements?
⚠ Common exam trap
Many candidates confuse the risk management plan with tracking requirement impacts, but the RTM is the specific artifact for linking and monitoring requirement changes throughout the project lifecycle.
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
✓
Requirements traceability matrix
The requirements traceability matrix (RTM) links each requirement to its origin, design, testing, and delivery status. When the vendor changes the migration tool mid-project, the RTM must be updated to reflect how this change impacts each requirement—such as compatibility, data migration rules, or security controls—ensuring all requirements are still met and traceable.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Risk management plan
Why it's wrong here
The risk management plan defines how risks are identified and handled; it does not track requirement changes. It is tempting because a vendor tool change introduces risk, but the impact on requirements is recorded in the requirements traceability matrix, which maps requirements to changes and their downstream effects.
- ✗
Project charter
Why it's wrong here
The project charter authorises the project and records high-level objectives; it is baselined and not updated for mid-project tool changes. It is tempting because it defines initial scope, but requirement impact belongs in the requirements traceability matrix, which links each requirement to its source and status.
- ✓
Requirements traceability matrix
Why this is correct
The requirements traceability matrix links each requirement to its source, design, and test artefacts, so the vendor tool change and its requirement impacts are recorded there. Updating it maintains bidirectional traceability, letting the project manager assess which requirements are affected and confirm coverage after the migration tool substitution.
- ✗
Work breakdown structure
Why it's wrong here
The work breakdown structure decomposes deliverables and tasks; it does not capture requirement changes or their impact. It is tempting because a new tool alters tasks, but the requirements traceability matrix is the document that maps requirements to changes. The WBS tracks scope decomposition, not requirement impact.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 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 PK0-005 practice question is part of Courseiva's free CompTIA 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 PK0-005 exam.