Quick Answer
The answer is the scope statement and the work breakdown structure (WBS). These two documents are commonly used to define and control project scope because the scope statement formally records the project’s deliverables, assumptions, and constraints, establishing the baseline against which all scope changes are measured, while the WBS decomposes that scope into smaller, manageable deliverables, providing a structured framework for ongoing control. On the CompTIA Project+ PK0-005 exam, this pairing tests your understanding of how scope definition and control are linked: the scope statement sets the boundaries, and the WBS enforces them. A common trap is confusing the WBS with the project schedule or thinking a change request alone controls scope—remember, you need both a written baseline and a breakdown to manage changes effectively. For a memory tip, think “Statement says what, WBS shows how.”
This PK0-005 practice question tests your understanding of project management concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO documents are commonly used to define and control project scope? (Choose two.)
Work breakdown structure (WBS)
Breaks down scope into manageable components.
Project schedule
Why wrong: Shows timeline, not scope definition.
Scope statement
Defines the scope, deliverables, and acceptance criteria.
Risk register
Why wrong: Documents risks, not scope.
Project charter
Why wrong: The charter authorizes but does not define or control scope in detail.
Answer choices
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 a deliverable-oriented decomposition of the project scope into smaller, manageable components, providing a common framework for scope definition and control. The scope statement formally documents the project scope, including deliverables, assumptions, and constraints, serving as the baseline against which scope changes are evaluated. Both documents are essential for establishing and maintaining scope boundaries throughout the project lifecycle.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
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
Breaks down scope into manageable components.
Related concept
Read the scenario before looking for a memorised answer.
Project schedule
Why it's wrong here
Shows timeline, not scope definition.
Scope statement
Why this is correct
Defines the scope, deliverables, and acceptance criteria.
Related concept
Read the scenario before looking for a memorised answer.
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.
Common exam traps
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.
Trap categories for this question
Command / output trap
Shows timeline, not scope definition.
Detailed technical explanation
The WBS is typically structured using a numbering system (e.g., 1.0, 1.1, 1.1.1) that maps to the project's deliverables, and each work package at the lowest level should be assigned to a single responsible party. The scope statement often includes acceptance criteria, exclusions, and constraints that directly feed into change control processes, such as the integrated change control system defined in PMBOK. In practice, scope creep is prevented by requiring any change to the WBS or scope statement to go through a formal change request and impact analysis.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the PK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Project Management Concepts — study guide chapter
Learn the concepts, then practise the questions
Project Management Concepts practice questions
Targeted practice on this topic area only
All PK0-005 questions
500 questions across all exam domains
CompTIA Project+ PK0-005 study guide
Full concept coverage aligned to exam objectives
PK0-005 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PK0-005 questions linked to Project Life Cycle Phases.
Practise PK0-005 questions linked to Basics of IT Infrastructure and IT Project Management.
Practise PK0-005 questions linked to Project Management Concepts.
Practise PK0-005 questions linked to Tools and Documentation.
Practise PK0-005 questions linked to PK0-005 fundamentals.
Practise PK0-005 questions linked to PK0-005 scenario.
Practise PK0-005 questions linked to PK0-005 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Project Management Concepts — This question tests Project Management Concepts — Read the scenario before looking for a memorised answer..
The correct answer is: Work breakdown structure (WBS) — The work breakdown structure (WBS) is a deliverable-oriented decomposition of the project scope into smaller, manageable components, providing a common framework for scope definition and control. The scope statement formally documents the project scope, including deliverables, assumptions, and constraints, serving as the baseline against which scope changes are evaluated. Both documents are essential for establishing and maintaining scope boundaries throughout the project lifecycle.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 30, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.