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.
Try one first
Hint
Focus on what objective criteria change-control policies use to declare an emergency, who is asking or what directly measures potential harm?
Answer D. Whether to declare a change an emergency should be driven by a documented risk assessment that evaluates severity and likelihood of harm to confidentiality, integrity, availability, business continuity, and regulatory obligations. A vulnerability that is publicly disclosed and actively exploited increases likelihood and potential impact and therefore can justify invoking emergency procedures and deploying a patch immediately despite normal testing. Stakeholder pressure, compliance timelines, cost, and scheduling inform planning and execution but are subordinate to the objective risk-based classification.
Why not A: Operational and scheduling concerns are tempting because organizations routinely prioritize changes around windows and resource constraints. They are incorrect as the governing factor here because, when likelihood and impact of a vulnerability are high, risk-based prioritization typically outweighs scheduling convenience.
Why not B: This distractor tempts because executives and customers often demand rapid action and those voices drive urgency in practice. It is wrong because stakeholder pressure is an input to response planning, not the objective criterion for classifying a change as an emergency; relying solely on directives risks inconsistent or unsafe decisions.
Why not C: Compliance obligations can make remediation urgent and therefore appear to mandate immediate action. However, they should be considered within the risk assessment (how likely and how severe the harm and regulatory impact would be); compliance alone does not automatically determine emergency classification without assessing actual risk.
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?
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.
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.
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.
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.
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.
Question 2
Hint
Ask what emergency change procedures are designed to address: who requested the change, who supplied it, or the risk of waiting.
Answer A. Emergency change procedures are intended for situations where waiting for the normal change process would expose the organization to significant operational or security harm. The primary decision here is whether delaying the patch increases the risk of unauthorized access or other unacceptable business impact. Other factors (vendor source, breadth of use, staff availability) inform implementation planning but do not by themselves justify emergency routing.
Why not B: This is tempting because vendor patches may appear standardized or more trustworthy, but the source of the patch does not determine urgency. Emergency treatment is based on the risk of waiting, regardless of who supplied the fix.
Why not C: Broader departmental use can increase the potential impact of a failure, making the change more important, but it is contextual. The key question is whether delaying implementation creates unacceptable operational or security exposure.
Why not D: Staff availability and segregation-of-duties considerations affect how the change is carried out and reviewed, but they do not primarily determine whether emergency classification is warranted. Emergency status should be driven by urgency and risk, not staffing convenience.
Question 3
Hint
Ask which change, if it failed, would cause the largest harm to the organization (operational loss, regulatory penalty, or financial restatement).
Answer D. Change-management governance should be driven primarily by expected business impact and associated risk (operational disruption, financial loss, regulatory exposure). Those consequences determine how much approval oversight, testing rigor, and rollback planning are warranted. Other factors, user scope, technical complexity, and schedule, are relevant inputs but are subordinate to the potential severity of harm if the change fails.
Why not A: Wide user impact matters for communication and rollout planning, but scope measures how many are affected rather than how severe the consequences would be. A large, low-risk cosmetic change typically needs lighter governance than a narrow change that could trigger regulatory fines or major financial harm.
Why not B: Technical complexity increases implementation risk and may require more testing, but complexity is a contributor to overall risk rather than the primary governance driver. Governance should be scaled to the likely business and compliance impact that results from implementation failure.
Why not C: Schedule and urgency affect prioritization, but time pressure should not override controls for high-impact changes. High-risk changes require robust governance even under tight timelines to protect the organization from severe operational or regulatory harm.
Question 4
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?
Answer A. Change routing should be risk-based: the primary determinant is the change's potential impact on confidentiality, integrity, availability, business operations, and regulatory compliance. Because the payment-processing module handles PCI and PII, even a small, urgent tweak may pose significant security, operational, and compliance risk and therefore justifies full CAB review. Neither requester seniority, stated urgency, nor small technical size alone override a formal impact-based assessment.
Why not B: Tempting because urgency often prompts expedited handling, but urgency alone doesn't eliminate high-impact concerns; urgent changes affecting sensitive systems (PCI/PII) may still require full CAB or an emergency CAB assessment with compensating controls.
Why not C: Tempting because size is an easy proxy for complexity, but small configuration tweaks can have outsized effects on critical or sensitive systems; size alone is an unreliable indicator of overall risk.
Why not D: Tempting because executives can create pressure to fast-track changes, but requester identity does not measure technical, security, or compliance risk; letting seniority dictate routing undermines controls and increases the chance of unsafe or noncompliant changes.
Question 5
Hint
Focus on what change management is designed to control: not convenience or authority, but risk to the production environment and reporting.
Answer C. Change-management rigor should be driven by risk and potential impact. Even a quick or localized code change can materially affect report accuracy, processing, or internal controls. Therefore decisions about testing, approvals, and controlled migration should be based on the change's potential impact on production processing and financial reporting, not on convenience or requester status.
Why not A: Quick coding time does not ensure low risk. Small code edits can have wide-reaching effects on logic or data, so coding effort alone is not the primary determinant of required controls.
Why not B: This is tempting because senior stakeholders may pressure IT, but approval requirements should be applied consistently based on risk, not on who requested the change.
Why not D: Timing near quarter-end can affect scheduling and justify extra caution, but it is not the primary governing factor; the key question remains the change's potential impact on reporting and production reliability.
Question 6
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.
Answer B. The core determination is whether waiting would create a time-sensitive risk that meets the organization's established emergency criteria. Emergency classification is about eligibility to use the expedited path, not about system importance alone or about what controls can be applied later. If the delay meets the emergency threshold, management then applies compensating controls (retrospective approval, log review, segregation checks) appropriate to the situation.
Why not A: This is tempting because business criticality and deadlines increase pressure to act, but those factors alone do not justify bypassing change controls. The policy requires a documented risk that would be unacceptable if the change were delayed, not just importance or urgency by themselves.
Why not C: Candidates may view availability of a retrospective reviewer as sufficient, but retrospective review is a compensating control after a change is classified as an emergency. The ability to review later does not determine whether the change meets the emergency criteria.
Why not D: Vendor origin or mixed-purpose content can be relevant context, but they do not by themselves make a change an emergency. The decisive factor is the consequence of delaying the update against the policy's emergency thresholds.
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
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.