mediumMultiple Choice
PK0-005 Practice Question: After a change request is approved, the project…
After a change request is approved, the project manager updates the project baseline. Which document must also be updated to reflect the impact of the change on project risks?
⚠ Common exam trap
CompTIA often tests the distinction between reactive documents (issue log) and proactive documents (risk register), so the trap here is confusing a change's potential future risks with current issues that have already materialized.
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
✓
Risk register
When a change request is approved and the project baseline is updated, the risk register must also be updated because the change may introduce new risks, alter the probability or impact of existing risks, or render some risks obsolete. The risk register is the formal document that captures identified risks, their analysis, and response plans, so any baseline change directly affects the risk profile of the project.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Issue log
Why it's wrong here
An issue log records problems currently affecting the project, not anticipated risks; approved changes alter the risk exposure captured in the risk register. It is tempting because issues and risks both track concerns, and an issue log is the right artefact once a risk has actually materialised and needs active resolution.
- ✓
Risk register
Why this is correct
Approved changes alter probability, impact or exposure of identified threats, so the risk register must be updated alongside the baseline to record new, modified or closed risks and their owners. It is the document reflecting the change's impact on project risks.
- ✗
Lessons learned
Why it's wrong here
Lessons learned capture retrospective knowledge from completed phases or past projects, not forward-looking risk exposure created by an approved change. It is tempting because changes often generate lessons, and the lessons learned register is correct when documenting what a closed change taught the team for future work.
- ✗
Stakeholder register
Why it's wrong here
The stakeholder register lists people and their engagement needs, so it cannot reflect how an approved change alters project risk exposure. It is tempting because changes frequently affect stakeholders, and updating the register is right when a change adds, removes or reassigns parties with an interest in the project.
Go deeper
Related to this question
About these practice questions
One of 954 original PK0-005 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 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.