Courseiva
Project Life Cycle →mediumMultiple Choice

PK0-005 Project Life Cycle Practice Question

A project manager is developing a network diagram for a software rollout. Activity D (3 days) can start only after Activity C (2 days) finishes, and Activity E (4 days) can start when Activity C starts. Activities D and E must both finish before Activity F (1 day) begins. What type of dependency exists between Activity C and Activity E?

⚠ Common exam trap

PK0-005 often tests the distinction between dependency types by describing scenarios where activities overlap or are conditionally linked. Candidates frequently confuse Start-to-Start with Finish-to-Start, especially when the wording implies a sequential relationship. The trap is to assume that because D follows C, E also follows C's finish, but the question explicitly states E starts when C starts.

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

✓

Start-to-Start (SS)

The dependency between Activity C and Activity E is Start-to-Start (SS) because Activity E can start when Activity C starts. In project management, a Start-to-Start relationship means the successor activity cannot begin until the predecessor activity begins. Here, E's start is tied to C's start, not C's finish, so SS is correct.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Start-to-Start (SS)

    Why this is correct

    Activity E can begin as soon as Activity C starts, not after it finishes. That relationship, where the successor's start depends on the predecessor's start, is a Start-to-Start dependency, so SS correctly describes the C-to-E link.

  • ✗

    Start-to-Finish (SF)

    Why it's wrong here

    Start-to-Finish means the successor must finish before the predecessor may start, which reverses the stated logic; here E begins as C begins. SF is used for just-in-time scheduling, such as a shift handover where the outgoing operator cannot leave until the replacement arrives.

  • ✗

    Finish-to-Start (FS)

    Why it's wrong here

    Finish-to-Start requires the successor to wait until the predecessor finishes, yet E starts when C starts, so no waiting occurs. FS is the default dependency used when a downstream task genuinely cannot begin until its predecessor is complete.

  • ✗

    Finish-to-Finish (FF)

    Why it's wrong here

    Finish-to-Finish would require E to finish when C finishes, but the stem states E starts when C starts, which is Start-to-Start. FF is tempting because both activities relate to C's completion timing, and it is genuinely correct where a successor cannot finish until its predecessor finishes, such as documentation ending alongside testing.

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 →

How Courseiva writes practice questions · Editorial policy

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.