PK0-005 · Question #248
During the execution phase, a new PM was assigned to a project. The PM received a request to add new functionality to the system that is being developed. While the PM was conducting a preliminary…
The correct answer is D. Change log. The change log (also called a change register) is a formal record of all change requests submitted throughout the project, including their status - approved, rejected, deferred, or pending. If this functionality was previously submitted and rejected during planning, that…
Question
During the execution phase, a new PM was assigned to a project. The PM received a request to add new functionality to the system that is being developed. While the PM was conducting a preliminary review with the team, the technical lead highlighted that this functionality request was rejected during the planning phase. Which of the following documents is the best source for the PM to use to confirm this assertion?
Options
- AIssue log
- BScope statement
- CRisk report
- DChange log
How the community answered
(32 responses)- A3% (1)
- B13% (4)
- C6% (2)
- D78% (25)
Explanation
The change log (also called a change register) is a formal record of all change requests submitted throughout the project, including their status - approved, rejected, deferred, or pending. If this functionality was previously submitted and rejected during planning, that decision would be documented in the change log with a date and rationale. The issue log (A) tracks project issues, not change requests. The scope statement (B) describes what is in scope but does not log the history of rejected changes. The risk report (C) tracks risks, not change decisions. The change log is the definitive document for confirming whether a specific change was previously reviewed and rejected.
Topics
Community Discussion
No community discussion yet for this question.