Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 15 of 204
Free Preview · 204 of 677 · questions 1–204 of 677 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The correct answer is: B. Defect log Explanation: During the stabilization phase, when an end user reports a bug compromising data integrity, the project manager needs to track and manage this defect effectively. A defect log is specifically designed to: Record details about software bugs and defects Track their status (open, in progress, resolved) Assign responsibility for fixes Monitor severity and priority This helps ensure that the defect is addressed systematically.
ANSWER A: When you see “MOST likely use” in the context of PMBOK®: "Issue log" is the recognized, broad repository for ANYTHING requiring resolution. "Defect log" is not a PMBOK® artifact, even though it’s common in software development. "Change log" tracks the status of change requests once they’ve been formally submitted and accepted or rejected. "Task board" (or Kanban board) can be used in Agile or hybrid environments, but it’s more of a visual management tool for tasks and workflow—less about formally registering a problem that requires escalation or resolution in a PMBOK® sense. Hence, from the PMI/PMBOK® perspective, “Issue log” is the correct place to record any new bug or data‐integrity problem that arises.
A would be for issues that arise in a project over all B is specifically for software projects, which the question states that it is.