PK0-005 Project Life Cycle Practice Question
A project manager is developing a network diagram and needs to represent an activity that can start only after its predecessor has finished. Which dependency type does this describe?
⚠ Common exam trap
PK0-005 often tests the confusion between dependency types, especially mixing up Start-to-Finish (SF) with Finish-to-Start (FS) due to similar abbreviations or reversed logic.
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
✓
Finish-to-Start (FS)
Finish-to-Start (FS) is the correct answer because it defines a dependency where the successor activity cannot begin until the predecessor activity has completed. This is the most common dependency type in project scheduling, representing a sequential relationship where the finish of one task triggers the start of the next. In network diagrams, it is denoted by an arrow from the predecessor's finish to the successor's start.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Finish-to-Start (FS)
Why this is correct
Finish-to-Start means the successor activity cannot begin until the predecessor activity has completed, which is exactly the constraint described. The other dependency types (Start-to-Start, Finish-to-Finish, Start-to-Finish) permit overlapping or different timing relationships, so they do not match the stem.
- ✗
Start-to-Start (SS)
Why it's wrong here
Start-to-Start links the start of a successor to the start of its predecessor, allowing both to run concurrently; it does not require the predecessor to finish. Finish-to-Start is the dependency where the successor cannot begin until the predecessor completes. SS suits activities that must commence together, such as parallel testing phases.
- ✗
Finish-to-Finish (FF)
Why it's wrong here
Finish-to-Finish ties the successor's finish to the predecessor's finish, governing completion alignment rather than the successor's start. The stem demands that the successor cannot start until the predecessor finishes, which is Finish-to-Start. FF applies when two activities must conclude together, such as documentation closing with testing.
- ✗
Start-to-Finish (SF)
Why it's wrong here
Start-to-Finish makes the successor's finish depend on the predecessor's start, so the successor completes only once the predecessor begins. The stem requires waiting for the predecessor's completion before starting, which is Finish-to-Start. SF is used for just-in-time delivery or shift handover scenarios.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.