mediumMultiple Choice
PK0-005 Practice Question: A project team is experiencing scope creep…
A project team is experiencing scope creep because stakeholders keep adding minor features without formal approval. What is the best way to prevent this in the future?
⚠ Common exam trap
CompTIA often tests the misconception that increasing the budget or updating the charter can control scope creep, but the correct answer is always the formal change control process because it provides a structured approval gate.
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 change control process
A change control process is the formal mechanism to evaluate, approve, or reject changes to project scope. By requiring all feature requests to go through this process, the project manager ensures that scope creep is prevented because no minor feature can be added without documented approval and impact analysis. This directly addresses the root cause—stakeholders bypassing formal approval.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Implement a change control process
Why this is correct
A formal change control process routes every proposed scope addition through documented impact assessment, approval and baseline update, so minor features cannot enter unapproved. This directly prevents the uncontrolled additions described, which occurred precisely because no such gate existed.
- ✗
Increase project budget
Why it's wrong here
Additional budget funds the extra features rather than gating them, so unapproved additions continue unchecked. It tempts because scope creep does raise cost, and extra funding would suit a project whose approved scope genuinely expanded, but here the problem is absent change control, not insufficient money.
- ✗
Ignore the requests until the next phase
Why it's wrong here
Deferring requests leaves them unassessed and unapproved, so they resurface later as committed work without change control. It tempts as a way to avoid confrontation mid-phase, and would suit low-impact items already queued, but it does not stop unapproved additions entering scope.
- ✗
Update the project charter
Why it's wrong here
Updating the charter records whatever was added, legitimising the creep retroactively instead of preventing it. It tempts because the charter defines scope, and revising it is correct after an approved change, but here no approval occurred, so the missing control is a formal change process.
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.