Google Professional Cloud DevOps Engineer Exam - Topic 3 Question 68 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam

Question #: 68
Topic #: 3

[All Professional Cloud DevOps Engineer Questions]

You are ready to deploy a new feature of a web-based application to production. You want to use Google Kubernetes Engine (GKE) to perform a phased rollout to half of the web server pods.

What should you do?

AUse a partitioned rolling update.

BUse Node taints with NoExecute.

CUse a replica set in the deployment specification.

DUse a stateful set with parallel pod management policy.

Show Suggested Answer

Suggested Answer: B

by German at May 21, 2024, 03:37 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Brock

3 months ago

Wait, are we really using half the pods? That’s bold!

upvoted 0 times

...

Lili

3 months ago

D? Really? That seems like overkill for this.

upvoted 0 times

...

Denny

3 months ago

B sounds interesting, but not sure it fits this scenario.

upvoted 0 times

...

Latrice

4 months ago

I think C might be better for managing replicas.

upvoted 0 times

...

Bette

4 months ago

A is the way to go for phased rollouts!

upvoted 0 times

...

Virgilio

4 months ago

Stateful sets are usually for stateful applications, right? I don't think that's applicable here, but I could be wrong.

upvoted 0 times

...

Malinda

4 months ago

Node taints with NoExecute sounds familiar, but I don't think that's what we want for a phased rollout. It seems more about scheduling than deployment.

upvoted 0 times

...

Tamar

4 months ago

I remember practicing with replica sets in deployments, but I can't recall if they specifically help with phased rollouts like this one.

upvoted 0 times

...

Roxane

5 months ago

I think a partitioned rolling update might be the right choice since it allows for phased rollouts, but I'm not entirely sure if it's the best option for GKE.

upvoted 0 times

...

Darell

5 months ago

A stateful set with parallel pod management policy could work, but I'm not sure if that's the right tool for a web server deployment. I'll need to double-check the requirements.

upvoted 0 times

...

Elena

5 months ago

Using Node taints with NoExecute sounds like an interesting approach, but I'm not sure if that's the best fit for a phased rollout. I'll have to review the details on that.

upvoted 0 times

...

Xenia

5 months ago

Hmm, I'm a bit confused about the difference between a rolling update and a replica set. I'll have to think this through carefully.

upvoted 0 times

...

German

5 months ago

I'm pretty confident this is a rolling update scenario, so I'll go with option A.

upvoted 0 times

...

Javier

5 months ago

This one seems pretty straightforward. I'm pretty sure the RSA Archer Public Sector solution helps organizations reach compliance with FISMA.

upvoted 0 times

...

Amina

5 months ago

This seems like a straightforward question. The satisfaction scale is clearly ordinal, with 1 being the lowest and 5 being the highest. I'm confident I can select the right answer.

upvoted 0 times

...

Brittni

5 months ago

I think if the logs are full, they might not show any new events, which could make debugging harder, but I'm not entirely sure if that's the main issue here.

upvoted 0 times

...

Junita

5 months ago

Okay, let me think this through. The key is to identify which of the given strategies are valid according to the ISTQB syllabus. I'll eliminate the options that don't match.

upvoted 0 times

...

Solange

9 months ago

I'm just here for the free donuts. Oh, the question? Hmm, I'd go with A. Sounds like the most straightforward way to do a phased rollout.

upvoted 0 times

...

Glenna

9 months ago

D is an interesting option, but a stateful set with parallel pod management policy seems overkill for a simple web server deployment. Isn't that more for stateful applications?

upvoted 0 times

Ilda

8 months ago

Agreed, let's go with a deployment and rolling update strategy for the phased rollout.

upvoted 0 times

...

Kati

8 months ago

That's a good point, a rolling update strategy would be more suitable for this scenario.

upvoted 0 times

...

Kanisha

8 months ago

That way you can easily control the number of pods being updated at a time.

upvoted 0 times

...

Tijuana

8 months ago

You could consider using a Deployment with a rolling update strategy instead.

upvoted 0 times

...

Socorro

8 months ago

I agree, using a stateful set for a simple web server deployment does seem like overkill.

upvoted 0 times

...

Jutta

9 months ago

You could try using a deployment with a rolling update strategy instead.

upvoted 0 times

...

Jordan

9 months ago

I think you're right, using a stateful set might be too much for a simple web server deployment.

upvoted 0 times

...

Harley

10 months ago

C is a nice idea, but a replica set alone won't give you the control you need for a phased rollout. I'd want something more specific to the deployment process.

upvoted 0 times

Laurel

9 months ago

Consider using Kubernetes Ingress to manage traffic routing during the rollout.

upvoted 0 times

...

Corinne

9 months ago

You can use Deployment strategies like RollingUpdate to control the deployment process.

upvoted 0 times

...

Malcom

9 months ago

Use Kubernetes Deployment objects to manage the rollout process.

upvoted 0 times

...

Lizette

10 months ago

B sounds interesting, but I'm not sure Node taints with NoExecute are the right tool for this task. Shouldn't we be looking at something more deployment-focused?

upvoted 0 times

Eric

9 months ago

A: Let's go with Deployments then for the rollout to production.

upvoted 0 times

...

Elouise

9 months ago

B: That's a good point. Deployments would be more deployment-focused than Node taints.

upvoted 0 times

...

Floyd

9 months ago

A: I think we should consider using Kubernetes Deployments for a phased rollout.

upvoted 0 times

...

Lisbeth

10 months ago

I think option A is the way to go. A partitioned rolling update allows you to gradually roll out the new feature to a subset of the pods, which seems perfect for this scenario.

upvoted 0 times

...