MENU
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?
Suggested Answer: B, D
Get Premium Professional Cloud DevOps Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
41 comments · newest first
CA
Cassandra
11 months ago
Wait, can you really just delete the staging environment? That seems extreme!
LO
Lonna
11 months ago
D is interesting, but deleting the old environment feels risky.
PA
Paulene
11 months ago
C seems smart, testing without serving traffic is a good idea.
MI
Micheline
11 months ago
I disagree, B is too risky with 50% traffic at once!
LI
Linwood
12 months ago
A sounds like a safe approach, gradual rollout is key.
WI
Wilbert
12 months ago
I recall something about green-blue deployments. Option D seems like it could work, but I'm not sure about deleting the existing environment right away.
RY
Ryan
1 year ago
I think option C sounds familiar. Testing without serving traffic first seems like a good way to ensure stability before rolling out.
ME
Melvin
1 year ago
I'm not entirely sure, but I feel like allowing 50% traffic could be too risky for production. Maybe we should stick to a smaller percentage first?
LA
Launa
1 year ago
I remember we discussed traffic splitting in our last practice session. I think starting with 1% traffic is a safer approach to minimize risk.
BE
Bernardine
1 year ago
This is a tricky one, but I think the best approach is to start small in staging and slowly ramp up the traffic to the new version. Option A seems like the safest bet to minimize user and developer impact. Gotta love those gradual rollouts!
GA
Gabriele
1 year ago
Okay, I think I've got this. The key is to test the new version extensively in staging before deploying to production. Option D with the green environment sounds like a good way to do that without disrupting the current production setup. I'm going to go with that one.
AL
Alyce
1 year ago
Hmm, I'm a bit confused by all the different options here. Splitting traffic 50/50 in staging seems risky to me, even if the test passes. I'm leaning more towards option C and gradually rolling out the new version with a new tag.
CA
Catalina
1 year ago
This seems like a pretty straightforward question about rolling out a new microservice version with minimal impact. I think option A is the way to go - slowly ramping up traffic to the new version in staging before fully deploying it.
RE
Remedios
1 year ago
Hmm, this question seems straightforward, but I want to make sure I understand the details correctly. I'll read through the options carefully and think about which ones best describe the CUIC database.
TA
Talia
1 year ago
I'm feeling unsure on this one. I know assurance is important, but did we cover avoidance specifically in our notes?
BA
Basilia
1 year ago
I think I know the answer to this. The requirement that the service be "solely for the convenience of the member" is the one that doesn't fit with the others. I'll go with that.
CH
Chauncey
1 year ago
I'm pretty confident the answer is 4 network cards. The question states the planes are "different from each other through up to", which implies a maximum of 4 different network cards.
KE
Kenneth
1 year 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.
ER
Eric
1 year ago
That way we can catch any issues early on before rolling out to all users.
TY
Tyra
1 year ago
Agreed, we can gradually increase the traffic to minimize impact.
DO
Doug
1 year ago
Option A sounds like a good plan. Let's start with 1% traffic.
WA
Walker
1 year 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.
HO
Hollis
1 year ago
It's a good way to minimize impact on users and developers while ensuring the new version works as expected.
SA
Sabina
1 year ago
That way, you can monitor the performance and stability of the new release before fully deploying it.
RE
Reuben
1 year ago
You could use traffic splitting to gradually shift traffic to the new version in production.
DW
Dwight
2 years 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.
FL
Florinda
1 year ago
It's important to prioritize stability and minimize disruptions during deployment
TA
Tanja
1 year ago
Minimize user and developer impact by thoroughly testing in staging and production environments
TY
Tyisha
1 year ago
This will help ensure stability before rolling out the new release
ST
Stephaine
1 year ago
Use the new-release tag approach to test the new version without serving traffic
RY
Ryan
2 years 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.
AU
Audra
2 years ago
That's a good point, Shizue. But I still think minimizing impact is crucial, so I prefer option A.
TR
Troy
2 years 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.
JO
Jose
1 year ago
B) Absolutely, gradual rollout helps catch any issues early on without affecting all users at once.
BO
Bonita
1 year ago
A) Yes, it's important to ensure the new version works as expected before rolling it out to all users.
LO
Louis
1 year 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
SE
Serita
1 year 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
JA
Jarvis
2 years ago
B) That sounds like a good plan. Testing with a small percentage of traffic first is a smart move to minimize impact.
HY
Hyman
2 years 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
SH
Shizue
2 years ago
I disagree, I believe option B is better. Splitting traffic evenly will give a more accurate test of the new version.
AU
Audra
2 years ago
I think option A is the best choice. It allows for gradual testing without impacting users and developers too much.