Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud DevOps Engineer 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?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Solange
1 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
1 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
Tijuana
1 days ago
You could consider using a Deployment with a rolling update strategy instead.
upvoted 0 times
...
Socorro
3 days ago
I agree, using a stateful set for a simple web server deployment does seem like overkill.
upvoted 0 times
...
Jutta
16 days ago
You could try using a deployment with a rolling update strategy instead.
upvoted 0 times
...
Jordan
18 days ago
I think you're right, using a stateful set might be too much for a simple web server deployment.
upvoted 0 times
...
...
Harley
1 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
15 days ago
Consider using Kubernetes Ingress to manage traffic routing during the rollout.
upvoted 0 times
...
Corinne
18 days ago
You can use Deployment strategies like RollingUpdate to control the deployment process.
upvoted 0 times
...
Malcom
1 months ago
Use Kubernetes Deployment objects to manage the rollout process.
upvoted 0 times
...
...
Lizette
2 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 days ago
A: Let's go with Deployments then for the rollout to production.
upvoted 0 times
...
Elouise
17 days ago
B: That's a good point. Deployments would be more deployment-focused than Node taints.
upvoted 0 times
...
Floyd
1 months ago
A: I think we should consider using Kubernetes Deployments for a phased rollout.
upvoted 0 times
...
...
Lisbeth
2 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
...
Vicente
2 months ago
I prefer using a replica set in the deployment specification for better scalability.
upvoted 0 times
...
Robt
2 months ago
I agree with Barb, it allows us to control the rollout process.
upvoted 0 times
...
Barb
2 months ago
I think we should use a partitioned rolling update.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77