PROFESSIONAL-CLOUD-DEVELOPER · Question #45
You have an application deployed in production. When a new version is deployed, some issues don't arise until the application receives traffic from users in production. You want to reduce both the imp
The correct answer is B. Canary deployment. A canary deployment routes only a small percentage of production traffic to the new version while the majority of users continue using the stable version. If issues appear, only the small canary population is affected, and the rollout can be halted before broader exposure - direc
Question
You have an application deployed in production. When a new version is deployed, some issues don't arise until the application receives traffic from users in production. You want to reduce both the impact and the number of users affected. Which deployment strategy should you use?
Options
- ABlue/green deployment
- BCanary deployment
- CRolling deployment
- DRecreate deployment
How the community answered
(31 responses)- A6% (2)
- B81% (25)
- C10% (3)
- D3% (1)
Explanation
A canary deployment routes only a small percentage of production traffic to the new version while the majority of users continue using the stable version. If issues appear, only the small canary population is affected, and the rollout can be halted before broader exposure - directly minimizing both the impact and the number of affected users. Option A, Blue/Green deployment, shifts 100% of traffic to the new version at cutover, so all users are impacted if a problem occurs. Option C, Rolling deployment, gradually replaces old instances with new ones, but all instances eventually serve the new version without an easy staged percentage rollout. Option D, Recreate deployment, takes down all existing instances before launching new ones, causing downtime and affecting all users at once.
Topics
Community Discussion
No community discussion yet for this question.