mediumMultiple Select
Common Project Charter Components: High-Level Scope, Business Case, and Budget Summary
Which THREE are common types of project management documentation? (Choose three.)
⚠ Common exam trap
CompTIA often tests the distinction between project management documentation (e.g., charter, risk register, scope statement) and technical or operational artifacts (e.g., network diagrams, server config files) to see if candidates understand the boundary between project governance and technical implementation.
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 (B) is a foundational project management document that formally authorizes the project, names the project manager, and captures high-level objectives, so it is a correct answer. The risk register (C) is a standard project management artifact used to identify, assess, and track risks and their responses throughout the project lifecycle. The scope statement (E) is also core project management documentation because it defines the project's deliverables, boundaries, and acceptance criteria. By contrast, a network diagram (A) is typically a technical or design artifact showing topology or dependencies rather than a standard project management document, and a server configuration file (D) is an operational IT artifact, not project management documentation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Network diagram
Why it's wrong here
A network diagram is a schedule-development technique output, not project management documentation such as the charter, business case or risk register. It tempts because it is a genuine project artefact, but the question asks for documentation types, and diagrams sit under scheduling tools rather than the document set.
- ✓
Project charter
Why this is correct
The project charter formally authorises the project and names the project manager, making it a foundational document produced during initiation. It records high-level scope, objectives, stakeholders and constraints, and is a standard artefact in project management documentation.
- ✓
Risk register
Why this is correct
The risk register catalogues identified risks with their probability, impact, priority scores, owners and planned responses. It is maintained throughout the project lifecycle and is a standard project management document, distinct from schedules, charters and status reports.
- ✗
Server configuration file
Why it's wrong here
A server configuration file is a technical operational artefact produced by infrastructure teams, not project management documentation like the charter, business case or risk register. It tempts because projects generate technical files, but the question concerns management documents, and configuration files fall outside that category.
- ✓
Scope statement
Why this is correct
The scope statement documents the agreed deliverables, boundaries, assumptions and acceptance criteria, forming the baseline against which scope changes are assessed. It is a core project management document, produced during planning and revised through formal change control.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.