PROFESSIONAL-CLOUD-DEVELOPER · Question #32
You have an application deployed in production. When a new version is deployed, you want to ensure that all production traffic is routed to the new version of your application. You also want to keep t
The correct answer is A. Blue/green deployment. Blue/green deployment uses two identical production environments: the 'blue' environment runs the current stable version, while the 'green' environment is provisioned with the new version. When the new version is ready, all production traffic is switched from blue to green at onc
Question
You have an application deployed in production. When a new version is deployed, you want to ensure that all production traffic is routed to the new version of your application. You also want to keep the previous version deployed so that you can revert to it if there is an issue with the new version. Which deployment strategy should you use?
Options
- ABlue/green deployment
- BCanary deployment
- CRolling deployment
- DRecreate deployment
How the community answered
(43 responses)- A77% (33)
- B5% (2)
- C5% (2)
- D14% (6)
Explanation
Blue/green deployment uses two identical production environments: the 'blue' environment runs the current stable version, while the 'green' environment is provisioned with the new version. When the new version is ready, all production traffic is switched from blue to green at once. The blue environment remains running and idle, enabling an instant rollback by redirecting traffic back if problems emerge. This exactly matches the requirements: all traffic moves to the new version immediately, and the old version is kept on standby. Option B (canary) splits traffic gradually between versions. Option C (rolling) replaces instances incrementally. Option D (recreate) shuts down the old version before starting the new one, eliminating the rollback safety net.
Topics
Community Discussion
No community discussion yet for this question.