ISC · Information Systems and Data Management · 6 practice questions
Auditor Conclusions on Change Management Deficiencies
Bypassing change controls can weaken reliance on the automated control affected by the change. Below: judge the auditor’s response to an emergency change that bypassed testing and independent migration.
Try one first
Hint
Focus on how bypassed approvals and lack of testing/documentation affect the reliability of automated controls and how auditors respond when ITGCs are deficient, even if a specific error was corrected.
Answer B. Bypassing CAB authorization, skipping regression testing, and failing to document or plan rollbacks are deficiencies in change-management IT general controls that increase the risk of unauthorized or erroneous production changes. When ITGCs are ineffective, auditors typically cannot rely on automated application controls and respond by increasing substantive procedures and documenting a control deficiency. Correcting the specific error mitigates the immediate misstatement but does not eliminate the underlying control weakness.
Why not A: A restatement is required only when prior-period financial statements are materially misstated. The stem describes a corrected error but gives no basis to conclude the prior statements were materially misstated; correction alone does not automatically trigger a restatement.
Why not C: Although unauthorized changes can create security risks, the scenario explicitly states there is no evidence of external data exfiltration. The primary issue here is data integrity (incorrect balances), not a demonstrated confidentiality breach that would normally prompt regulatory penalties.
Why not D: Even if management detected and corrected the error, the underlying failures in change-management controls remain. Auditors still assess the control deficiency and typically increase substantive testing rather than leave planned procedures unchanged.
What should you do?
The situation
Cove requires approval, documented testing, and independent migration for code changes. After verbal approval from the AP manager, a developer directly deploys an emergency change to duplicate-invoice logic. The ticket is completed the next day, but no testing or independent review evidence exists. A daily report shows flagged duplicates, not missed duplicates. No separate validation occurs. Which auditor conclusion is best supported?
Reduce reliance on the duplicate-invoice control after deployment until the revised logic is validated.
Best The bypass creates an operating deficiency. Missed duplicates could continue passing without appearing on the report.
Keep reliance unchanged because verbal approval and the completed ticket establish adequate control.
Wrong Approval and later documentation do not replace testing evidence or independent migration.
Reduce reliance only on deployment day because the daily report monitors later processing.
Wrong The report cannot reveal missed duplicates, so the risk continues after deployment day.
Treat every accounts payable function as unreliable for the entire year.
Wrong The facts support reduced reliance on the changed duplicate-invoice control after deployment, not every function throughout the year.
Key points
- Remember: focus on the changed control after deployment, not the entire application for the entire year.
- A required control that was bypassed indicates an operating deficiency, not necessarily a design deficiency.
- A report of flagged duplicates cannot reveal duplicates the changed logic failed to flag.
How the exam traps you
- Treating verbal approval and a completed ticket as proof the change was controlled. Neither replaces testing evidence or independent migration.
- Limiting reduced reliance to deployment day because a daily exception report exists. The report cannot detect duplicates that the revised logic misses.
- Rejecting the entire application for the full year. Tie the conclusion to the affected control and the period after deployment.
Question 2
Hint
Focus on the main purpose of change management controls before thinking about speed or convenience.
Answer D. Change management exists to ensure changes are authorized, tested, documented, and migrated by appropriate personnel. Allowing developers to deploy changes without formal approval, testing, or independent migration removes those safeguards and increases the likelihood that faulty or unauthorized code will disrupt live processing and outputs. Thus the most direct consequence is a higher risk of processing errors in production.
Why not A: This confuses change management with backup and recovery. The ability to restore historical data depends on backups and rollback procedures; skipping formal change controls does not improve restoration assurance.
Why not B: This is tempting because fewer handoffs can seem faster, but efficiency does not substitute for control. Skipping approval, testing, and independent migration removes error-detection and authorization steps and therefore increases, not decreases, production risk.
Why not C: This distractor appeals to the idea of personal accountability, but segregation of duties requires separating development from deployment and approval functions. Letting developers push their own changes weakens segregation of duties and increases the risk of unauthorized or erroneous changes.
Question 3
Hint
Focus on what change management controls are supposed to prevent before a change reaches production.
Answer D. Change management requires that modifications be authorized, tested, approved, and documented before reaching production. Allowing developers to deploy urgent fixes without independent review or testing increases the likelihood that faulty or unauthorized code will be introduced, which can cause incorrect processing, outages, or other operational problems.
Why not A: While single-person ownership might feel accountable, proper accountability in change management comes from documented approvals, testing, and audit trails. Concentrating duties in one person increases the chance that errors or unauthorized changes go undetected.
Why not B: This is tempting because fewer handoffs can seem simpler, but skipping independent approval and testing typically increases risk. Independent review exists to catch mistakes and unauthorized changes before they affect production.
Why not C: This distractor plays on responsiveness, but segregation of duties is weakened when the same developer can both make and deploy changes without authorization. Direct response does not substitute for appropriate separation of responsibilities and controls.
Question 4
Hint
Focus on what the failed change-management steps mean for the specific logic that changed, and when that risk would begin and end.
Answer D. The primary risk is reduced reliability of the specific automated control affected by the unvalidated change. That risk begins once the altered logic is in production and continues until independent validation or other evidence substantiates the change. The daily exception report does not fully compensate because it cannot reveal duplicates that the changed logic fails to flag.
Why not A: This is tempting because candidates often overweight after-the-fact approval and ticket completion. However, verbal approval and later ticket closure do not substitute for evidence of testing, independent migration, or review. Without validation, the changed logic could still process transactions incorrectly.
Why not B: This attracts candidates who view the exception report as a sufficient compensating control. The risk is not confined to the migration date: if flawed logic remains in production, it can affect all subsequent transactions. Moreover, the report cannot show duplicates that the altered logic fails to detect.
Why not C: This overgeneralizes a specific change-management failure into a total loss of reliance. The facts point to a breakdown tied to a specific change in duplicate-invoice matching logic, not to every AP function for the entire year.
Question 5
Hint
Identify which change-management objective is still not satisfied after considering the compensating controls: traceability, recoverability, testing, or confirmation that the exact approved code is what reached production.
Answer A. The key remaining gap is change integrity: the process does not verify that the exact code moved to production matches the code described, reviewed, or retrospectively approved in the emergency ticket. That means a ticket, repository log, and after-the-fact review can all exist while unauthorized or different code still reaches production. Skipped testing is also a risk, but the missing reconciliation makes the authorization evidence itself less reliable.
Why not B: This is tempting because the stem explicitly says preimplementation testing may be skipped, which is a classic emergency-change weakness. But it is wrong because the controls described do not confirm that the deployed code matches the ticketed and later approved change, so the risk is not limited to merely authorized-but-untested fixes. Unauthorized or altered code can still be introduced under the cover of a valid emergency ticket.
Why not C: This distractor is attractive because retrospective approval often signals weak documentation. However, the stem states that source-code commits are logged in the repository and deployment logs are reviewed, so traceability exists. The bigger problem is not identifying that a change occurred, but verifying that the exact deployed change is the one management intended to authorize.
Why not D: This sounds plausible because emergency changes can create rollback problems in practice. But the question expressly says backup/recovery controls are otherwise effective, and repository logging also suggests version history exists. The more direct consequence from the facts given is weak assurance over the authorization and integrity of the deployed code, not inability to restore prior versions.
Question 6
Hint
Focus on the primary purpose of change management controls: what risk do approval, testing, and separate migration responsibilities reduce?
Answer B. Change management controls ensure changes are authorized, tested, and migrated by appropriate, independent personnel before reaching production. When a developer bypasses preimplementation approval and migrates code directly, the primary consequence is an increased likelihood that an unauthorized or erroneous change will enter the live environment. Post-deployment documentation does not remove the control failure that occurred at the time of deployment.
Why not A: Although an incorrect program change can later affect data quality, issues with incomplete or inaccurate source data are primarily caused by input and user-entry controls. The immediate and most direct risk from bypassing change controls is uncontrolled deployment of code, not user data-entry errors.
Why not C: Backup and recovery are separate IT general controls; nothing in the scenario indicates backups or recovery procedures were altered or weakened. The scenario describes a breakdown in change authorization and migration procedures, not in backup operations.
Why not D: Duplicate-detection and batch controls are application-level processing controls. While program changes could theoretically alter processing logic, the stem points to a failure of change-management discipline, the most direct consequence is unauthorized or erroneous code reaching production.
Common questions
Is bypassing a change-management policy a design or operating deficiency?
Cove required testing and independent migration, but personnel skipped those steps. That indicates an operating deficiency.
How long does an untested program change affect audit reliance?
Reliance on Cove’s duplicate-invoice control is weakened from deployment until validation or other sufficient evidence supports the revised logic’s reliability.
Can an exception report compensate for weak change controls?
Only if it addresses the relevant risk. Cove’s report shows flagged duplicates, so it cannot reveal duplicates that the changed logic fails to flag.
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.