PROFESSIONAL-CLOUD-DEVELOPER · Question #167
The new version of your containerized application has been tested and is ready to deploy to production on Google Kubernetes Engine. You were not able to fully load-test the new version in…
The correct answer is B. Deploy the application via a continuous delivery pipeline using canary deployments. Use Cloud. A canary deployment sends a small percentage of real production traffic to the new version while keeping the majority on the old version. This allows you to monitor actual performance metrics in production incrementally and roll back quickly if problems emerge - all without a…
Question
The new version of your containerized application has been tested and is ready to deploy to production on Google Kubernetes Engine. You were not able to fully load-test the new version in pre-production environments, and you need to make sure that it does not have performance problems once deployed. Your deployment must be automated. What should you do?
Options
- AUse Cloud Load Balancing to slowly ramp up traffic between versions. Use Cloud Monitoring to
- BDeploy the application via a continuous delivery pipeline using canary deployments. Use Cloud
- CDeploy the application via a continuous delivery pipeline using blue/green deployments. Use
- DDeploy the application using kubectl and set the spec.updateStrategv.type to RollingUpdate. Use
How the community answered
(36 responses)- A22% (8)
- B58% (21)
- C6% (2)
- D14% (5)
Explanation
A canary deployment sends a small percentage of real production traffic to the new version while keeping the majority on the old version. This allows you to monitor actual performance metrics in production incrementally and roll back quickly if problems emerge - all without a full cutover. Blue/green deployments (C) switch 100% of traffic at once, which does not allow gradual performance validation. A RollingUpdate (D) replaces pods incrementally but doesn't control traffic splitting for safe monitoring. Cloud Load Balancing alone (A) is not a deployment strategy for GKE. Canary is the correct strategy when load testing was incomplete and risk must be minimized.
Topics
Community Discussion
No community discussion yet for this question.