CompTIA Cloud+ (CV0-004)OperationsMedium
A development team is frequently deploying new features to a critical production environment. To minimize risk and ensure continuous availability during deployments, they want to test new versions with a small subset of real user traffic before rolling out to everyone. Which deployment strategy should be recommended?
- AIn-place upgrade.
- BCanary deployment.
- CBlue/Green deployment.
- DRolling update.
Show answer & explanationAnswer & explanation
Correct answer: B. Canary deployment.
Canary deployment allows a new version of an application (the 'canary') to be rolled out to a small percentage of users first. This enables the development team to monitor its performance and stability with real traffic before deciding to fully roll out or roll back, minimizing risk and ensuring continuous availability.
Why the other options are wrong
- A. In-place upgrades directly update the existing instances, which carries the highest risk of downtime or issues if the new version is faulty.
- C. Blue/Green deployment involves two identical environments, switching all traffic at once, which doesn't allow for gradual testing with a subset of users.
- D. Rolling updates gradually replace instances of the old version with the new, but typically without explicit traffic segmentation for a 'canary' test group.
Canary Deployment
A deployment strategy that releases a new version of an application to a small subset of users (the 'canary') to test its performance in a production environment before a full rollout.
- Reduces risk by limiting exposure to new code.
- Allows for real-world performance monitoring.
- Enables easy rollback if issues are detected.
Memory trick: Canary sings first: test small, then go big.