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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Developer Exam - Topic 5 Question 88 Discussion

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

Your application is deployed in a Google Kubernetes Engine (GKE) cluster. When a new version of your application is released, your CI/CD tool updates the spec.template.spec.containers[0].image value to reference the Docker image of your new application version. When the Deployment object applies the change, you want to deploy at least 1 replica of the new version and maintain the previous replicas until the new replica is healthy.

Which change should you make to the GKE Deployment object shown below?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Reita at Jul 18, 2024, 12:40 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Eleonore
3 months ago
C just doesn’t make sense for a rolling update scenario!
upvoted 0 times
...
Wynell
3 months ago
I’m leaning towards A, but I’m not sure about the maxSurge setting.
upvoted 0 times
...
Alishia
4 months ago
Wait, why would you set maxUnavailable to 0? Seems risky.
upvoted 0 times
...
Pamela
4 months ago
Definitely agree with B, maxSurge of 1 is key!
upvoted 0 times
...
Venita
4 months ago
I think option B is the best choice for zero downtime.
upvoted 0 times
...
Steffanie
4 months ago
I’m not entirely confident, but I think maxUnavailable should be set to 1 to ensure we always have at least one replica running. I need to double-check that.
upvoted 0 times
...
Willodean
5 months ago
I feel like I might confuse the Recreate strategy with RollingUpdate. I remember that Recreate takes down all old pods before starting new ones, which doesn't seem to fit this scenario.
upvoted 0 times
...
Katina
5 months ago
I think option B sounds right because we want to ensure at least one new replica is up before taking down the old ones. That aligns with what we practiced.
upvoted 0 times
...
Alesia
5 months ago
I remember that with RollingUpdate, we can control how many replicas are updated at once, but I'm not sure about the maxSurge and maxUnavailable values.
upvoted 0 times
...
Melita
5 months ago
I'm feeling pretty confident about this one. The question is asking us to deploy the new version while maintaining the previous replicas, so option B seems like the right choice.
upvoted 0 times
...
Trevor
5 months ago
Okay, I think I've got this. The key is to maintain the previous replicas while deploying the new version, so I'll go with option B - RollingUpdate with maxSurge set to 1 and maxUnavailable set to 0.
upvoted 0 times
...
Shanda
5 months ago
Hmm, I'm a bit confused about the difference between RollingUpdate and Recreate strategies. I'll need to review the documentation to make sure I understand the implications of each choice.
upvoted 0 times
...
Cristen
5 months ago
This looks like a tricky Kubernetes question. I'll need to carefully consider the deployment strategy options and how they impact the rollout of the new version.
upvoted 0 times
...
Margurite
5 months ago
This one seems straightforward - bid/no-bid and proposal preparation are definitely part of the pre-award phase, so I'm going with A.
upvoted 0 times
...
Clay
5 months ago
I found the Local Snapshot Backup topic a bit confusing. Is it really part of RDS for MySQL, or just related?
upvoted 0 times
...
Samira
10 months ago
Hmm, let me think about this. I need to keep the old version running while the new one is deployed. Yep, Option B is the winner!
upvoted 0 times
Ciara
9 months ago
User 4: Agreed, let's go with Option B.
upvoted 0 times
...
Yvonne
9 months ago
User 3: Option B looks like the right choice, with maxSurge set to 1 and maxUnavailable set to 0.
upvoted 0 times
...
Jordan
9 months ago
User 2: Yeah, we should make sure the old version is maintained until the new one is healthy.
upvoted 0 times
...
Howard
9 months ago
User 1: I think we need to update the Deployment strategy.
upvoted 0 times
...
...
Corinne
11 months ago
Haha, this question is a piece of cake! I'm gonna ace this exam with my Kubernetes knowledge. Option B all the way, baby!
upvoted 0 times
...
Celestina
11 months ago
I'm not sure about this. Doesn't the Recreate strategy mean the old version will be completely replaced? I think the RollingUpdate is the better choice here.
upvoted 0 times
Ceola
10 months ago
I agree, RollingUpdate will ensure a smooth transition without downtime.
upvoted 0 times
...
Maryrose
10 months ago
A) Set the Deployment strategy to RollingUpdate with maxSurge set to 0, maxUnavailable set to 1.
upvoted 0 times
...
...
Tyisha
11 months ago
Option B looks good to me. Maintaining the previous replicas while deploying the new version is exactly what I need.
upvoted 0 times
Miles
9 months ago
User4: Let's go with option B then, it fits our requirements perfectly.
upvoted 0 times
...
Clemencia
9 months ago
User3: That makes sense, it ensures a smooth transition to the new version.
upvoted 0 times
...
Leonardo
9 months ago
User2: Agreed, setting maxSurge to 1 will maintain the previous replicas while deploying the new version.
upvoted 0 times
...
Francoise
10 months ago
User1: I think option B is the way to go.
upvoted 0 times
...
...
Katie
11 months ago
But wouldn't setting maxSurge to 0 ensure that we deploy at least 1 replica of the new version before removing the old ones?
upvoted 0 times
...
Catalina
11 months ago
I disagree, I believe setting the Deployment strategy to RollingUpdate with maxSurge set to 1, maxUnavailable set to 0 is the better option.
upvoted 0 times
...
Katie
11 months ago
I think we should set the Deployment strategy to RollingUpdate with maxSurge set to 0, maxUnavailable set to 1.
upvoted 0 times
...

Save Cancel