Which criteria typically trigger a deployment rollback decision?

Which criteria typically trigger a deployment rollback decision?

• A. Critical failures, unacceptable error rates, or failed compliance checks.
• B. New feature flag toggles.
• C. Calendar date.
• D. Completion of deployment window.

Answer: (A)

When deciding to rollback a deployment, you rely on health and compliance signals from the new release. The trigger is when post-deploy indicators show problems: critical failures, unacceptable error rates, or failed compliance checks. These signals mean the new version isn’t meeting reliability, performance, or policy requirements, so reverting to the previous stable version minimizes impact. New feature flag toggles are a deployment-control mechanism to gradually expose changes, not a direct health signal that automatically causes a rollback. Scheduling factors like a calendar date or completion of a deployment window don’t reflect the actual state of the release, so they aren’t the reasons to rollback.

When deciding to rollback a deployment, you rely on health and compliance signals from the new release. The trigger is when post-deploy indicators show problems: critical failures, unacceptable error rates, or failed compliance checks. These signals mean the new version isn’t meeting reliability, performance, or policy requirements, so reverting to the previous stable version minimizes impact.

New feature flag toggles are a deployment-control mechanism to gradually expose changes, not a direct health signal that automatically causes a rollback. Scheduling factors like a calendar date or completion of a deployment window don’t reflect the actual state of the release, so they aren’t the reasons to rollback.