ISC · Information Systems and Data Management · 8 practice questions
Emergency Change Controls Before Production Deployment
Emergency changes accelerate required controls rather than eliminate them. Below: follow an urgent database patch from incident detection through approval, feasible testing, backup, rollback planning, deployment, and review.
Try one first
Hint
First decide whether this qualifies as an emergency; then identify which authorizations and pre-change safeguards your policy requires before an expedited production change.
Answer A. Production data is actively being corrupted, so this meets the emergency-change criteria, but the organization's emergency process still applies. That process requires advance ECA authorization and pre-change safeguards (a current full production backup and a documented rollback plan) and notifications before expedited deployment. Requiring those items preserves recoverability and control while allowing rapid remediation; the change is then subject to post-implementation CAB review for governance.
Why not B: Tempting because speed seems critical and the patch worked in staging, but staging does not fully mirror production and there is no recent backup or rollback plan. Approving deployment without ECA authorization and pre-change safeguards violates policy and risks worsening data loss or unrecoverable corruption.
Why not C: Tempting because full regression testing increases confidence, but insisting on complete regression and full CAB approval before acting would delay remediation and allow ongoing production corruption when the policy provides an expedited emergency path. The correct approach uses the emergency process with required safeguards, not an avoidable full-delay.
Why not D: Tempting as a pragmatic compromise, but an after-the-fact backup cannot recover data already lost or corrupted prior to or during deployment. Allowing deployment without prior ECA authorization and without a pre-established rollback plan still violates the emergency-change controls and increases risk.
The timeline
- Incident detectionA database bug is actively corrupting customer records.
The DBA has prepared a patch. Waiting increases harm, so use the company's emergency change path rather than wait for routine CAB approval.
- Before deployment: requestOpen the emergency change ticket.
Record the corruption, business impact, proposed patch, and reason the change cannot wait.
- Before deployment: authorizationObtain approval from the designated Emergency Change Authority.
Record the authorization. The DBA's request for immediate deployment does not replace the approval required by policy.
- Before deployment: testingReview staging results and complete feasible expedited testing.
The patch passed staging, but data volume and configuration differ from production. Document test evidence and remaining risks.
- Before deployment: recoveryTake a current full production backup and document the rollback plan.
The existing full backup is 36 hours old. This company's emergency policy requires a current full backup and documented rollback steps before implementation.
- Before deployment: notificationNotify the business owner and security.
Record the required notifications in the emergency ticket before releasing the patch.
- DeploymentHave available operations personnel deploy the patch.
Use controlled production access. Monitor results and use the documented rollback plan if the patch causes unacceptable problems.
- After deploymentComplete the change record and post-implementation CAB review.
Review authorization, testing, implementation, and results. Retrospective review does not replace required predeployment authorization or recovery safeguards.
Key points
- Remember: Emergency means an expedited approval path, not permission to deploy first and obtain required approval later.
- The company's policy determines the authorized emergency approver and required safeguards.
- A successful staging test does not remove risks from production differences.
- Operations deployment preserves separation from development but does not replace approval, testing, or recovery safeguards.
How the exam traps you
- Deploy immediately because customer records are already being corrupted. Obtain designated emergency authorization before deployment; urgency does not waive this policy requirement.
- Take the backup and write rollback instructions after the patch succeeds. Prepare both before deployment so recovery is possible if the patch fails.
- Let the DBA deploy because the DBA wrote and tested the patch. Use available operations personnel to deploy through controlled procedures.
Question 2
Hint
Focus on which control objective is most at risk when the same person can create and implement an urgent change with little evidence of review.
Answer B. This is the best answer because even emergency changes should remain subject to controlled procedures, including authorization, appropriate testing, documentation, and postimplementation review. Allowing the developer to move code directly into production with documentation completed later and no required independent review creates a clear change-management weakness. The problem is not that emergency changes occur, but that they bypass essential controls.
Why not A: This may tempt candidates who associate low-risk changes with simplified procedures. However, change management still requires defined approval and documentation, even if the process for standard or low-risk changes is streamlined. The fact pattern's main weakness involves emergency changes bypassing controls, not routine changes being overcontrolled.
Why not C: This is tempting because release windows are a common control in production change management. But genuine emergency changes often must be implemented immediately to restore service or reduce risk. The issue is not the timing of the release window; it is the lack of approval, testing, documentation discipline, and independent oversight around emergency changes.
Why not D: This distractor plays on role confusion. Segregation of duties is important, but it does not mean the security team must perform all production changes. A better control is to require proper authorization, testing, and an independent migration or review process rather than assigning all changes to a different function.
Question 3
Hint
Think about how a strong change management process handles urgent production fixes without abandoning core controls.
Answer B. A sound change-management program includes a controlled emergency change path for urgent issues. That path permits expedited implementation but still requires authorization, as much testing as practicable before deployment, and a documented post-implementation review to restore full controls and document rationale.
Why not A: Tempting because speed matters, but allowing the developer to promote code directly breaks segregation of duties and increases risk. Emergency changes may be expedited, but migration should still be controlled and performed by someone other than the developer when possible.
Why not C: Overly rigid; strong change management does not forbid emergency fixes when business risk requires them. The correct approach is to use a defined emergency process, not automatic delay.
Why not D: Business approval is important but cannot substitute for technical testing, IT authorization, or segregation of duties. Emergency changes still require both business and IT controls to mitigate risk.
Question 4
Hint
Focus on what changes in an emergency process and what controls still must remain in place.
Answer D. Emergency changes do not eliminate change management controls; they modify them. A sound process still requires authorized approval, testing as far as practical, controlled migration, and follow-up review and documentation after implementation. This balances urgency with accountability and reduces the risk of unauthorized or poorly executed production changes.
Why not A: This is tempting because urgency often makes candidates think controls can be skipped temporarily. However, effective emergency change management still requires approval before implementation when feasible and should not rely on unrestricted developer changes directly to production without controlled procedures.
Why not B: This distractor is attractive because business-owner approval is important for change requests. However, business approval alone is not enough; emergency changes also need appropriate IT change authorization, controlled migration, and follow-up review under the formal change process.
Why not C: This choice sounds control-focused, but it ignores the purpose of an emergency change process. When a critical issue needs immediate action, the organization should use its emergency procedures rather than wait for the normal release cycle.
Question 5
Hint
Consider whether the organization has an emergency change procedure and what steps it requires after a critical fix is applied; the best answer both mitigates risk quickly and follows the emergency controls.
Answer D. DeltaTech's emergency change procedure explicitly allows immediate deployment of critical security fixes while preserving control through required after-the-fact documentation and notification. This mitigates the active threat promptly while maintaining accountability and enabling retrospective CAB review.
Why not A: Tempting because it prioritizes stopping exploitation, but it bypasses the organization's emergency change controls; failing to document and notify undermines accountability and prevents the required retrospective review and audit trail.
Why not B: This follows standard procedure but is wrong here because it needlessly exposes systems to an active exploit when an emergency change path exists to address critical vulnerabilities quickly.
Why not C: A partial deployment may leave many systems exposed and still fails to follow the formal emergency change requirements (timely documentation and notification), reducing traceability and control.
Question 6
Hint
Think about how a well-designed change management process handles urgent production fixes without abandoning control.
Answer B. A sound change management process does not abandon controls during an urgent outage; it uses a documented emergency path. The best response is to obtain the required expedited approval, do as much practical testing as time allows, implement the fix, and then complete documentation and a post-implementation review. This approach restores service while preserving accountability and control.
Why not A: Tempting because it prioritizes speed, but skipping the organization's emergency approval process weakens controls and increases risk; approvals and at least minimal testing should occur through the emergency path before deployment when that process exists.
Why not C: This overapplies normal change windows; when an emergency change process exists for urgent service restoration, using it is appropriate to avoid unnecessarily prolonged outages.
Why not D: While the developer may act quickly, unilateral deployment bypasses approvals and segregation-of-duties safeguards; the emergency process preserves rapid response while maintaining accountability.
Question 7
Hint
Think about how good controls handle urgent situations without abandoning approval and documentation.
Answer D. Urgent fixes should not bypass change management entirely. A well-designed process provides an emergency change path that still requires authorization, documented testing to the extent feasible, a clear backout plan if the fix fails, and a post-implementation review to ensure controls remain effective. That approach balances business continuity with control and accountability.
Why not A: This is tempting because speed is important for payroll, but allowing an immediate unapproved production change undermines authorization, testing, and accountability controls. Urgency can justify an expedited emergency process, not bypassing controls entirely.
Why not B: Segregation of duties is important, but transferring coding tasks to operations creates other risks because operations staff typically aren't responsible for making code changes. The appropriate response is to follow the approved emergency change process with proper roles, testing, and oversight.
Why not C: Strictly waiting for the regular release schedule ignores that effective change management includes an emergency option for high-impact issues. Delaying the fix could result in incorrect employee pay and operational harm when a controlled emergency process exists.
Question 8
Hint
Focus on which normal change controls can be abbreviated in a true emergency and which controls still must exist shortly afterward.
Answer D. Emergency changes should permit rapid remediation when delay increases risk, but they do not remove core change-control requirements. The best response preserves expedited authorization while enforcing immediate documentation (ticketing), controlled use of break-glass access, and an independent retrospective review on the next business day to verify authorization, testing, implementation, and outcomes. That combination closes the gaps shown, late ticketing, after-the-fact testing evidence, and missing independent review, without preventing timely emergency response.
Why not A: This is tempting because full CAB approval strengthens governance, but it is wrong: requiring preimplementation CAB approval defeats the purpose of an emergency policy by introducing delays that can worsen exposure. A better control is narrowly defined expedited action with prompt documentation and after-the-fact oversight.
Why not B: This is tempting because stability is a key outcome and speed matters, but it is wrong: a simple stability check does not ensure the change was properly authorized, documented in a timely manner, or independently reviewed. Emergency controls must include prompt logging and independent retrospective assessment, not just a post-hoc stability note.
Why not C: This is tempting because segregation of duties reduces risk, but it is wrong: making independence an absolute precondition for remediation can delay necessary fixes during an active exploit and increase overall exposure. Controlled break-glass access plus rapid independent retrospective review is a more balanced control.
Common questions
Do emergency changes need CAB approval before deployment?
Not under this company's emergency policy. The designated Emergency Change Authority authorizes deployment in advance, and the change advisory board reviews it afterward.
Can an emergency patch be deployed without full production-like testing?
Use feasible expedited testing under the emergency policy. Here, staging differs from production, so document the remaining risk and preserve approval, backup, rollback, and monitoring controls.
Why does an emergency change need both a backup and a rollback plan?
The backup preserves a recovery copy; the rollback plan documents how to back out the change. This company's policy requires a current full production backup and documented rollback steps before deployment.
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.