PK0-005 Tools and Documentation Practice Question
A project manager is selecting two documents that are essential for defining project scope. Which TWO documents should they choose?
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 scope statement (D) is correct because it formally documents the project's deliverables, boundaries, acceptance criteria, and exclusions, serving as the authoritative baseline definition of what is and is not in scope. The work breakdown structure (C) is correct because it decomposes the approved scope into hierarchical, manageable work packages, translating the scope statement into a deliverable-oriented framework that guides planning and control. Together these two documents define scope (scope statement) and organize it (WBS), which is why they are the essential pair for scope definition. The communication plan (A) governs information distribution and reporting, the risk register (B) tracks identified risks and responses, and the RACI matrix (E) clarifies roles and responsibilities—none of these define or decompose project scope, so they do not belong here.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Communication plan
Why it's wrong here
The communication plan specifies who receives which information, in what format and frequency; it governs stakeholder engagement, not the deliverables or boundaries of the project. It is tempting because scope changes drive communication needs, and it would be correct when planning information distribution across the project lifecycle.
- ✗
Risk register
Why it's wrong here
The risk register records identified threats, their probability, impact and planned responses; it does not bound what the project will deliver. It is tempting because scope changes spawn risks, and it would be the right artefact when assessing exposure or planning mitigation, not for defining scope boundaries.
- ✓
Work breakdown structure (WBS)
Why this is correct
The work breakdown structure decomposes the total project scope into deliverable-oriented, manageable components, providing the definitive hierarchical scope baseline. It satisfies the stem's scope-definition requirement, complementing the scope statement by translating agreed deliverables into discrete work packages for estimation and control.
- ✓
Scope statement
Why this is correct
The scope statement formally documents the project's deliverables, boundaries and acceptance criteria, giving the baseline against which scope creep is judged. It satisfies the stem's requirement for a scope-defining document, alongside the work breakdown scope baseline components.
- ✗
RACI matrix
Why it's wrong here
The RACI matrix assigns responsibility, accountability, consultation and information roles for activities; it allocates people, not scope. It is tempting because work packages appear in both, and it would be the correct choice when clarifying who does what on defined deliverables, not for establishing scope.
Go deeper
Related to this question
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 →
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.