mediumMultiple Choice
Schedule Compression Techniques: Crashing vs Fast Tracking
The sponsor asks the project manager to accelerate the project schedule without changing scope. Which technique should the project manager recommend?
⚠ Common exam trap
CompTIA often tests the distinction between crashing (adding resources) and fast tracking (parallel execution), where candidates mistakenly choose fast tracking because it sounds like a faster approach, but it risks rework and does not guarantee schedule compression without scope change.
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
✓
Crashing
Crashing is the correct technique because it involves adding additional resources to critical path activities to compress the project schedule without altering scope. This directly addresses the sponsor's request to accelerate the schedule while keeping the project scope unchanged.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monte Carlo simulation
Why it's wrong here
Monte Carlo simulation models schedule risk probabilistically; it quantifies uncertainty rather than compressing durations. It is tempting because it supports schedule analysis and contingency planning, but it cannot accelerate delivery without scope change. Crashing or fast-tracking alters task durations or dependencies to shorten the critical path.
- ✓
Crashing
Why this is correct
Crashing adds resources to critical path activities to shorten duration, directly compressing the schedule while scope stays fixed. It typically raises cost and risk, but that trade-off is acceptable when the sponsor demands acceleration without altering deliverables.
- ✗
Fast tracking
Why it's wrong here
Fast tracking overlaps activities that were sequential, which shortens duration but raises rework risk and requires the dependencies to permit parallel execution. It is tempting because it adds no people or cost, yet crashing, adding resources to the critical path, is the technique when overlap is impossible.
- ✗
Resource leveling
Why it's wrong here
Resource leveling resolves overallocation by delaying tasks, which typically extends the schedule rather than compressing it. It is tempting because it optimises resource usage across competing demands, suiting scenarios where resource limits drive planning. Schedule acceleration without scope change requires crashing or fast-tracking instead.
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.