PK0-005 Tools and Documentation Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Business case

  Why it's wrong here

  The business case justifies the investment by comparing benefits, costs and risks, but it is an input that precedes approval and carries no authorising authority. It is tempting because it triggers the project, yet the project charter is what formally authorises the work and names the project manager.

• ✓

  Project charter

  Why this is correct

  The project charter formally authorises the project's existence and explicitly identifies the assigned project manager, conferring authority to proceed. It satisfies both constraints in the stem, whereas subsidiary documents such as the project management plan assume authorisation already exists.

• ✗

  Project management plan

  Why it's wrong here

  The project management plan describes how the project will be executed, monitored and controlled; it is produced after authorisation and does not grant it. It is tempting as the overarching governing document, yet the project charter is the artefact that formally authorises the project and identifies the project manager.

• ✗

  Scope statement

  Why it's wrong here

  The scope statement documents deliverables, boundaries and acceptance criteria; it neither authorises the project nor names the project manager. It is tempting because it is a foundational planning document, but authorisation belongs to the project charter, which the sponsor signs to formally empower the manager.