PK0-005 Tools and Documentation Practice Question
A project manager is closing out a fixed-price contract. The vendor has completed all deliverables, and the PM must formally document that the work was completed satisfactorily so that final payment can be released. Which document should the PM prepare and have signed?
⚠ Common exam trap
A common mix-up: candidates confuse the document that defines the work (the SOW) with the document that confirms the work is done (formal acceptance).
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
✓
Formal acceptance / sign-off document
Formal acceptance is the documented confirmation that contract deliverables meet requirements and is required before final payment and contract closure. The SOW defines scope, the change log tracks modifications, and the lessons learned register captures knowledge; none of these certify completion or authorize release of final payment for the fixed-price vendor.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Procurement statement of work (SOW)
Why it's wrong here
The SOW defines the deliverables, scope, and acceptance criteria before work begins; it is an input to the contract, not a post-completion acceptance record. It cannot certify that the vendor finished satisfactorily, so it would not trigger final payment release in this fixed-price closure scenario.
- ✗
Lessons learned register
Why it's wrong here
The lessons learned register captures knowledge for future projects. While it is updated during closure, it does not document the vendor's satisfactory completion or authorize payment. Preparing it does not satisfy the requirement to formally accept the deliverables and close the procurement in this scenario.
- ✗
Change request log
Why it's wrong here
The change request log tracks proposed and approved modifications to scope, schedule, or contract terms. It does not verify that the vendor's deliverables are complete or satisfactory, so it cannot serve as the acceptance artifact needed to authorize final payment in this fixed-price contract closure.
- ✓
Formal acceptance / sign-off document
Why this is correct
A formal acceptance document signed by the authorized stakeholder confirms the deliverables met the agreed criteria and closes the contract. It is the standard control for releasing final payment and completing procurement closure, which is exactly what the PM needs here after the vendor finished all fixed-price deliverables.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.