PracticeISCFree practice exam

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.

The ruleBefore deployment, obtain designated emergency authorization, perform feasible testing, and prepare the required current backup and documented rollback plan. Use an independent deployer when possible, then complete the required post-implementation review.

Try one first

Your change management policy states: normal changes require CAB approval; emergency changes may be expedited but must be authorized in advance by the designated Emergency Change Authority (ECA), include a documented rollback plan and a current full backup, require notification of the business owner and security, and be subject to post-implementation CAB review. In production, a recently discovered bug is actively corrupting customer records. The DBA developed a patch that stops the corruption and tested it in staging, but staging does not fully mirror production (different data volume and a configuration difference). The last full production backup is 36 hours old and there is no documented rollback plan. The DBA asks to apply the patch immediately out-of-hours without ECA authorization because any delay will allow further corruption. As the change manager, what is the most appropriate immediate action?
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.

The timeline

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

  2. Before deployment: requestOpen the emergency change ticket.

    Record the corruption, business impact, proposed patch, and reason the change cannot wait.

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

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

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

  6. Before deployment: notificationNotify the business owner and security.

    Record the required notifications in the emergency ticket before releasing the patch.

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

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

7 more, each from a different angle

0 of 7 answered · 0 correct

Question 2

A company has a formal change management process for routine system changes. However, for emergency application fixes, the developer who writes the code may move it directly into production to restore service. The change ticket is completed afterward, and there is no required evidence of preimplementation testing or prompt independent review. What is the primary issue in this process?
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.

Question 3

A company requires production changes to have a documented request, evidence of testing, approval, and migration by someone other than the developer. During Year 1 month-end close, a developer identifies a bug that is causing incorrect sales tax calculations. The controller says the fix must be deployed that night to avoid misstated invoices. Which action is most consistent with sound change management?
Hint

Think about how a strong change management process handles urgent production fixes without abandoning core controls.

Question 4

A company discovers on the last day of Year 1 that a defect in its billing system is preventing customer invoices from being generated. Management decides the issue must be fixed before the overnight processing run. Assume the company has a documented emergency change process. Which response should the company require to maintain effective change management?
Hint

Focus on what changes in an emergency process and what controls still must remain in place.

Question 5

Year 1: DeltaTech has a formal change management process requiring documented change requests, risk assessment, testing, and CAB approval before deployment to production. An urgent security patch addressing an actively exploited vulnerability is released for the company's web application; deploying it will cause a brief planned outage. The CAB does not meet for three days, and the standard change process would take two days to complete. DeltaTech also maintains an emergency change procedure that permits immediate deployment for critical security fixes, provided the on-call change owner documents the change and notifies the CISO within 24 hours for retrospective CAB review. The on-call developer can deploy the patch immediately but has not yet prepared the documentation or notified the CISO. What is the most appropriate action under DeltaTech's change management process?
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.

Question 6

A company discovers at 8:00 p.m. that a production billing application is rejecting all customer payments. A developer has identified a code fix and wants to move it into production immediately. The company has a documented emergency change process that allows accelerated approval when service restoration is urgent. Which response is most appropriate?
Hint

Think about how a well-designed change management process handles urgent production fixes without abandoning control.

Question 7

A company discovers on the morning of payroll processing that a recent application update is causing some employee overtime hours to calculate incorrectly. The payroll manager says the issue must be fixed before payroll is run that afternoon. The developer who found the bug offers to make the correction directly in production to save time. Under a well-designed change management process, what is the best action?
Hint

Think about how good controls handle urgent situations without abandoning approval and documentation.

Question 8

A company's standard change process requires a documented ticket, evidence of testing, approval before implementation, and migration to production by personnel separate from development. Its emergency-change policy allows abbreviated preimplementation approval when a critical vulnerability is actively being exploited, but the policy still requires immediate logging of the change and an independent retrospective review on the next business day. During a real exploit, a senior systems engineer used a monitored break-glass account to implement a production configuration change after oral approval from the CISO. The change successfully stopped the exploit. However, the ticket was opened several hours later, testing evidence was attached after deployment, and no independent retrospective review occurred. Assume this was a valid emergency under policy. Which is the best action to strengthen change management without impairing emergency response?
Hint

Focus on which normal change controls can be abbreviated in a true emergency and which controls still must exist shortly afterward.

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

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

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.