You are building a CI/CD pipeline that consists of a version control system, Cloud Build, and Container Registry. Each time a new tag is pushed to the repository, a Cloud Build job is triggered, which runs unit tests on the new code builds a new Docker container image, and pushes it into Container Registry. The last step of your pipeline should deploy the new container to your production Google Kubernetes Engine (GKE) cluster. You need to select a tool and deployment strategy that meets the following requirements: • Zero downtime is incurred • Testing is fully automated • Allows for testing before being rolled out to users • Can quickly rollback if needed What should you do?
- ATrigger a Spinnaker pipeline configured as an A/B test of your new code and, if it is successful, deploy the container to production.
- BTrigger a Spinnaker pipeline configured as a canary test of your new code and, if it is successful, deploy the container to production.
- CTrigger another Cloud Build job that uses the Kubernetes CLI tools to deploy your new container to your GKE cluster, where you can perform a canary test.
- DTrigger 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. (correct answer)
Reveal answer & explanationHide answer
The correct answer is D. Option D: Trigger 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.
Explanation
Google Kubernetes Engine runs managed Kubernetes for containerized, portable workloads. Cloud Build runs managed CI pipelines to build, test, and package code.
