PK0-005 Practice Question: A project sponsor wants to formally close a…

Answer analysis

Option-by-option breakdown

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

• ✗

  Stakeholder register

  Why it's wrong here

  The stakeholder register records engagement and communication details throughout delivery; it carries no acceptance signatures or completion criteria. It is tempting because closure requires confirming stakeholders were managed, yet the formal sign-off document is the final project report or acceptance form recording the sponsor's approval.

• ✗

  Lessons learned

  Why it's wrong here

  Lessons learned captures knowledge for future projects and is produced during closure, but it does not obtain sign-off. It is tempting because it is a closure output, so candidates associate it with the closing process group; the document actually signed to confirm completion is the final project report or formal acceptance.

• ✗

  Project charter

  Why it's wrong here

  The project charter authorises the project at initiation and records high-level objectives; it is not a closure artefact and cannot confirm deliverables were accepted. It is tempting because it is a formal approved document bearing the sponsor's signature, but that signature starts the project rather than closing it.

• ✓

  Final project report

  Why this is correct

  The final project report summarises scope, schedule, cost and outcome performance, providing the sponsor with documented evidence for formal sign-off. It satisfies the stem's closure requirement, unlike the charter or business case, which belong to earlier phases.