In change management, what is the purpose of a testing/rollback plan?

• A. To log the change in the asset registry.
• B. To implement the change quickly to minimize downtime.
• C. To verify the change works as intended and provide a rollback path if issues arise.
• D. To replace the existing system with a new one.

Answer: (C)

A testing/rollback plan is about verification and reversibility. It ensures you validate that the change behaves as intended in a controlled setting and that you have a clear, tested way to revert to the prior state if problems arise after deployment. This means laying out the tests you will run, the acceptance criteria the change must meet, and the exact rollback steps, including how to restore data and the conditions that trigger a rollback. By defining these elements, you protect service availability and data integrity because issues can be caught early and reversals can be performed quickly and safely. Logging the change in an asset registry helps with tracking, but it doesn’t provide the necessary verification and rollback capability. Rushing the change to minimize downtime bypasses essential checks, and replacing the entire system is a different kind of effort that goes beyond what a rollback plan is designed to cover.