easyMultiple Select
PK0-005 Practice Question: Which TWO documents are commonly used to define…
Which TWO documents are commonly used to define and control project scope? (Choose two.)
⚠ Common exam trap
CompTIA often tests the distinction between the project charter (which authorizes the project) and the scope statement (which defines the detailed scope), leading candidates to incorrectly select the charter as a scope definition document.
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
✓
Work breakdown structure (WBS)
The Work breakdown structure (WBS) is correct because it decomposes the total project scope into manageable, hierarchical deliverables and work packages, providing the definitive framework for defining and controlling what is in scope. The Scope statement is correct because it formally documents the project's deliverables, boundaries, acceptance criteria, and exclusions, serving as the baseline against which scope changes are evaluated and controlled. The Project schedule is not a scope-defining document; it sequences activities and timelines derived from the WBS and scope baseline. The Risk register tracks identified risks, their analysis, and responses, not scope definition. The Project charter authorizes the project and provides high-level scope, but detailed scope definition and control are accomplished through the scope statement and WBS.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Work breakdown structure (WBS)
Why this is correct
The work breakdown structure decomposes deliverables into manageable work packages, giving a hierarchical, deliverable-oriented view of everything inside the project boundary. This directly satisfies the stem's requirement to define scope, since anything absent from the WBS lies outside the agreed scope baseline.
- ✗
Project schedule
Why it's wrong here
Shows timeline, not scope definition.
- ✓
Scope statement
Why this is correct
The scope statement documents the agreed project boundaries, deliverables, and acceptance criteria, giving a baseline against which scope changes are assessed. It satisfies the stem's requirement for a document that defines and controls scope, since it formally records what is in and out of the project.
- ✗
Risk register
Why it's wrong here
Documents risks, not scope.
- ✗
Project charter
Why it's wrong here
The charter authorizes but does not define or control scope in detail.
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 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.