mediumMultiple Select
PK0-005 Practice Question: Which TWO documents should be finalized during…
Which TWO documents should be finalized during project closure?
⚠ Common exam trap
The PK0-005 exam often tests the distinction between documents created in different project phases, so candidates mistakenly select the WBS or risk register because they are heavily used during execution, but they are not finalized during closure.
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
✓
Final project report
The final project report (B) is a key closure document that summarizes project performance, deliverables, and lessons learned, providing a formal record for stakeholders. Lessons learned (C) captures what went well and what could be improved, which is essential for organizational process improvement and future project planning.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Work breakdown structure
Why it's wrong here
The work breakdown structure is created during planning and drives execution; closure finalises acceptance documentation and lessons learned rather than the WBS. It is tempting because the WBS defines deliverables being verified, but it is a planning baseline, and closure instead confirms the resulting product was accepted.
- ✓
Final project report
Why this is correct
The final project report formally records scope, deliverables, variances and acceptance, providing the sponsor's authorisation to close. Finalising it during closure satisfies the requirement to document final performance against baselines and transition the product to operations.
- ✓
Lessons learned
Why this is correct
Lessons learned captures knowledge gained throughout the project lifecycle, documenting what succeeded and what failed for future reference. Finalising this during closure satisfies the requirement to formally record retrospective insights before the team disbands, ensuring organisational knowledge persists beyond project completion.
- ✗
Project charter
Why it's wrong here
The project charter is authorised at initiation and already baselined, so closure finalises acceptance documentation and lessons learned instead. It is tempting because the charter is a governing document, but it is an input to closure, not an output finalised there; changes to it would reopen scope, not close the project.
- ✗
Risk register
Why it's wrong here
The risk register is maintained throughout the project and its residual risks are transferred or closed via the final report, not finalised as a closure deliverable. It is tempting because risks must be addressed before closure, but the register is a living execution artefact, whereas closure finalises acceptance and lessons-learned documents.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.