Exam Professional Cloud DevOps Engineer topic 1 question 144 discussion

A&E seem correct for using live production traffic. The question states "You want to use live production traffic to test a new version of the application,"

B. Deploy a new Cloud Run revision with a tag and use the --no-traffic option. - This allows manual testing by the QA team without exposing the new version to production traffic. - Tagging the revision makes it easy to access the new version directly for testing purposes. - The --no-traffic flag ensures no production traffic is automatically routed to the new revision. E. Deploy the new application version, and split traffic to the new version. - Splitting traffic lets you test the new version with a controlled percentage of live production requests. - This method follows best practices for gradual rollouts, limiting the risk of major failures. - If issues arise, you can easily revert traffic back to the previous version.

I think this should be BE.. Because option D doesn’t provide a built-in mechanism for partial traffic splitting or rolling back easily. You’d end up routing all production traffic to the new revision’s URL without the safe test approach that traffic splitting offers. This increases the risk of disruptions if there are issues.

Definitely E for prod traffic. And B for developer only end.

B: https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#deploy-with-tags D: https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#console_1:~:text=In%20the%20form%3A-,Set%20it%20to%20the%20desired%20percentage%2C%20for%20example%2C%205.%20Note%20that%20the%20currently%20serving%20version%27s%20percentage%20is%20automatically%20reduced%20by%20that%20same%20amount.,-Click%20Save.

Looks like just only (option B) is the most reasonable. But after thinking harder on this question, maybe choosing (option B & D) its okey to involves 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.

Vote BD

I would go for BD Option E does not right as it talks about split the live traffic

I would go for BD

keyword: You want to use live production traffic

https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#tags B is correct which targets to utilise the cloud run tag feature without serving traffic first, the idea is once tested adequately, then migrate traffic to the tagged revision. But not sure what is another answer given it is multi-choice, none of them apart from B looks reasonable.

C should definitely be one of the options https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration