Google Exam Professional Cloud DevOps Engineer Topic 5 Question 72 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam

Question #: 72
Topic #: 5

[All Professional Cloud DevOps Engineer Questions]

You are building and deploying a microservice on Cloud Run for your organization Your service is used by many applications internally 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. What should you do?

ADeploy the new version of the service to the staging environment Split the traffic, and allow 1 % of traffic through to the latest version Test the latest version If the test passes gradually roll out the latest version to the staging and production environments

BDeploy the new version of the service to the staging environment Split the traffic, and allow 50% of traffic through to the latest version Test the latest version If the test passes, send all traffic to the latest version Repeat for the production environment

CDeploy the new version of the service to the staging environment with a new-release tag without serving traffic Test the new-release version If the test passes; gradually roll out this tagged version Repeat for the production environment

DDeploy a new environment with the green tag to use as the staging environment Deploy the new version of the service to the green environment and test the new version If the tests pass, send all traffic to the green environment and delete the existing staging environment Repeat for the production environment

Show Suggested Answer

Suggested Answer: B, D

by Paola at Jul 08, 2024, 11:33 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Kenneth

1 months ago

Option A is the way to go. It's like a choose-your-own-adventure book, but with code! 1% traffic? More like 1% chance of it all going wrong.

upvoted 0 times

Eric

3 days ago

That way we can catch any issues early on before rolling out to all users.

upvoted 0 times

...

Tyra

9 days ago

Agreed, we can gradually increase the traffic to minimize impact.

upvoted 0 times

...

Doug

13 days ago

Option A sounds like a good plan. Let's start with 1% traffic.

upvoted 0 times

...

Walker

2 months ago

Creating a separate green environment for staging is an elegant solution, but it might be overkill for this scenario. The cost and complexity could outweigh the benefits.

upvoted 0 times

Hollis

19 days ago

It's a good way to minimize impact on users and developers while ensuring the new version works as expected.

upvoted 0 times

...

Sabina

24 days ago

That way, you can monitor the performance and stability of the new release before fully deploying it.

upvoted 0 times

...

Reuben

25 days ago

You could use traffic splitting to gradually shift traffic to the new version in production.

upvoted 0 times

...

Dwight

2 months ago

The new-release tag approach looks interesting. Testing the new version without serving traffic is a smart way to ensure stability before rolling it out.

upvoted 0 times

Florinda

2 days ago

It's important to prioritize stability and minimize disruptions during deployment

upvoted 0 times

...

Tanja

4 days ago

Minimize user and developer impact by thoroughly testing in staging and production environments

upvoted 0 times

...

Tyisha

24 days ago

This will help ensure stability before rolling out the new release

upvoted 0 times

...

Stephaine

1 months ago

Use the new-release tag approach to test the new version without serving traffic

upvoted 0 times

...

Ryan

2 months ago

Splitting the traffic 50/50 in the staging environment is a bit risky. I'd prefer a smaller percentage to start with and gradually increase it if the test passes.

upvoted 0 times

...

Audra

2 months ago

That's a good point, Shizue. But I still think minimizing impact is crucial, so I prefer option A.

upvoted 0 times

...

Troy

2 months ago

Deploying the new version to the staging environment and gradually rolling it out while monitoring the traffic seems like a sensible approach. Minimizing user and developer impact is the key here.

upvoted 0 times

Jose

1 months ago

B) Absolutely, gradual rollout helps catch any issues early on without affecting all users at once.

upvoted 0 times

...

Bonita

1 months ago

A) Yes, it's important to ensure the new version works as expected before rolling it out to all users.

upvoted 0 times

...

Louis

2 months ago

B) Deploy the new version of the service to the staging environment Split the traffic, and allow 50% of traffic through to the latest version Test the latest version If the test passes, send all traffic to the latest version Repeat for the production environment

upvoted 0 times

...

Serita

2 months ago

A) Deploy the new version of the service to the staging environment Split the traffic, and allow 1 % of traffic through to the latest version Test the latest version If the test passes gradually roll out the latest version to the staging and production environments

upvoted 0 times

...