Which statement best describes the components of a robust rollback plan?

Which statement best describes the components of a robust rollback plan?

• A. Artifact versions should be changed frequently to prevent caching.
• B. Rollback plans should only rely on hotfix patches.
• C. Rollback plans should specify exact artifact versions, preconditions, revert steps, data migration considerations, and verification checks.
• D. Rollback plans are optional if canary analysis is used.

Answer: (C)

A robust rollback plan is actionable and comprehensive, detailing exactly what to revert and how to do it safely. The best statement captures all the essential components: it specifies the exact artifact versions to return to, the preconditions that must be met before rollback, the precise revert steps to execute, how to handle any data migrations or schema changes during the reversal, and the verification checks to confirm the system is healthy after rollback. This combination ensures the rollback is repeatable, auditable, and minimizes the chance of leaving the system in an inconsistent state. Why this approach fits best: knowing the exact artifact version to roll back to removes ambiguity about what state the system should return to. Preconditions prevent rolling back at a time that could cause data loss or user impact. Clear revert steps provide a deterministic sequence of actions rather than ad-hoc fixes. Data migration considerations acknowledge that databases often evolve with deployments, so you need a plan for undoing or safely compensating those changes. Verification checks give concrete evidence that the rollback succeeded and functionality is restored. Why the other options don’t fit as well: changing artifact versions frequently to prevent caching addresses deployment hygiene, not the rollback act itself and lacks the structured steps and validation required to revert safely. Relying only on hotfix patches omits the broader rollback needs, such as exact state, data handling, and post-rollback validation. Treating rollback plans as optional if canary analysis is used ignores the possibility that canaries can miss issues or still require a formal, tested rollback path to guarantee a clean recovery.

A robust rollback plan is actionable and comprehensive, detailing exactly what to revert and how to do it safely. The best statement captures all the essential components: it specifies the exact artifact versions to return to, the preconditions that must be met before rollback, the precise revert steps to execute, how to handle any data migrations or schema changes during the reversal, and the verification checks to confirm the system is healthy after rollback. This combination ensures the rollback is repeatable, auditable, and minimizes the chance of leaving the system in an inconsistent state.

Why this approach fits best: knowing the exact artifact version to roll back to removes ambiguity about what state the system should return to. Preconditions prevent rolling back at a time that could cause data loss or user impact. Clear revert steps provide a deterministic sequence of actions rather than ad-hoc fixes. Data migration considerations acknowledge that databases often evolve with deployments, so you need a plan for undoing or safely compensating those changes. Verification checks give concrete evidence that the rollback succeeded and functionality is restored.

Why the other options don’t fit as well: changing artifact versions frequently to prevent caching addresses deployment hygiene, not the rollback act itself and lacks the structured steps and validation required to revert safely. Relying only on hotfix patches omits the broader rollback needs, such as exact state, data handling, and post-rollback validation. Treating rollback plans as optional if canary analysis is used ignores the possibility that canaries can miss issues or still require a formal, tested rollback path to guarantee a clean recovery.