PK0-005 Tools and Documentation Practice Question
A project manager needs to track the status of every project document, including who wrote it, when it was last revised, and who has approved it. Which tool is most appropriate for maintaining this information?
⚠ Common exam trap
The trap here is assuming any project log or register can track documents; only a DMS provides version and approval metadata.
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
✓
Document management system (DMS)
A document management system is purpose-built to store documents with metadata such as author, revision date, and approval status, and to enforce version control. The issue log, risk register, and WBS serve different functions and lack the versioning and approval-tracking capabilities needed to maintain an authoritative index of project documents.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Document management system (DMS)
Why this is correct
A document management system provides version control, check-in/check-out, authorship, revision history, and approval workflow for project documents. It is designed exactly for tracking who created, revised, and approved each artifact, making it the right tool for this scenario's need to monitor document status centrally.
- ✗
Issue log
Why it's wrong here
An issue log records problems, owners, and resolution status. It does not catalog document authorship, revision dates, or approval states. Using it to track documents would leave the PM without a reliable index of version control and approvals, and it would mix active problems with document management records.
- ✗
Risk register
Why it's wrong here
The risk register lists identified risks with probability, impact, and response plans. It does not store document metadata such as author, revision date, or approval status. Employing it for document tracking would omit version control and confuse risk management records with project documentation management.
- ✗
Work breakdown structure (WBS)
Why it's wrong here
The WBS decomposes project scope into deliverables and work packages. It does not manage document versions, authorship, or approvals. While the WBS may reference documents as deliverables, it cannot serve as the repository or index the PM requires for tracking revision and approval status across project artifacts.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.