easyMultiple Choice
Project Charter: Authorization and Purpose
Which of the following documents formally authorizes the project and provides the project manager with the authority to apply organizational resources?
Quick Answer
The answer is the project charter. This document formally authorizes the project’s existence and grants the project manager the authority to apply organizational resources, as it is issued by the project sponsor or initiator. Without a signed charter, the project manager lacks the official mandate to commit funds, assign personnel, or make binding decisions, which is why the project charter authorization purpose is to establish that critical partnership between the performing and requesting organizations. On the CompTIA Project+ PK0-005 exam, this concept tests your understanding of the initiating process group, and a common trap is confusing the charter with the project management plan or a business case—remember, only the charter provides the formal go-ahead. A useful memory tip: think of the charter as the project’s “birth certificate” and the project manager’s “power of attorney” rolled into one.
⚠ Common exam trap
The PK0-005 exam often tests the distinction between the project charter (which authorizes the project and grants authority) and the project plan (which details execution), leading candidates to mistakenly select the project plan because it is 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 formal document that authorizes the project's existence and provides the project manager with the authority to apply organizational resources to project activities. It is issued by the project sponsor or initiator and establishes a partnership between the performing and requesting organizations. Without a signed charter, the project manager lacks the official mandate to commit resources or make binding decisions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Scope statement
Why it's wrong here
The scope statement defines boundaries, deliverables and acceptance criteria, but grants no authority over organisational resources. It is tempting because it is a foundational planning document, and it would be correct when documenting what is in and out of scope after the charter is approved.
- ✗
Business case
Why it's wrong here
A business case justifies the project’s viability and expected benefits, but it does not formally authorise the project or grant the project manager authority to apply resources. The project charter fulfils that role by providing the official mandate and spending delegation. This option is tempting because the business case is often the preceding document that triggers charter approval, making it seem as though it carries the same authorising weight.
- ✗
Project plan
Why it's wrong here
A project plan describes how the work will be executed, scheduled and controlled; it is produced after authorisation, not as the authorising instrument. It is tempting because it governs delivery, and would be the right artefact once the charter exists and baselines are being set.
- ✓
Project charter
Why this is correct
The project charter formally authorises the project and grants the project manager authority to apply organisational resources. It is issued by the sponsor, names the project manager, and documents high-level scope, objectives and constraints. This directly satisfies the stem's requirement for both formal authorisation and resource-application authority, unlike subsidiary plans or registers.
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 →
Same concept, more angles
2 more ways this is tested on PK0-005
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. 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?
easy- A.Project management plan
- B.Risk register
- C.Work breakdown structure
- ✓ D.Project charter
Why D: 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.
Variation 2. During project planning, the project team identifies several assumptions and constraints. Which document is the most appropriate place to record these items?
easy- ✓ A.Project charter or project management plan
- B.Issue log
- C.Communication plan
- D.Risk register
Why A: Assumptions and constraints are foundational elements that shape project planning and execution. The project charter formally authorizes the project and often captures high-level assumptions and constraints, while the project management plan details how the project will be executed, monitored, and controlled, including a more comprehensive list. Recording them in these documents ensures they are visible to all stakeholders and integrated into the project's baseline.
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.