mediumMultiple Choice
PK0-005 Practice Question: At the end of a project phase, the team holds a…
At the end of a project phase, the team holds a meeting to discuss what went well and what could be improved. Which document is produced from this meeting?
⚠ Common exam trap
It's easy for candidates to confuse the phase-end meeting with a status meeting and select 'Status report,' not realizing that the specific purpose of the phase-end meeting is to capture lessons learned, not just report current status.
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
✓
Lessons learned
The meeting at the end of a project phase is a retrospective, specifically designed to capture what went well and what could be improved. The formal document produced from this meeting is the lessons learned document, which records insights and recommendations for future phases or projects. This aligns with the PMI's definition of lessons learned as a key output of the project's monitoring and controlling processes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Lessons learned
Why this is correct
Lessons learned captures the retrospective discussion of what went well and what could be improved, documenting insights for future phases and projects. It is the standard output of a phase-end review, feeding organisational process assets.
- ✗
Risk register update
Why it's wrong here
A risk register update records identified risks, their analysis and responses; it is not the output of a lessons-learned discussion, which captures successes, failures and recommendations for future phases. It is tempting because retrospectives can surface new risks, and a register update would be correct when a review identifies or reassesses risks.
- ✗
Project closure report
Why it's wrong here
A project closure report is produced when the entire project, not a single phase, is formally closed; it confirms deliverable acceptance and releases resources. It is tempting because both documents are created at a boundary, and a closure report would be correct at final project completion rather than a phase-end review.
- ✗
Status report
Why it's wrong here
A status report communicates current progress, schedule and budget performance to stakeholders during execution; it does not record retrospective findings about what went well or could improve. It is tempting because both are periodic documents, and a status report would be correct for routine progress communication, not lessons learned.
Go deeper
Related to this question
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 →
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.