Google Cloud Professional Cloud DevOps Engineer — Question 112

The new version of your containerized application has been tested and is ready to be deployed to production on Google Kubernetes Engine (GKE). You could not fully load-test the new version in your pre-production environment, and you need to ensure that the application does not have performance problems after deployment. Your deployment must be automated. What should you do?

Answer options

• A. Deploy the application through a continuous delivery pipeline by using canary deployments. Use Cloud Monitoring to look for performance issues, and ramp up traffic as supported by the metrics.
• B. Deploy the application through a continuous delivery pipeline by using blue/green deployments. Migrate traffic to the new version of the application and use Cloud Monitoring to look for performance issues.
• C. Deploy the application by using kubectl and use Config Connector to slowly ramp up traffic between versions. Use Cloud Monitoring to look for performance issues.
• D. Deploy the application by using kubectl and set the spec.updateStrategy.type field to RollingUpdate. Use Cloud Monitoring to look for performance issues, and run the kubectl rollback command if there are any issues.

Correct answer: A

Explanation

Answer A is correct because canary deployments allow for gradual traffic allocation to the new version, enabling monitoring for performance issues before full rollout. Options B and C, while valid deployment strategies, do not offer the same level of controlled traffic management as canary deployments. Option D focuses on rolling updates but lacks the proactive monitoring and gradual traffic ramp-up that canary deployments provide.