ISC · Information Systems and Data Management · 162 practice questions
Change management: classify changes, keep control in emergencies, and enforce segregation of duties
Decide if it is an emergency, apply only the allowed shortcuts, then restore full control fast, and never let developers deploy their own code to production.
Mixed drill
Questions from every rule below, shuffled. You get the explanation after each one, and at the end, the rules to review.
The rules, one page each
- Emergency Change Criteria: When an Active Exploit Cannot WaitStep by step
Classify a change as an emergency when immediate implementation is necessary to address a critical production threat before the normal process can reasonably finish. Follow the policy's emergency authorization, documentation, and review requirements.
- Change Classification: Risk and Business ImpactWhat next?
Classify 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.
- Standard vs normal vs major: Does it fit the preapproved runbook?Sort it
A standard change is low risk, repeatable, and executed exactly as a preapproved runbook; any deviation, one‑time configuration, schema change, or higher‑impact logic change requires normal or major controls with testing and approvals.
- Normal Change Management: Testing, Approval, and MigrationTimeline
For nonemergency changes, document the request, complete and retain production-like testing, obtain formal release approval after reviewing results, and document a rollback plan. An authorized person independent of development must migrate the approved change to production.
- Emergency Change Controls Before Production DeploymentTimeline
Before 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.
- Emergency Change Post-Implementation Review and ApprovalTimeline
As 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.
- Auditor Conclusions on Change Management DeficienciesWhat next?
Bypassing required change procedures is an operating deficiency in change-management ITGCs. Reliance on affected automated controls is weakened from deployment until validation or other sufficient evidence supports their reliability.
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 change management. No account needed to start.
Open the free simulator →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.