True or false: A change-request log provides a complete history of a request as long as it records each status label, even if it omits when and by whom the status changed.
4 Change Logs and Audit Trails Online Quiz Questions
Use this free practice quiz with 20 questions to review 4 Change Logs and Audit Trails, test your knowledge, and prepare for your next test or exam.
True or false: If a change-request record needs correction, the earlier entry or system history should be preserved and the correction documented with its author, date, and reason.
- A
True
- B
False
Select all the information that belongs in a change request's decision record.
- A
The decision outcome
- B
The requester's preferred release date, whether or not it affected the decision
- C
The decision date and decision-maker or approver
- D
The organization's record-retention schedule
- E
The rationale and any conditions or follow-up actions
Select all the practices that help control and protect change-request records.
- A
Identify who may create, approve, or change records.
- B
Restrict access appropriately.
- C
Allow anyone to alter records without recording the change.
- D
Back up records.
- E
Retain records according to the organization's rules.
What value should every change request have so its record can be distinguished from other requests? Enter the concise name of the value.
What kind of identifiers should link supporting documents and related records to a change request? Enter the two-word phrase.
When correcting a change-request record, preserve the earlier entry and document the of the correction.
If a request is deferred, record the reason and, when known, the condition or date for .
A change request was approved and implemented, but a later reviewer must verify how it reached closure. What records should the team preserve to let the reviewer reconstruct the request's path and confirm its completion?
A team discovers that several open requests in its log no longer reflect their actual progress. Which process change best addresses this problem?
- A
Assign someone to update the log and periodically reconcile open requests with their actual status.
- B
Update the log only when a request is first submitted.
- C
Let each requester decide whether status changes are recorded.
- D
Stop checking open requests once they have a unique identifier.
Which date-related request detail records when a change request was submitted?
What information should accompany a rejection so the requester and later reviewers can understand the outcome?
A change coordinator updates a request from “Submitted” to “Under review.” Which entry best makes this transition traceable?
- A
The new status and the request title
- B
The new status, a timestamp, and the responsible person or workflow
- C
The new status and the requester's name only
- D
The new status and an estimate of the remaining work
The example status names are mandatory for every organization that maintains a change log.
- A
True
- B
False
A team defers a change request because it depends on another project. What should the team record to make the deferral useful?
- A
Mark it “Deferred” and remove the request from the log
- B
Record only the name of the person who deferred it
- C
Record the reason and, if known, the condition or date for reconsideration
- D
Change its status to “Rejected” until it is ready to be reviewed
A request has been approved, but work has not started. How should its record represent this situation?
- A
Show the request as rejected because implementation has not begun
- B
Record the approval decision while showing that implementation has not yet occurred
- C
Show the request as implemented because it has been approved
- D
Replace the approval decision with the current implementation status
A change requires approval from both technical and operations reviewers. Which recordkeeping approach best preserves the approval history?
- A
Keep only the final approval and discard earlier responses
- B
Record the number of approvals without recording who acted
- C
Retain each approval or rejection, its actor, comments, and time
- D
Record only objections, since approvals are implied by the final result
A reviewer finds an error in a recorded decision. What is the best way to correct the record while preserving its auditability?
- A
Preserve the earlier entry and record who made the correction, when, and why
- B
Replace the old information without noting that it changed
- C
Delete the entire request and create a new one
- D
Change the information and record only the date of the change
A change has been implemented, but its required verification result has not been recorded. What should the change owner do?
- A
Close it as soon as approval is granted
- B
Keep it open until required implementation and verification records are attached
- C
Close it when implementation begins, then add evidence if requested
- D
Close it once the owner reports completion, even if verification is pending
Which record set best allows a reviewer to reconstruct a change request's path from submission through closure without relying on memory?
- A
Keep only the final status and the request owner's name.
- B
Retain approvals but discard the original request and implementation evidence.
- C
Store related documents separately without linking them to the request.
- D
Preserve the original request, relevant impact-analysis material, approvals and comments, status transitions, implementation evidence, and closure record, linked to the request by stable identifiers.
Related study packs and tools
- Flashcards
1 Project Governance and Decision Rights
Learn how project governance assigns decision authority, sets boundaries, escalates issues, and records decisions.
- Quiz
1 Project Governance and Decision Rights
A 14-question quiz on project governance, decision authority, escalation, and decision records.
- Flashcards
2 Governance Roles and Accountability
Learn how project governance assigns decision-making authority, accountability, delivery duties, oversight, and escalation paths.
- Study guide
2 Governance Roles and Accountability
Learn how project governance assigns decision authority, accountability, delivery responsibilities, oversight, and escalation across project roles.
- Study guide
3 Analyzing Stakeholders
Learn how to assess stakeholders, select tools for comparing them, and keep judgments evidence-based, validated, and current.
PMP Stakeholder ManagementUpdated - Flashcards
3 Escalation Paths and Issue Resolution
Learn how to classify project matters, set escalation routes and thresholds, and make escalations actionable.
- Quiz
3 Escalation Paths and Issue Resolution
A medium-difficulty quiz on applying escalation routes, decision rights, thresholds, and response practices in project issue resolution.
- Study guide
3 Escalation Paths and Issue Resolution
Learn how to distinguish project risks, issues, conflicts, and decisions, then design and use escalation routes that support timely, accountable resolution.
- Study guide
4 Planning and Practicing Stakeholder Engagement
Learn how to plan stakeholder engagement, choose appropriate participation methods, build trust, address disagreement, and adapt a project’s approach as needs and circumstances change.
PMP Stakeholder ManagementUpdated - Quiz
4 Project Oversight and Control
A medium-difficulty quiz on applying project oversight, performance monitoring, stage-gate decisions, change control, escalation, and corrective action.
- Study guide
4 Project Oversight and Control
Learn how project teams monitor performance, make formal decisions at stage gates, control changes, and respond to issues through corrective action and escalation.
- Quiz
6 Quality Planning and Delivery
Apply core quality-planning and delivery practices to project scenarios, including acceptance criteria, assurance and control, defect response, and evidence-based improvement.
PMP ProcessUpdated