Which Tool Should the PM Use First for Testing Bugs?
During the testing process, testers have found multiple bugs that could jeopardize the project commitment date. Which of the following tools should the project manager use first to update the findings?
Community Votes
60% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests your ability to differentiate between pre-existing problem registers and phase-specific tracking tools when bugs directly threaten project deadlines.
This question evaluates the distinction between technical tracking artifacts and project management registers when handling testing-phase defects. Community discussion emphasizes that while developers use technical logs, the project manager must follow standardized documentation protocols to maintain project control.
Candidates frequently choose the Issue Log because it tracks project-level problems, failing to recognize that the Defect Log is the designated primary tool for capturing and triaging bugs discovered during active testing.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The Defect Log serves as the primary repository for recording, categorizing, and tracking bugs identified during the testing lifecycle. Since the scenario explicitly mentions findings during the testing process, logging them here first ensures accurate technical classification and prioritization. This initial step prevents premature escalation and maintains clear accountability between quality assurance and project management teams.Why the Other Options Are Wrong
A Change Log documents approved modifications to baselines rather than initial bug discoveries. The Risk Log tracks uncertain future events, whereas these bugs have already materialized into concrete problems. Although the Issue Log monitors project obstacles, it is generally updated after initial technical validation, making it a secondary step for the project manager.Community Comment Notes
Several examinees debate whether the PM should skip technical logs and jump straight to the Issue Log. Comment [4] accurately points out that defect logs contain technical severity metrics managed by developers, while PMs focus on schedule impacts in issue logs. Despite this valid distinction, CompTIA expects candidates to prioritize the Defect Log as the immediate action for testing-phase findings, confirming option A as the best choice.Exam Strategy
Always map the scenario's phase to the correct tracking artifact; testing-phase bugs belong in the Defect Log first, regardless of their potential schedule impact. Reserve Issue and Change logs for when technical defects have been validated and require formal project baseline adjustments.
Related Analysis
Practice All PK0-005 Questions
Access 102 questions with complete answers and detailed explanations.
View Full PK0-005 Practice Test →