PK0-005 Tools and Documentation Practice Question
A project manager is preparing a procurement statement of work (SOW) for an external vendor. The SOW must clearly define the deliverables, acceptance criteria, and performance standards. Which document should the project manager reference to ensure the SOW aligns with the project's overall objectives and constraints?
⚠ Common exam trap
The trap here is assuming the project management plan or WBS contains all necessary details for a procurement SOW, when in fact the project scope statement provides the specific deliverable descriptions and acceptance criteria.
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
✓
Project scope statement
The project scope statement is the correct reference because it contains the detailed deliverables, acceptance criteria, and boundaries that must be reflected in the procurement SOW. It ensures the vendor's obligations are clearly defined and aligned with the project's overall objectives, reducing the risk of misunderstandings or scope creep during contract execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Project management plan
Why it's wrong here
The project management plan is a comprehensive document that integrates all subsidiary plans, but it is too broad for directly drafting a procurement SOW. The SOW needs specific scope details, which are found in the project scope statement and requirements documentation. Referencing the entire plan would not efficiently provide the precise deliverable descriptions required for the vendor.
- ✓
Project scope statement
Why this is correct
The project scope statement details the project deliverables, acceptance criteria, and exclusions, which are essential for creating a precise procurement SOW. It ensures the vendor's work aligns with the project's boundaries and quality expectations. By referencing it, the project manager can clearly define what the vendor must produce and how it will be accepted.
- ✗
Project charter
Why it's wrong here
The project charter authorizes the project and names the project manager, but it does not contain the detailed scope, deliverables, or acceptance criteria needed for a procurement SOW. While it provides high-level objectives, the SOW requires more granular information from the project scope statement and requirements documentation to ensure vendor deliverables align with project needs.
- ✗
Work breakdown structure (WBS)
Why it's wrong here
The WBS decomposes project work into manageable components, but it does not include acceptance criteria or performance standards. While it helps identify deliverables, it lacks the descriptive detail needed for a procurement SOW. The SOW requires explicit quality metrics and acceptance terms, which are better sourced from the project scope statement.
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.