PracticeISCFree practice exam

ISC · Information Systems and Data Management · 6 practice questions

Change Classification: Risk and Business Impact

Change classification depends on potential business and control impact, not how small the edit looks or who requests it. Below, judge proposed responses to a small access change that could affect revenue reporting.

The ruleClassify a change and set testing and approval rigor using a documented assessment of business impact and risk to confidentiality, integrity, and availability, not requester seniority or implementation effort.

Try one first

A company has a formal change-management policy requiring testing and approvals before production changes. A vendor patch addresses a vulnerability that is publicly disclosed and actively exploited. Deploying the patch without testing risks about 30 minutes of downtime for a mission-critical application, while delaying deployment to complete testing leaves systems exposed. Network security recommends immediate deployment; operations insists on completing the full testing cycle; senior management urges immediate remediation to reassure customers. Which factor should govern the decision to treat this update as an emergency change and deploy immediately rather than follow the normal change workflow?
Hint

Focus on what objective criteria change-control policies use to declare an emergency, who is asking or what directly measures potential harm?

What should you do?

The situation

Harbor Co.'s controller requests a small update to user access logic in its revenue application before quarter-end. Coding takes under an hour and affects few users, but faulty access could expose customer data, permit unauthorized revenue-report changes, or disrupt processing. This is not an emergency. Policy requires classification before choosing testing and approval requirements. How should IT respond?

  1. Document access, reporting, and processing risks, then use that assessment to select the category and required controls.

    Best This bases classification and control rigor on potential harm rather than effort, requester status, or deadline pressure.

  2. Keep the update out of production while IT assesses its access and reporting risks.

    Acceptable This is a reasonable interim safeguard, but it does not yet determine the category or required controls.

  3. Classify it as minor because coding takes under an hour and few users are affected.

    Wrong Effort and user count do not measure the severity of unauthorized access or inaccurate reporting.

  4. Let the controller's approval replace the usual review because the controller owns the reporting deadline.

    Wrong Requester authority does not replace risk-based testing and approval requirements.

  5. Reduce testing to meet quarter-end, then assess the impact after deployment.

    Wrong Deadline pressure does not justify selecting controls before assessing this nonemergency change's risks.

Key points

  • Remember: A small edit can need strong controls when the consequences of failure are serious.
  • Assess downstream effects on revenue reports, not just the access setting being changed.
  • Choose the change category after assessing risk, then determine the required testing and approvals.

How the exam traps you

  • Treating a quick edit affecting few users as automatically minor. Assess what incorrect access could expose, alter, or disrupt.
  • Letting the controller's title determine the approval path. Apply the same risk-based classification regardless of who requests the change.
  • Using the quarter-end deadline to justify lighter controls. Consider timing in the assessment; deadline pressure does not establish low risk.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

On the last day of 20X5, Falcon Co. learns that a newly disclosed software vulnerability could allow unauthorized access to its customer database. A vendor patch is available immediately, but Falcon's normal change process would delay implementation for three days. Falcon's policy permits emergency changes when justified and requires a post-implementation review. Which factor should primarily govern whether Falcon routes this patch through the emergency change process?
Hint

Ask what emergency change procedures are designed to address: who requested the change, who supplied it, or the risk of waiting.

Question 3

Company Z is planning two changes for the next quarter. Change A is a company-wide cosmetic redesign of the employee self-service portal affecting ~85% of users; it does not change data processing logic, has a tested fallback, and poses little regulatory exposure. Change B is a small code update to payroll tax calculations that could cause incorrect tax filings and regulatory fines if implemented incorrectly; rollback for this change is technically difficult. Both changes have similar schedule pressure and resource allocation. When deciding the appropriate level of change-management governance (approval authority, testing rigor, rollback planning), which single factor should govern that decision?
Hint

Ask which change, if it failed, would cause the largest harm to the organization (operational loss, regulatory penalty, or financial restatement).

Question 4

An organization routes changes either to full Change Advisory Board (CAB) review or to an expedited process. IT receives a requested change that (1) is a small configuration tweak to the payment-processing module that will briefly take the module offline, (2) is flagged urgent to meet a regulatory reporting deadline, and (3) was requested by a vice president. The payment-processing module handles cardholder data (PCI) and customer PII. Which of the following should most govern whether this change requires full CAB review rather than expedited handling?
Hint

Which choice captures the likely operational, security, and regulatory consequences of the change rather than who asked for it, how fast it's needed, or how many lines are changed?

Question 5

A company uses formal change management for systems that support financial reporting. Two days before quarter-end, the controller asks IT to make a "small" change to the logic used in a revenue report. The developer argues the change should be moved quickly because it affects only one report and can be coded in less than an hour. Under sound change management, which factor should primarily govern whether the change requires formal testing, approval, and controlled migration?
Hint

Focus on what change management is designed to control: not convenience or authority, but risk to the production environment and reporting.

Question 6

An entity's change management policy permits an emergency change to bypass normal preimplementation user acceptance testing and the next scheduled change advisory board meeting only when waiting for the standard release cycle would expose the entity to a documented risk that meets predefined emergency criteria. A vendor issues a patch for the entity's internet-facing payroll application. The patch both remediates a newly disclosed privilege-escalation vulnerability and improves processing speed. Industry alerts report active exploitation in the wild, but the entity has not yet confirmed an internal compromise. Payroll must run tomorrow morning. The application is financially significant, and the only person available tonight to deploy the patch is the same developer who tested it; however, an independent infrastructure manager can review logs and the ticket the next morning. Assume the policy otherwise allows retrospective review for true emergencies. Which factor should govern whether management classifies this as an emergency change rather than waiting for the normal release cycle?
Hint

Separate the question of whether the emergency path is allowed from the question of what controls must surround the change once that path is used.

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

What should govern change classification?

A documented assessment of potential business and control impact should govern classification. Here, access to customer data and revenue reports matters more than coding time.

Can a small code change require formal testing and approval?

Yes. A small access-logic edit can expose data, permit unauthorized report changes, or disrupt processing, so its potential consequences determine the required rigor.

Does a controller's urgent request justify lighter change controls?

No. The controller's title and quarter-end deadline do not replace the risk assessment that determines testing and approval requirements.

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.