New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud Developer Exam - Topic 15 Question 102 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 102
Topic #: 15
[All Professional Cloud Developer Questions]

You have an application controlled by a managed instance group. When you deploy a new version of the application, costs should be minimized and the number of instances should not increase. You want to ensure that, when each new instance is created, the deployment only continues if the new instance is healthy. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Latanya
3 months ago
D is definitely not the right choice, too many unhealthy instances!
upvoted 0 times
...
Teddy
3 months ago
C doesn't make sense, we need healthy instances!
upvoted 0 times
...
Shoshana
3 months ago
Wait, can you really set maxSurge to 0? Sounds risky!
upvoted 0 times
...
Wenona
4 months ago
I disagree, B seems more reliable for health checks.
upvoted 0 times
...
Carli
4 months ago
A is the way to go! Keeps costs down.
upvoted 0 times
...
Mona
4 months ago
I’m leaning towards option B since it seems to ensure that we only take down one instance at a time, but I’m not entirely sure about the surge settings.
upvoted 0 times
...
Paola
4 months ago
I practiced a similar question where we had to ensure health checks were in place. I feel like maxUnavailable should be 0 to avoid issues.
upvoted 0 times
...
Anisha
4 months ago
I think option A sounds familiar because it allows for one new instance while keeping the others healthy, but I’m not completely confident.
upvoted 0 times
...
Tamekia
5 months ago
I remember studying rolling updates, but I'm not sure if maxSurge or maxUnavailable is the right choice here.
upvoted 0 times
...
Truman
5 months ago
I've done a few rolling updates before, so I think I've got a good handle on this. I'll go with option A - that seems like the best way to minimize costs and ensure healthy instances.
upvoted 0 times
...
Iluminada
5 months ago
I'm a bit confused by the different settings for maxSurge, maxUnavailable, maxHealthy, and maxUnhealthy. I'll need to make sure I understand how they work to pick the right approach.
upvoted 0 times
...
Ty
5 months ago
Okay, let's see. I think the key is to use a rolling update with the right settings to control the number of instances and health checks. I'll need to review the options closely.
upvoted 0 times
...
Curtis
5 months ago
Hmm, this seems like a tricky one. I'll need to think through the deployment options carefully to minimize costs and ensure the new instances are healthy.
upvoted 0 times
...
Izetta
9 months ago
Wait, are we deploying the app or playing a game of 'Who's the Healthiest'? I'm so confused, but I'll go with Option A just to be safe.
upvoted 0 times
...
Daron
10 months ago
Option D, the 'Healthy Unhealthy' approach! I love it, it's like a game of health tug-of-war.
upvoted 0 times
Marti
8 months ago
C) Perform a rolling-action with maxHealthy set to 1, maxUnhealthy set to 0.
upvoted 0 times
...
Rebbecca
8 months ago
B) Perform a rolling-action with maxSurge set to 0, maxUnavailable set to 1
upvoted 0 times
...
Earnestine
8 months ago
A) Perform a rolling-action with maxSurge set to 1, maxUnavailable set to 0.
upvoted 0 times
...
Linn
8 months ago
C) Perform a rolling-action with maxHealthy set to 1, maxUnhealthy set to 0.
upvoted 0 times
...
Roxane
8 months ago
B) Perform a rolling-action with maxSurge set to 0, maxUnavailable set to 1
upvoted 0 times
...
Nana
8 months ago
A) Perform a rolling-action with maxSurge set to 1, maxUnavailable set to 0.
upvoted 0 times
...
...
Hannah
10 months ago
Hmm, Option C looks promising. Ensuring the new instance is healthy before continuing, that's a smart move.
upvoted 0 times
Kenneth
9 months ago
User 4: Let's go with Option C then, sounds like the best choice.
upvoted 0 times
...
Zita
9 months ago
User 3: Agreed, it's a smart way to minimize costs and ensure stability.
upvoted 0 times
...
Glendora
9 months ago
User 2: Yeah, making sure the new instance is healthy first is important.
upvoted 0 times
...
Lettie
9 months ago
User 3: Agreed, it's a smart move to minimize costs and ensure stability.
upvoted 0 times
...
Felix
9 months ago
User 2: Yeah, making sure the new instance is healthy is important.
upvoted 0 times
...
Gilma
10 months ago
User 1: I think Option C is the way to go.
upvoted 0 times
...
Helga
10 months ago
User 1: I think Option C is the way to go.
upvoted 0 times
...
...
Kirk
10 months ago
I'm leaning towards Option B. Keeping the number of instances the same while rolling out the new version - sounds good to me!
upvoted 0 times
Ardella
9 months ago
User 2: Yeah, keeping the number of instances the same is important.
upvoted 0 times
...
Thaddeus
9 months ago
User 1: I think Option B is the way to go.
upvoted 0 times
...
...
Slyvia
10 months ago
But with maxSurge set to 1, we can ensure that only one new instance is created at a time to minimize costs.
upvoted 0 times
...
Chauncey
10 months ago
I disagree, I believe the correct answer is B.
upvoted 0 times
...
Dalene
11 months ago
Option A seems like the way to go. Minimizing costs and ensuring the new instance is healthy before moving forward - that's exactly what we need!
upvoted 0 times
...
Slyvia
11 months ago
I think the answer is A.
upvoted 0 times
...

Save Cancel