CompTIA Cloud+ (CV0-004)OperationsHard
A development team frequently deploys new versions of a web application to a cloud environment. After some deployments, users report intermittent errors and slow response times. The team wants to implement a strategy that allows them to quickly revert to a previous, stable version of the application if a new deployment introduces issues, minimizing downtime and impact. Which deployment strategy best supports this requirement?
- ABlue/Green deployment
- BIn-place deployment
- CCanary deployment
- DRolling update
Show answer & explanationAnswer & explanation
Correct answer: A. Blue/Green deployment
Blue/Green deployment involves running two identical production environments ('Blue' for the current version, 'Green' for the new version). Traffic is switched from Blue to Green. If issues arise, traffic can be instantly reverted back to the stable Blue environment, providing the fastest rollback and minimal downtime.
Why the other options are wrong
- B. In-place deployment updates the existing application, making quick rollback difficult and potentially causing downtime during updates.
- C. Canary deployment routes a small percentage of traffic to the new version for testing, but a full rollback for a complete failed deployment isn't as instantaneous as Blue/Green.
- D. Rolling updates gradually replace instances, but rollback can be slower and more complex if issues are found late in the process.
Blue/Green Deployment
A deployment strategy that runs two identical production environments (Blue and Green) and switches live traffic between them.
- Provides zero-downtime deployments.
- Enables instant rollback to the previous stable version.
- Requires double the infrastructure resources during deployment.
Memory trick: Blue/Green: Like 'Traffic Lights', switch instantly.