Which Tool Should the PM Use First for Testing Bugs?

PK0-005 By islever Editorial Last updated

Short answer

A Defect log

Question

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?
  1. Defect log Correct Answer
  2. Change log
  3. Issue log
  4. Risk log

Key Takeaways

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.

Common mistake: 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.

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.

Community Votes

A
60%
C
40%

60% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. bigjudy2560 👍 2 Answered A
    this is a defect, not an issue.
  2. 044f354 👍 1 Answered C
    Developers and testers use defect log, which is a software development tool, not a project tool. things like the bug's severity, tracking/naming convention, technical details (like memory bug) etc. The PM uses issue log to track problems that impact the project, like software bugs. things like the existence of the bug, its impact to the project, and some reference to its name/convention. PM does not want technical aspect of the bug. double checked my opinion with perplexity.ai : (A) Defect log ❌ While related, a defect log is more specific to software bugs and may not capture all project-level issues. (B) Change log ❌ A change log tracks approved changes, not potential issues or bugs. (C) Issue log ✅ An issue log tracks problems that could impact project objectives, including bugs affecting the commitment date. (D) Risk log ❌ A risk log is for potential future problems, not current issues already identified
  3. stinkle 👍 1 Answered C
    Issue log is for issues that arise within the project phases that have already happened. A Defect log is for already deployed in prod - products.
  4. 95d3b92 👍 1 Answered A
    The defect log is specifically used to record and track bugs or defects found during the testing phase.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

How to Interpret a Velocity Chart for Project Scheduling?

S-grade

Email Impersonation Attack Scenario: Best Classification?

S-grade

Which Document Defines Product Success Criteria?

S-grade

What Should a Project Manager Do When Stakeholders Decline the Kickoff?

S-grade

Practice All PK0-005 Questions

Access 102 questions with complete answers and detailed explanations.

View Full PK0-005 Practice Test →

← Back to PK0-005 Study Guide