Discuss Google Professional Cloud Developer Exam Topic 5 Question 88

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?

ASet the Deployment strategy to RollingUpdate with maxSurge set to 0, maxUnavailable set to 1.

BSet the Deployment strategy to RollingUpdate with maxSurge set to 1, maxUnavailable set to 0.

CSet the Deployment strategy to Recreate with maxSurge set to 0, maxUnavailable set to 1.

DSet the Deployment strategy to Recreate with maxSurge set to 1, maxUnavailable set to 0.

Suggested Answer: A

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

32 comments · newest first

Eleonore 11 months ago

C just doesn’t make sense for a rolling update scenario!

Wynell 11 months ago

I’m leaning towards A, but I’m not sure about the maxSurge setting.

Alishia 11 months ago

Wait, why would you set maxUnavailable to 0? Seems risky.

Pamela 11 months ago

Definitely agree with B, maxSurge of 1 is key!

Venita 12 months ago

I think option B is the best choice for zero downtime.

Steffanie 12 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.

Willodean 1 year 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.

Katina 1 year 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.

Alesia 1 year 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.

Melita 1 year 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.

Trevor 1 year 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.

Shanda 1 year 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.

Cristen 1 year 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.

Margurite 1 year 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.

Clay 1 year ago

I found the Local Snapshot Backup topic a bit confusing. Is it really part of RDS for MySQL, or just related?

Samira 2 years 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!

Ciara 1 year ago

↳ replying to Samira

User 4: Agreed, let's go with Option B.

Yvonne 1 year ago

↳ replying to Samira

User 3: Option B looks like the right choice, with maxSurge set to 1 and maxUnavailable set to 0.

Jordan 1 year ago

↳ replying to Samira

User 2: Yeah, we should make sure the old version is maintained until the new one is healthy.

Howard 1 year ago

↳ replying to Samira

User 1: I think we need to update the Deployment strategy.

Corinne 2 years 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!

Celestina 2 years 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.

Ceola 1 year ago

↳ replying to Celestina

I agree, RollingUpdate will ensure a smooth transition without downtime.

Maryrose 1 year ago

↳ replying to Celestina

A) Set the Deployment strategy to RollingUpdate with maxSurge set to 0, maxUnavailable set to 1.

Tyisha 2 years ago

Option B looks good to me. Maintaining the previous replicas while deploying the new version is exactly what I need.

Miles 1 year ago

↳ replying to Tyisha

User4: Let's go with option B then, it fits our requirements perfectly.

Clemencia 1 year ago

↳ replying to Tyisha

User3: That makes sense, it ensures a smooth transition to the new version.

Leonardo 1 year ago

↳ replying to Tyisha

User2: Agreed, setting maxSurge to 1 will maintain the previous replicas while deploying the new version.

Francoise 1 year ago

↳ replying to Tyisha

User1: I think option B is the way to go.

Katie 2 years 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?

Catalina 2 years ago

I disagree, I believe setting the Deployment strategy to RollingUpdate with maxSurge set to 1, maxUnavailable set to 0 is the better option.

Katie 2 years ago

I think we should set the Deployment strategy to RollingUpdate with maxSurge set to 0, maxUnavailable set to 1.

Google Professional Cloud Developer Exam - Topic 5 Question 88 Discussion