PK0-005 Project Life Cycle Practice Question

During project closure, which three activities should be performed? (Select THREE)

⚠ Common exam trap

PK0-005 often tests the confusion between process group activities, tricking candidates into selecting planning or initiating tasks (like charter or risk register) as closure activities.

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

✓

Obtain formal acceptance

Option A (Obtain formal acceptance) is correct because project closure requires the customer or sponsor to formally sign off on the deliverables, confirming they meet requirements before the project can be officially closed. Option B (Conduct lessons learned) is correct because closure includes capturing what went well, what did not, and recommendations so future projects benefit from the experience. Option D (Archive project documents) is correct because closure involves storing final artifacts, contracts, and records in the organizational knowledge base for audit, compliance, and historical reference. Option C (Develop project charter) is incorrect because the charter is created during initiation to authorize the project, not at closure. Option E (Create risk register) is incorrect because the risk register is built and maintained during planning and execution, and closure instead focuses on closing out remaining risks.

Answer analysis

Option-by-option breakdown

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

✓
Obtain formal acceptance
Why this is correct
Formal acceptance confirms the customer or sponsor agrees the deliverables meet requirements, authorising closure. Without it the project cannot be signed off or the product transitioned, so obtaining it is a mandatory closure activity alongside handover and lessons learned.
✓
Conduct lessons learned
Why this is correct
Conducting lessons learned captures what succeeded and failed, feeding improvements into future projects. It is a standard closure activity, alongside finalising documentation and releasing resources, directly satisfying the stem's requirement for activities performed during project closure.
✗
Develop project charter
Why it's wrong here
Closure covers final deliverable acceptance, lessons learned, resource release and administrative sign-off; the charter is authorised during initiation to formally start the project. It is tempting because both are project documents, but the charter precedes execution and cannot be produced at closure.
✓
Archive project documents
Why this is correct
Archiving project documents preserves the management and product records for audit, reference and future projects once the team disbands. It satisfies closure's requirement to capture and retain project information before releasing resources, complementing formal acceptance and lessons learned.
✗
Create risk register
Why it's wrong here
Closure requires verifying deliverables, archiving records, releasing the team and capturing lessons learned; the risk register is created during planning and maintained throughout execution. It is tempting as a core project artefact, but risks are closed or transferred earlier, not newly registered at closure.

Go deeper

PK0-005 Project Life Cycle Practice Question

Why each option matters

Option-by-option breakdown

Related to this question