hardMultiple Choice
PK0-005 Practice Question: A project manager is using a predictive life…
A project manager is using a predictive life cycle for a software development project. What is a key characteristic of this approach?
⚠ Common exam trap
A common mix-up: candidates confuse 'predictive' with 'iterative' or 'agile' because all involve phases, but the key differentiator is when scope is finalized and how changes are handled—predictive locks scope early, while agile embraces change throughout.
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
✓
The project scope is defined early and changes are constrained
In a predictive (waterfall) life cycle, the project scope is defined and baselined early in the project, and changes are tightly controlled through a formal change control process. This approach is suitable for software development projects where requirements are well-understood and unlikely to change significantly, such as when building a system with fixed regulatory or contractual specifications.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deliverables are produced in small increments
Why it's wrong here
A predictive life cycle plans the full scope up front and delivers the product through sequential phases, so small incremental deliverables belong to iterative or agile approaches. It is tempting because incremental delivery is common in software, but predictive projects define and approve requirements before build begins.
- ✓
The project scope is defined early and changes are constrained
Why this is correct
In a predictive (waterfall) life cycle, scope, schedule and cost baselines are fixed during planning, so change requests must pass formal integrated change control. Defining scope early and constraining changes is therefore the defining characteristic, enabling stable sequential execution.
- ✗
The team adapts to changing requirements
Why it's wrong here
Adaptive life cycles (e.g., Agile) embrace change.
- ✗
Requirements are defined iteratively
Why it's wrong here
Predictive life cycles define and baseline requirements during initiation, then manage changes through formal control; iterative elaboration belongs to agile or hybrid approaches. It is tempting because software requirements often evolve, but that evolution is handled by change requests, not by design in a predictive cycle.
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.