ISC · Information Systems and Data Management · 9 practice questions
Emergency Change Post-Implementation Review and Approval
Emergency changes still require prompt documentation, independent validation, and retrospective approval. Below, a billing outage timeline shows why restoring service does not complete change control.
Try one first
Hint
Focus on the control that should happen after an emergency change when normal pre-implementation steps were skipped.
Answer D. Emergency changes may need to be implemented quickly, but they should not bypass change management entirely. A strong emergency change process requires the change to be documented, reviewed after implementation by an independent person, and formally approved retrospectively. This compensates for the pre-implementation controls that were skipped because of the outage.
Why not A: User confirmation that the service is functioning is useful evidence that the fix worked, but it does not replace formal change documentation, independent review, and managerial approval. Relying solely on user sign-off fails to provide an audit trail and control over emergency changes.
Why not B: Updating records and stabilizing the system are important, but allowing the same developer to close the process without independent review leaves risks unaddressed. An independent post-implementation review and formal retrospective approval help ensure the change was appropriate and properly controlled.
Why not C: Assuming the emergency status removes the need for follow-up controls is a common mistake. Emergency changes may accelerate implementation but still require post-implementation documentation, testing, and review to ensure the change is correct and authorized.
The timeline
- Day 0, 11:00 p.m.The billing system fails.
Company policy permits emergency developer deployment with verbal IT manager authorization. It requires documentation, independent review, and retrospective approval by the next business day.
- Day 0, 11:10 p.m.The authorized developer deploys a fix and billing resumes.
Restored service does not establish that only the intended code reached production or that billing results are correct.
- Day 0, immediately after deploymentRecord the emergency change and preserve evidence.
Record the actual authorization and deployment times. Retain the production change, logs, and available test results. Do not backdate approval.
- Next business day, morningAn independent reviewer verifies the deployed code.
Compare the production version with the emergency ticket, tested fix, and source-code record. The implementing developer must not be the sole reviewer.
- Next business day, after code verificationIndependently validate billing results.
Review testing evidence, perform needed validation, and check affected billing output for unintended errors. User confirmation alone is insufficient.
- Next business day, after validationObtain formal retrospective approval.
The CAB reviews the emergency justification, exact change, testing evidence, and independent findings. Approval must address the specific change, not merely acknowledge the outage.
- Next business day, before closureDocument the decision and complete the change record.
If independent validation supports the fix and residual risk is acceptable, retain it with formal approval. If validation identifies unacceptable problems, assess corrective action or controlled rollback.
Key points
- Remember: A working system proves service was restored, not that the exact production change was independently verified and approved.
- Follow the emergency policy's deadline; next-business-day review is this example's requirement, not a universal deadline.
- Documentation, independent validation, and formal approval serve different purposes; none replaces the others.
How the exam traps you
- Close the change because users confirm billing works. Use user confirmation as evidence, then complete independent validation and retrospective approval.
- Let the implementing developer perform the final review and approval. The developer supplies evidence; independent personnel validate the change and appropriate personnel approve it.
- Automatically reverse the fix because advance approval was bypassed. Assess the change and its results before deciding whether rollback is needed.
Question 2
Hint
Separate the change category decision from the control-exception decision: ask what makes a change standard versus emergency, and then ask which controls may be modified rather than eliminated.
Answer A. This is an emergency change because the change is needed to restore critical processing before normal approval channels can operate, and it is not a standard change because it is neither preapproved nor repeatable. In a genuine emergency, some normal sequencing and segregation controls may be overridden as an exception, but compensating controls (documented emergency authorization, at least limited testing, and timely independent postimplementation review) are required. Testing and documentation should still occur to the extent feasible rather than being abandoned.
Why not B: Tempting because the change restores service, but standard changes must be preapproved, repeatable, and low-risk. A one-time code fix during an outage is not a preapproved repeatable standard change simply because it returns existing functionality.
Why not C: While segregation of duties is an important control, an absolute ban during an emergency can cause greater business harm. Emergency procedures exist to allow controlled exceptions with compensating controls (authorization and independent review), not to require waiting until normal staffing is restored.
Why not D: Emergency procedures permit compressed sequencing, but they do not justify skipping all pre-release controls when some authorization and limited testing are feasible. Permitting at least documented emergency authorization and evidence of limited testing before migration reduces avoidable risk.
Question 3
Hint
Consider the difference between preventing an unauthorized change and detecting one after the fact. When an emergency hotfix has already been applied without full process, focus on what compensating control most directly addresses the risk that untested code is now in production.
Answer C. Emergency hotfixes can be applied to restore service, but untested production changes must be independently validated and documented afterward. An immediate independent review and controlled testing with a tested rollback plan confirm the fix and protect availability. Requiring post-implementation CAB review and tightening developer production access addresses both the technical risk and the control breakdown.
Why not A: Tempting because the policy permits post-implementation CAB review, but retroactive paperwork alone fails to verify the safety of an untested production change and leaves the access-control failure unaddressed.
Why not B: Tempting because restoring an approved state reestablishes compliance, but an immediate rollback can reintroduce the outage if the hotfix was necessary; validation and a controlled rollback plan should precede reversion.
Why not D: Tempting as a deterrent, but punitive action before a technical assessment and due HR process is premature; the immediate priority is to confirm service stability and fix the process and access control failures.
Question 4
Hint
Focus less on whether emergency changes are allowed and more on what independent control evidence exists after the normal sequence is bypassed.
Answer C. Emergency changes can justify an abbreviated workflow, but when the same developer can alter production directly and there is no timely independent approval or validation, the risk of unauthorized, untested, or incomplete changes increases. Next-day ticket completion and weekly CAB review are useful retrospective controls but do not ensure immediate validation or that production code matches the repository. The missing independent comparison between production and the repository further weakens version integrity and the audit trail.
Why not A: This is tempting because emergency processes commonly allow retrospective review; however, retrospective documentation and weekly reviews do not substitute for timely independent approval or immediate validation, and they do not guarantee that production and repository code are consistent.
Why not B: This distractor appeals to candidates who conflate operational speed with control effectiveness. In fact, using a release administrator to deploy changes is typically a segregation-of-duties control that reduces the risk of unauthorized code reaching production and is not the primary weakness here.
Why not D: This choice sounds risk-based but is wrong because restricting the account's scope does not fix the core control gap: direct developer access to production without timely independent validation and without reconciling production code to the repository still leaves significant audit and integrity risks.
Question 5
Hint
Think about how emergency changes differ from normal changes: the timing of control activities may shift, but the control itself should still happen.
Answer B. Emergency changes may be implemented before normal approval steps when immediate action is necessary, but they are not exempt from change management. A prompt retrospective emergency change review should be performed as soon as practicable after implementation and include documentation, appropriate approval, and verification of testing and migration details to preserve accountability while addressing urgent operational needs.
Why not A: This is tempting because it acknowledges follow-up, but it wrongly ties documentation and approval to a later emergency or to whether an error later appears; retrospective approval and documentation should occur promptly after the emergency change regardless.
Why not C: Annual ITGC assessments review whether controls worked over time but do not replace timely approval and documentation of individual emergency changes; waiting for an annual assessment would leave the change undocumented for too long.
Why not D: Bundling routine fixes into scheduled releases is common, but an emergency change requires its own prompt retrospective review; delaying documentation and approval until the next release would leave the production change insufficiently authorized and documented.
Question 6
Hint
Look for the situation where normal change controls may be bypassed only temporarily, and only with compensating controls still in place.
Answer A. This describes a narrow emergency exception where bypassing normal segregation of duties can be acceptable to restore critical service. Even in an emergency, the change should be documented, given explicit temporary authorization, and subject to prompt post-implementation review as a compensating control. Emergency handling replaces normal preimplementation controls with documented compensating controls rather than eliminating control requirements.
Why not B: Small or cosmetic changes can still introduce issues and are normally subject to the change-management process; a developer should not unilaterally bypass approvals or independent migration without an approved, documented exception process.
Why not C: Business pressure alone does not constitute a technical emergency that justifies bypassing controls. Without an approved emergency process and compensating controls, skipping testing and approvals is inappropriate.
Why not D: Missing a release window is an operational scheduling issue, not an emergency. Even if tested, the approved release and migration procedures (including independent migration) should be followed unless an authorized exception process is used.
Question 7
Hint
Think about what should still happen even when a change is urgent enough to qualify as an emergency.
Answer B. Emergency change paths are intended for urgent situations, but they do not eliminate core controls. The request should be documented, receive expedited approval, and include as much testing as is practical with evidence retained. Segregation of duties should be preserved by having an authorized person independent of development promote the code to production so timely response is balanced with control.
Why not A: This is tempting because of urgency, but allowing the developer to bypass approval and segregation increases the risk of unauthorized or faulty changes. Speed is important, but controls like approval and independent promotion reduce the chance of making the outage worse.
Why not C: This distractor overstates controls: well-designed change management includes an emergency process for urgent issues. Saying changes should 'never' occur outside scheduled releases is unrealistic and would leave the organization unable to respond to critical outages.
Why not D: Completing testing and approvals only after implementation treats preventive controls as paperwork. Testing and approval are intended to reduce the chance of further failures; retroactive documentation does not provide the same protection.
Question 8
Hint
Focus on what an emergency change may bypass temporarily versus what the organization still must do afterward to restore control.
Answer A. Emergency changes can be necessary to restore critical services, but they require compensating controls afterward. The best action is an independent postimplementation review to reconstruct the production change, evaluate any impact on data and processing, obtain after‑the‑fact authorization, and ensure any permanent correction is rebuilt, tested, and migrated through the normal change-management process. That approach closes the control gap without causing unnecessary operational disruption.
Why not B: This overstates the exception: retrospective documentation and approval are required, but emergency status does not permanently exempt a change from independent verification, testing evidence, or proper promotion of any enduring fix.
Why not C: Post-hoc testing may help assess the technical fix, but it does not by itself reconstruct exactly what was changed in production, provide independent verification of data integrity, or substitute for formal retrospective approval and proper promotion of a permanent solution.
Why not D: Automatic rollback would cause unnecessary disruption given the service is stable and no immediate legal/safety rollback requirement exists; the appropriate control response is a documented independent review and formal remediation, not an immediate suspension of operations.
Question 9
Hint
Think about what should happen after an emergency change skips the normal pre-approval path.
Answer C. Emergency changes may bypass normal pre-change steps, but they still require prompt follow-up controls. Those controls typically include documentation of the change, retrospective authorization, and a post-implementation review of what was changed and how it was tested to ensure no new risks were introduced. This preserves accountability while recognizing the operational need to restore service quickly.
Why not A: Backdating approvals creates a false audit trail and defeats controls. The correct approach is transparent exception handling with retrospective approval and review, not falsifying records.
Why not B: Tempting because service was restored, but success does not eliminate the need for change-management controls. Emergency changes still require documentation, retrospective approval, and review to detect errors or unintended side effects.
Why not D: Automatic rollback can cause unnecessary disruption if the emergency change correctly resolved the outage. The priority is to apply proper post-implementation controls and assess whether rollback is needed based on the review, not to assume reversal is always required.
Common questions
When should an emergency change receive post-implementation review?
As soon as practicable after implementation, within the emergency policy's deadline. In this example, the policy requires review and retrospective approval by the next business day.
Is CAB approval enough after an emergency change?
No. A change advisory board (CAB) review that checks only paperwork or service restoration does not verify the deployed code. Independent validation must establish what reached production and whether it produced the intended results.
Must an emergency change without advance approval be rolled back?
No. Independently validate the change and its results and assess the risk. A stable fix within acceptable risk need not be rolled back merely because normal advance approval was bypassed; complete the required retrospective review and approval.
Watch it solved
A full CPA ISC task-based simulation on Change management, worked step by step.
Change Management: Approval & Segregation | CPA ISC TBS on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Change management
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.