easyMultiple Choice
PK0-005 Practice Question: Which document is used to record and track…
Which document is used to record and track changes to project scope and their approval status?
⚠ Common exam trap
Watch out — candidates often confuse the change log with the issue log, mistakenly thinking that any problem (issue) that affects scope is automatically a scope change, but the issue log is for managing problems, while the change log is specifically for the formal change control process and its approval status.
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
✓
Change log
The change log is the correct document for recording and tracking changes to project scope and their approval status. It serves as a formal, chronological record of all scope change requests, including the date, description, impact analysis, and final disposition (approved, rejected, deferred). This aligns with the PMI's Project Management Body of Knowledge (PMBOK) guidance for the Perform Integrated Change Control 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.
- ✗
Lessons learned
Why it's wrong here
Lessons learned captures retrospective knowledge at project closure or phase gates, not live scope changes awaiting approval. It is tempting because it does document project events, and would be correct when recording insights for future projects. Here, the stem requires an active log tracking each scope change request and its approval status.
- ✓
Change log
Why this is correct
The change log records each change request, its assessment, approval or rejection decision and current status. It satisfies the stem's requirement to track scope changes and their approval status, unlike the scope statement or issue log.
- ✗
Issue log
Why it's wrong here
An issue log records problems and their resolution, not scope changes or approval status. It is tempting because issues and change requests both flow through project governance, and unresolved scope disputes may appear as issues. It would be correct when tracking blockers, risks escalated to action, or defects requiring owners and deadlines.
- ✗
Risk register
Why it's wrong here
A risk register records identified threats and opportunities with their probability, impact and mitigation owners; it does not log scope changes or their approval state. It is tempting because both artefacts are living documents updated throughout delivery, and the register would be the right choice if the question asked where a newly identified threat to the project schedule is documented.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-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 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.