What is a common rollback trigger example?

What is a common rollback trigger example?

• A. They are identical processes with different names.
• B. Continuous delivery ensures code is ready for release with manual approval; continuous deployment automatically deploys every change to production after passing tests.
• C. Continuous delivery means automatic deployment to production; continuous deployment requires manual approvals.
• D. Continuous delivery delays all releases until the end of quarter.

Answer: (B)

A rollback trigger is a condition that causes a release to be reverted to a previous, stable version to restore reliability. In deployment practice, continuous deployment automatically pushes every change that passes tests into production. Because changes land in production rapidly, having rollback mechanisms ready is a standard safeguard: if something goes wrong after deployment, you trigger a rollback to restore the prior working state. This scenario—automatic production deployment with the need to revert faulty changes quickly—is a common and practical example of a rollback trigger. The other options describe how deployment workflows are gated or described, rather than illustrating how a rollback would be initiated.

A rollback trigger is a condition that causes a release to be reverted to a previous, stable version to restore reliability. In deployment practice, continuous deployment automatically pushes every change that passes tests into production. Because changes land in production rapidly, having rollback mechanisms ready is a standard safeguard: if something goes wrong after deployment, you trigger a rollback to restore the prior working state. This scenario—automatic production deployment with the need to revert faulty changes quickly—is a common and practical example of a rollback trigger. The other options describe how deployment workflows are gated or described, rather than illustrating how a rollback would be initiated.