Which rollback strategy switches traffic back to the previously stable environment?

Which rollback strategy switches traffic back to the previously stable environment?

• A. In-place rollback
• B. Rolling back by patch
• C. Canaries rollback
• D. Blue-green rollback

Answer: (D)

Blue-green rollback works by maintaining two production environments that are identical, with one currently serving live traffic and the other held as the known-good version. When a new release has issues, you switch the router or load balancer to send all traffic back to the previously stable environment. This swap effectively rolls back the deployment without changing the code in the currently running environment, providing an immediate and low-risk recovery. It also minimizes downtime and preserves the user experience while you address the problem in the new release. The other options describe reverting changes within the same environment, applying patches, or withdrawing traffic from a small subset, none of which describe the practice of redirecting all traffic back to the stable environment like blue-green rollback does.

Blue-green rollback works by maintaining two production environments that are identical, with one currently serving live traffic and the other held as the known-good version. When a new release has issues, you switch the router or load balancer to send all traffic back to the previously stable environment. This swap effectively rolls back the deployment without changing the code in the currently running environment, providing an immediate and low-risk recovery. It also minimizes downtime and preserves the user experience while you address the problem in the new release. The other options describe reverting changes within the same environment, applying patches, or withdrawing traffic from a small subset, none of which describe the practice of redirecting all traffic back to the stable environment like blue-green rollback does.