PracticeISCFree practice exam

ISC · Information Systems and Data Management · 9 practice questions

Normal Change Management: Testing, Approval, and Migration

For a normal change, complete testing, obtain formal release approval, and document a rollback plan before independent production migration. Below: a billing calculation fix moves from the initial request to a controlled production release.

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

Try one first

An entity plans to correct a calculation error in its billing application. The developer who wrote the fix also has production access. Assume this is a normal change, not an approved emergency change. Under a sound change-management process, which response is required before the fix is moved to production?
Hint

Focus on the core preventive controls in normal IT change management, especially approval, testing, and who should move code into production.

The timeline

  1. Day 0Document and obtain initial approval of the billing calculation change request.

    Identify the requested correction and its business impact. Initial approval authorizes development, not production release. This is a normal change, with no emergency exception.

  2. DevelopmentThe developer codes the billing fix and performs unit testing.

    Successful unit tests do not make the fix ready for production. Required QA and user acceptance testing remain.

  3. TestingQA and billing users test the fix in a separate, production-like environment.

    Document and retain results showing that the correction works and does not disrupt existing billing calculations.

  4. Before release approvalDocument the rollback plan for the billing fix.

    Specify how to back out the change if implementation fails. A backup alone does not replace a documented rollback plan.

  5. Release approvalThe business owner or required change authority reviews test results and impact, then formally approves release.

    Release approval follows completed testing. The initial approval to develop the fix does not satisfy this requirement.

  6. Before production migrationConfirm the release controls are complete and an independent operations person is assigned.

    Postpone deployment if required testing, formal release approval, the rollback plan, or independent migration is missing.

  7. Production releaseAuthorized operations personnel migrate the approved billing fix, not the developer.

    Restrict production deployment rights to authorized personnel independent of development, and retain the migration record.

Key points

  • Remember: Approval to start development is not approval to release; release approval follows documented testing.
  • Developer unit tests do not replace the required QA and user acceptance testing.
  • If testing, release approval, rollback planning, or independent migration is missing, postpone deployment.

How the exam traps you

  • Treating successful developer unit tests as sufficient for production release. Complete the required testing in a separate, production-like environment and retain the results.
  • Approving production release when coding ends, before testing results are available. Obtain formal release approval after testing results and business impact have been reviewed.
  • Letting the developer deploy because testing and business approval are complete. Use authorized personnel independent of development to migrate the approved change.

8 more, each from a different angle

0 of 8 answered · 0 correct

Question 2

LuminCo must update its ERP payroll calculation for new tax-withholding rules that take effect in 10 days. Current practice: developers have direct write access to production and often deploy their own changes; the QA/test environment is not synchronized with production and cannot fully replicate payroll data or configurations; formal CAB approvals, pre-deployment acceptance testing, and rollback procedures are not consistently used. Which of the following is the correct approach LuminCo should adopt to align with appropriate change-management controls for this payroll update?
Hint

Think preventive, pre-deployment controls (formal approvals, production-like testing, segregation of duties, rollback planning) rather than detective measures or relaxed emergency authorizations.

Question 3

A company requires program changes to be approved, tested in a nonproduction environment, and migrated to production by operations personnel. During a review, the CPA finds that change requests are documented and testing evidence is retained, but developers still have the ability to move their own code into production without independent migration approval. Assume no emergency-change exception applies. Which conclusion is best supported?
Hint

Focus on which control prevents a developer from both creating and deploying a change without independent oversight.

Question 4

A company discovers on the morning of payroll processing that a payroll tax-rate table in its ERP system is outdated. The controller asks IT to update the production environment immediately so payroll can run on time. Under a sound change management process, which factor should primarily govern whether the update is moved to production?
Hint

Focus on what makes a production change acceptable under control standards, even when the business says the change is urgent.

Question 5

A company plans to deploy a nonemergency update to its billing system before month-end. The developer has completed coding and unit testing, but user acceptance testing has not been performed, the change request has not received formal approval, and no back-out plan has been documented. Management wants to move the change into production tonight to avoid delay. Assuming no emergency exception applies, what is the best action?
Hint

Focus on which change management steps are expected before a routine change reaches production, not on management's deadline pressure.

Question 6

Novus Corp uses a centralized revenue application. Late on a Saturday, a lead developer discovered a code bug that caused monthly revenue to be overstated and directly applied a code correction in production at 11:40 p.m. Novus's change management policy permits emergency changes to be authorized by the IT operations manager and later reviewed by the change advisory board (CAB), but requires that emergency changes be implemented by the operations team through the automated deployment pipeline; developers are not permitted to edit production code directly. In this case the IT operations manager gave verbal emergency authorization that evening, but the developer bypassed the deployment pipeline and made the production edit herself. The change was logged after the fact, a rollback plan was documented the next business day, and a formal change request and post-implementation review were created on Monday. Which of the following is the best-supported conclusion about Novus's change management controls?
Hint

Identify which control was explicitly bypassed during implementation (who performed the deployment and how that maps to segregation of duties and deployment controls).

Question 7

A company updates its inventory application regularly. Currently, the same developer who writes a program change also moves that change into production after receiving an email from the IT manager. User acceptance testing is informal, and there is no documented approval before implementation. Assume no emergency change exception applies. Which action is the best way to strengthen change management over program changes?
Hint

Focus on the key objectives of change management: authorization, testing, documentation, and separation between development and production.

Question 8

Arbor Co. uses formal change tickets for normal application changes. Developers code and unit test in a test environment. Business users approve the completed change, and an operations administrator who is not a developer moves approved code into production. However, each developer also retains direct update access to production programs for urgent fixes, and no independent review is performed over any direct production changes. Which conclusion is best?
Hint

Focus on who can bypass the normal change process and whether any compensating independent control catches that risk.

Question 9

A CPA is evaluating a company's application change management controls for reliance. For normal changes, each ticket requires documented user-requester approval, developer peer review, successful testing in a separate QA environment, and business-owner approval before release. Emergency changes may be moved to production before business-owner approval, but they must be documented and reviewed the next business day. The company uses a deployment tool to move approved code into production, but all developers and the IT operations lead use the same shared administrator credential in that tool. The tool records that the shared account performed the deployment, but it does not identify which individual initiated it. Assume all other stated controls operate as described. Which conclusion is best supported?
Hint

Focus on which fact most directly affects control over migration into production, not just whether every step is ideal.

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

When should a normal change receive formal approval for production?

After testing results are documented and reviewed, but before production migration. Initial request approval authorizes development, not production release.

Are developer unit tests enough before deploying a normal change?

No. For this billing fix, complete QA and user acceptance testing in a separate, production-like environment and retain evidence before release approval.

Can a normal change be deployed without a rollback plan?

No. Document how to back out the billing fix before release. Postpone deployment if the rollback plan or another required release control is incomplete.

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.