You have an application that runs on Cloud Run. You want to use live production traffic to test a new version of the application, while you let the quality assurance team perform manual testing. You want to limit the potential impact of any issues while testing the new version, and you must be able to roll back to a previous version of the application if needed. How should you deploy the new version? (Choose two.)
A. Deploy the application as a new Cloud Run service.
B. Deploy a new Cloud Run revision with a tag and use the –no-traffic option.
C. Deploy a new Cloud Run revision without a tag and use the –no-traffic option.
D. Deploy the new application version and use the –no-traffic option. Route production traffic to the revision’s URL.
E. Deploy the new application version, and split traffic to the new version.
Disclaimer
This is a practice question. There is no guarantee of coming this question in the certification exam.
Answer
B, D
Explanation
Looks like just only (option B) is the most reasonable.
But after thinking harder on this question, maybe choosing (option B & D) it’s fine to involve deploying the new version of the application on Cloud Run by creating a new revision with a tag and using the –no-traffic option. This approach allows the isolation of the new revision from live production traffic initially.
Once the deployment is complete, extensive testing can be conducted without affecting users. Subsequently, when confident in the new version’s stability, production traffic can be gradually directed to it using the Cloud Run services update-traffic command.
This combination ensures a controlled and risk-mitigated approach to deploying and testing new versions, with the ability to roll back if any issues arise during the testing phase.
A. Deploy the application as a new Cloud Run service.
(It won’t give ability to test new version with live production traffic.)
B. Deploy a new Cloud Run revision with a tag and use the –no-traffic option.
(https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#deploy-with-tags)
C. Deploy a new Cloud Run revision without a tag and use the –no-traffic option.
(Deploying without a tag won’t be useful.)
D. Deploy the new application version and use the –no-traffic option. Route production traffic to the revision’s URL.
(https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#gradual)
E. Deploy the new application version, and split traffic to the new version.
(Not an option.)