easyMultiple Choice
PK0-005 Practice Question: A project manager is assigned to a new project…
A project manager is assigned to a new project and needs to document high-level risks, assumptions, and constraints. Which document should the project manager create first?
⚠ Common exam trap
PK0-005 often tests the confusion between the project charter (authorizes the project, created first) and the project management plan (how the project will be executed, created after the charter) — candidates frequently pick the PM plan because it sounds more comprehensive.
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 charter
The project charter is the document that formally authorizes the project and captures the high-level risks, assumptions, constraints, business case, and success criteria before detailed planning begins. It is created first because it gives the project manager the authority to proceed and serves as the input to developing the project management plan and other subsidiary documents. Without an approved charter, the PM has no formal mandate to plan or execute.
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 consolidates subsidiary plans and baselines, and is produced after the project charter authorises the project; it does not capture initial high-level risks, assumptions and constraints. It is tempting as the overarching document, but it is developed progressively, not first.
- ✗
Risk register
Why it's wrong here
The risk register records identified risks with analysis and responses, but it excludes assumptions and constraints and is populated after risk identification begins. It is tempting because risks are named in the stem, but the charter is the document that first captures all three at a high level.
- ✗
Work breakdown structure
Why it's wrong here
The work breakdown structure decomposes deliverables into work packages; it contains no fields for risks, assumptions or constraints. It is tempting because it is an early planning artefact, but it is created after scope is defined and serves decomposition, not the documentation of these high-level items.
- ✓
Project charter
Why this is correct
The project charter authorises the project and captures high-level risks, assumptions, and constraints before detailed planning begins. It satisfies the stem's requirement to document these items first, since the charter is the initiating-phase artefact that precedes the project management plan, risk register, and business case.
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 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.