Why is performing a cutover during a maintenance window recommended during database migration?

• A. To allow unrestricted traffic during the transition.
• B. To minimize the impact on production services and provide a window for rollback if needed.
• C. To avoid any testing during migration.
• D. To increase downtime to ensure data consistency.

Answer: (B)

When you migrate a database, the cutover is the moment you switch from the old system to the new one. Performing that switch during a maintenance window keeps the change in a controlled, low-traffic period so you can validate data, monitor progress, and quickly rollback if something isn’t right. This minimizes impact to production services because users aren’t being affected by ongoing, unplanned changes, and it gives you a guaranteed window to verify correctness and perform any fixes before resuming normal operations. Unrestricted traffic during the switch would risk interruptions and data inconsistencies; skipping testing defeats verification; and deliberately extending downtime isn’t the goal—the aim is a brief, well-managed window that preserves continuity while ensuring a safe transition.