CAPM Predictive Lifecycle Practice Question
In a predictive (waterfall) project, the project phases are completed sequentially. If the design phase is delayed by two weeks, what is the likely impact on the project?
⚠ Common exam trap
CAPM often tests the misconception that waterfall projects can easily recover delays through overlapping or that non-critical phases have no downstream impact, when in fact sequential dependencies make any phase delay propagate to the project end date.
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 duration is extended by exactly two weeks.
In a predictive (waterfall) project, phases are executed sequentially with dependencies, so a delay in the design phase pushes all subsequent phases (development, testing, deployment) forward by the same amount. Because the design phase is on the critical path and no overlapping is permitted in a pure waterfall model, the entire project duration extends by exactly two weeks. This reflects the rigid, plan-driven nature of predictive project management.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The project duration is extended by exactly two weeks.
Why this is correct
In a predictive waterfall project, phases run sequentially with no overlapping or fast-tracking, so a two-week design delay pushes every dependent downstream phase by the same amount. The critical path lengthens by exactly two weeks, assuming no float or compression is applied later.
- ✗
The delay can be recovered by overlapping subsequent phases.
Why it's wrong here
Overlapping phases is fast tracking, which contradicts the sequential predictive model stated in the stem. It is tempting because compression techniques do recover schedule, but they require deliberate re-planning and add risk, not automatic recovery of a two-week slip.
- ✗
Only the design phase is affected; later phases can start on time.
Why it's wrong here
In a predictive sequential project, a design delay pushes every dependent phase, since later phases cannot begin until design completes. It is tempting because phases are distinct work packages, but the finish-to-start dependency between them means the schedule end date slips.
- ✗
No impact because design is not on the critical path.
Why it's wrong here
In a sequential predictive project, design precedes build, so it lies on the critical path by definition; the delay moves the project finish. It is tempting because float analysis matters, but no float exists when phases run strictly one after another.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI 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 CAPM exam.