easyMultiple Choice
PK0-005 Practice Question: Best describes a mandatory dependency in a…
Which of the following best describes a mandatory dependency in a project schedule?
⚠ Common exam trap
PK0-005 often tests dependency terminology, and the trap is confusing mandatory (hard logic) dependencies with discretionary (soft logic) dependencies, or conflating the internal/external dimension with the mandatory/discretionary dimension.
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
✓
A dependency that is inherent in the nature of the work and cannot be changed.
A mandatory dependency, also called a hard logic dependency, is one that is inherent in the nature of the work and cannot be changed without fundamentally altering the project scope or sequence. For example, you cannot test software before it is coded, or pour a foundation before excavating. This type of dependency is dictated by physical, technical, or contractual necessity and is not subject to the project manager's discretion.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A dependency that is required by the project team based on best practices.
Why it's wrong here
Best-practice sequencing is a discretionary dependency, chosen by the team and reorderable if needed. Mandatory dependencies stem from hard logic or contractual requirements, such as concrete curing before framing. Teams select discretionary dependencies to optimise scheduling, fast-tracking or crashing them when compressing the timeline.
- ✗
A dependency that involves a third-party vendor outside the project.
Why it's wrong here
Mandatory dependencies arise from the inherent nature of the work or a hard contractual constraint, not merely from involving an external vendor. Vendor involvement may create a discretionary dependency if the sequence could be reordered. Mandatory means the successor cannot start until the predecessor finishes.
- ✓
A dependency that is inherent in the nature of the work and cannot be changed.
Why this is correct
A mandatory dependency arises from the intrinsic nature of the work — for example, foundations must precede walls. It is contractual or physical in origin, unlike discretionary dependencies, which are preference-based and can be reordered.
- ✗
A dependency that can be changed if the project manager decides to reorder tasks.
Why it's wrong here
A mandatory dependency is fixed by the nature of the work itself, so it cannot be reordered at the project manager's discretion. This option describes a discretionary dependency, which is a soft logic preference that the team may reorder when beneficial — the correct classification when sequencing is a choice rather than a technical constraint.
Go deeper
Related to this question
About these practice questions
One of 954 original PK0-005 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.