Explanation:
The correct answer is the canary deployment method because it allows for a partial rollout of the change to a select group of users, enabling performance evaluation against the baseline deployment with minimal user impact in case of failure. Other methods like Blue/Green or Red/Black involve switching all traffic to the new version at once, affecting all users if a failure occurs. Rolling updates gradually replace instances, increasing the number of affected users as the deployment progresses, making it less ideal for minimizing impact.
Ultimate access to all questions.
Imagine you're on an SRE team responsible for a frontend web service in production, which provides an HTTP-based API for data manipulation. A new version is ready for testing with live traffic, but there's a need to limit potential user impact in case of failure. Which deployment strategy best meets this requirement?
A
Implement a Rolling update deployment method for the new version in production.
B
Use a Blue/Green deployment method to introduce the new version in production.
C
Opt for a canary deployment method to roll out the new version in production.
D
Choose a Red/Black deployment method for deploying the new version in production.
No comments yet.