PracticeISCFree practice exam

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.

The ruleAs soon as practicable after an emergency change, document what changed, preserve testing evidence, independently validate the deployed change and its results, and obtain formal retrospective approval.

Try one first

An organization normally requires documented approval, testing, and separate migration to production for program changes. During Year 1, a critical billing system outage occurs on the last day of the month, and a developer makes an emergency fix directly in production after receiving verbal approval from the IT manager. Assume emergency changes are allowed when service must be restored immediately. Which action should the organization take next to best support effective change management?
Hint

Focus on the control that should happen after an emergency change when normal pre-implementation steps were skipped.

The timeline

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

8 more, each from a different angle

0 of 8 answered · 0 correct

Question 2

A company uses formal change categories of standard, normal, and emergency. At 1:00 a.m. on the last night of the month, a production defect stops invoice generation. Missing the 5:00 a.m. batch would materially delay revenue processing. The proposed fix is a new one-time code change, not a preapproved repeatable script. A staging clone is available for a targeted test, the incident manager and application owner are reachable for emergency authorization, but no separate release administrator is available before 5:00 a.m. Which conclusion is most appropriate under sound change-management control?
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.

Question 3

Company X's change-management policy requires CAB approval for planned changes and prohibits developers from direct production access. Emergency hotfixes may be applied immediately to restore service but must be documented and presented to the CAB afterward. During Year 1, a production outage occurred; a developer with direct production credentials logged into production and applied a hotfix that restored service. The change was untested, operations was not notified, and no change request or CAB documentation was created. As the IT audit manager reviewing the incident, what is the best action to recommend to management?
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.

Question 4

A company uses an ERP application that supports financial reporting. For normal program changes, the process requires a documented ticket, manager approval, testing in a QA environment, and migration to production by a release administrator who does not have development access. For emergency changes, when a significant business disruption is occurring, the on-call senior developer may use a break-glass account to modify production directly. The developer must complete the ticket by the next business day, and the change advisory board reviews a weekly report of emergency changes. System logs identify when the break-glass account was used, but no one independently compares the code running in production to the version later checked into the source-code repository. Assume no other compensating controls. Which conclusion is best supported?
Hint

Focus less on whether emergency changes are allowed and more on what independent control evidence exists after the normal sequence is bypassed.

Question 5

A company normally requires testing and approval before any code is moved to production. On the morning of a payroll deadline, IT implements an emergency patch directly in production to correct a critical processing failure. Assume the patch could not reasonably wait for the normal change window. Under sound change management, when should formal approval, documentation, and review of this change occur?
Hint

Think about how emergency changes differ from normal changes: the timing of control activities may shift, but the control itself should still happen.

Question 6

A company normally requires all application changes to be tested, approved, and migrated to production by personnel independent of development. Assume the company has a documented emergency change process. Under which circumstance is it most acceptable for a developer to move a change directly into production?
Hint

Look for the situation where normal change controls may be bypassed only temporarily, and only with compensating controls still in place.

Question 7

A company's billing system has a defect that is preventing invoices from being generated on the last business day of Year 1. A developer has prepared a code fix and asks for it to be moved into production that afternoon. The company has a formal change management process that includes emergency changes. Which action is most consistent with effective change management?
Hint

Think about what should still happen even when a change is urgent enough to qualify as an emergency.

Question 8

A company's normal change-management process requires a documented change request, approval by the business owner, testing in a nonproduction environment, and migration to production by someone other than the developer. During Year 2 month-end close, an overnight interface failure stopped billing. To restore service quickly, the on-call developer used emergency access to edit a production script directly. Processing resumed before business opened. The next morning, management confirms the outage is over, but there was no preimplementation approval, no nonproduction test evidence, and no independent record of exactly what was changed in production. Assume service is currently stable and an immediate rollback is not required for legal or safety reasons. What is the best action?
Hint

Focus on what an emergency change may bypass temporarily versus what the organization still must do afterward to restore control.

Question 9

A company experienced a production outage in 20X6. To restore service quickly, a system administrator used emergency access to implement a code change directly in production before normal approval and testing steps were completed. The company's policy allows emergency changes if required follow-up controls are completed immediately afterward. Which action is the most appropriate required response?
Hint

Think about what should happen after an emergency change skips the normal pre-approval path.

Drill all 162 Change management questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Change management practice →

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.