Exam Professional Cloud Developer topic 1 question 141 discussion

Zero Downtime: Canary testing allows you to gradually roll out your new container to a small percentage of users while the rest continue using the previous version. This ensures zero downtime during the deployment process. Automated Testing: Spinnaker is a powerful CI/CD platform that can automate your canary testing process, including monitoring the new container's performance and health. Testing Before Rollout: Canary testing allows you to test the new container in a production environment with real users, but with limited impact. This helps identify any issues before a full rollout. Quick Rollback: If the canary test reveals problems, Spinnaker can quickly roll back to the previous version, minimizing disruption to users.

Spinnaker is a cloud native continuous delivery platform that can be used to deploy applications to a variety of cloud providers, including Google Kubernetes Engine (GKE). Spinnaker is a good choice for deploying applications to GKE because it provides a number of features that make it easy to deploy applications quickly and reliably, including: Canary deployments: Canary deployments allow you to deploy a new version of your application to a small subset of users before rolling it out to all users. This allows you to test the new version of your application and identify any problems before they impact all of your users. Rollback: Spinnaker can be used to quickly rollback to a previous version of your application if you encounter any problems with the new version.

Shadow testing is the right choice. Canary is not suitable here since the requirement is to test before rolling new version to users. Option A also comes very closer since it has A/B testing that is done only after releasing the newer version to users that is only small amount of traffic is diverted to dedicated users (testers) who gives faster feedback about newer product/service.

Option D, triggering another Cloud Build job that uses the Kubernetes CLI tools to deploy your new container to your GKE cluster, where you can perform a shadow test, could meet the requirements you specified. Shadow testing is a technique where you can test the new version of an application by mirroring user traffic to it, without impacting the user requests to the current version. This way, you can test the new version of your application in a real-world environment with real user traffic, which allows for testing before being rolled out to users and allows for a quick rollback if needed. And with the use of Kubernetes CLI tools you can automate this process, so the testing and deployment is fully automated.

D is the answer. https://cloud.google.com/architecture/implementing-deployment-and-testing-strategies-on-gke#perform_a_shadow_test With a shadow test, you test the new version of your application by mirroring user traffic from the current application version without impacting the user requests.

vote D

IMHO by eliminating B and C - uses canary which letting the users use the new version without testing A - canary is often a synonym of A/B testing