Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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?

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

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
16 hours ago
That way we can catch any issues early on before rolling out to all users.
upvoted 0 times
...
Tyra
7 days ago
Agreed, we can gradually increase the traffic to minimize impact.
upvoted 0 times
...
Doug
11 days ago
Option A sounds like a good plan. Let's start with 1% traffic.
upvoted 0 times
...
...
Walker
1 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
17 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
22 days ago
That way, you can monitor the performance and stability of the new release before fully deploying it.
upvoted 0 times
...
Reuben
23 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
Tanja
2 days ago
Minimize user and developer impact by thoroughly testing in staging and production environments
upvoted 0 times
...
Tyisha
22 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
...
Jarvis
2 months ago
B) That sounds like a good plan. Testing with a small percentage of traffic first is a smart move to minimize impact.
upvoted 0 times
...
Hyman
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
...
...
Shizue
2 months ago
I disagree, I believe option B is better. Splitting traffic evenly will give a more accurate test of the new version.
upvoted 0 times
...
Audra
2 months ago
I think option A is the best choice. It allows for gradual testing without impacting users and developers too much.
upvoted 0 times
...

Save Cancel