mediumMultiple Choice
PK0-005 Practice Question: A project manager is reviewing lessons learned…
A project manager is reviewing lessons learned from a previous similar project. That project suffered from frequent requirement changes that caused schedule delays and cost overruns. What should the project manager do to mitigate this risk on the current project?
⚠ Common exam trap
CompTIA often tests the misconception that preventing all changes or reducing stakeholder involvement is effective risk mitigation, when the correct approach is to manage changes through a structured, approved process rather than avoid or suppress them.
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
✓
Implement a robust change control process and ensure all changes are reviewed by the change control board.
Implementing a robust change control process with a change control board (CCB) ensures that all requirement changes are formally reviewed, approved, and documented before being incorporated. This directly addresses the risk of frequent, uncontrolled changes that caused schedule delays and cost overruns in the previous project, aligning with the PMBOK Guide's 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.
- ✗
Proceed without changes since the lessons learned may not apply to this project.
Why it's wrong here
Ignoring documented lessons leaves the same uncontrolled change exposure unaddressed, so the prior delays and overruns recur. It is tempting because each project differs, but lessons learned exist to inform risk planning; the project manager should instead establish change control and stakeholder engagement to manage requirement volatility.
- ✗
Minimize stakeholder involvement to reduce the number of change requests.
Why it's wrong here
Excluding stakeholders suppresses the visibility that surfaces requirement changes early, so changes still arrive late and unmanaged, worsening overruns. It is tempting because fewer requests appear to reduce churn, but engagement is precisely what enables controlled change; a formal change control process with impact assessment addresses the root cause.
- ✗
Develop a rigid schedule that does not allow any changes to requirements.
Why it's wrong here
A rigid schedule forbidding change does not prevent requirements from changing; it simply forces them through informally, causing the same delays and overruns. It is tempting because freezing scope appears to protect the baseline, but the correct mitigation is a change control board that evaluates, approves or rejects changes with schedule and cost impact.
- ✓
Implement a robust change control process and ensure all changes are reviewed by the change control board.
Why this is correct
A formal change control process with change control board review directly addresses the root cause of the previous project's delays: uncontrolled requirement changes. By requiring impact assessment and approval before implementation, scope creep is contained, protecting both the schedule baseline and cost baseline from unauthorised modifications.
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.