Exam Professional Cloud DevOps Engineer topic 1 question 90 discussion

Answers A and B split traffic, but C has a gradual rollout which doesn't have instant rollback. D with the blue/green deployment has instant rollback with no impact to either users or developers. I believe the answer is D.

https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#deploy-with-tags A common use case for this feature is to use it for testing and vetting of a new service revision before it serves any traffic, in this typical sequence: 1Run integration tests on a container during development. 2Deploy the container to a Google Cloud project that you use only for staging, serving no traffic, and test against a tagged revision. 3Deploy it to production, without serving traffic, and test against a tagged revision in production. 4Migrate traffic to the tagged revision. The tag lets you directly test the new revision at a specific URL, without serving traffic.

D. No impact

A. Deploying the new version to the staging environment and allowing only 1% of traffic to the latest version minimizes user and developer impact, as the majority of traffic continues to be served by the current version. Testing the latest version in the staging environment ensures that any issues can be identified and addressed before rolling out the new version to production. not C cause: Deploying the new version with a new-release tag without serving traffic in the staging environment delays the testing process and does not provide an accurate representation of how the new version performs under real-world conditions with actual traffic.

https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#:~:text=A%20common%20use,the%20tagged%20revision.

Choose A. This approach allows for thorough testing while minimizing the risk of impacting users and developers. It provides a controlled rollout with the ability to monitor and react to any issues that may arise during the deployment process. Option A aligns with best practices for deploying and testing new versions in a microservices environment.

Choose A

This approach allows you to deploy and test the new version without impacting users, as no traffic is directed to the new version initially. After thorough testing in the staging environment, you can confidently roll out the new version to a small percentage of users in the production environment, gradually increasing it while monitoring performance and stability. This method offers a controlled and safe way to introduce changes.

I would go for D as it is the only one that will not impact users or devs

Deploy it without serving a traffic. this approach is the optimal since we need to test it intensively. this will avoid the negative impact

I think A. need a canary to reduce the sphere of influence.

D should be it

Rethinking answer is C for using release tag. "You are deploying a new release, and you need to test the new version extensively in the staging and production environments. You must minimize user and developer impact. "

I will go with C

A, B, and C involve splitting traffic, which may not provide the level of isolation required for extensive testing without impacting users and developers Correct Answer is D