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 Developer Topic 9 Question 68 Discussion

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

You plan to deploy a new application revision with a Deployment resource to Google Kubernetes Engine (GKE) in production. The container might not work correctly. You want to minimize risk in case there are issues after deploying the revision. You want to follow Google-recommended best practices. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Melodie
30 days ago
Hmm, this question is making me hungry. I could really go for a nice StatefulSet sandwich right about now.
upvoted 0 times
...
Shawana
1 months ago
Converting to a StatefulSet and using a HorizontalPodAutoscaler scale-down policy of 0 is the most cautious approach, but it might be a bit too conservative. I'd probably go with the rolling update with a PodDisruptionBudget.
upvoted 0 times
Emerson
2 days ago
I think option A sounds like a good choice.
upvoted 0 times
...
...
Devorah
1 months ago
Converting the Deployment to a StatefulSet and using a PodDisruptionBudget of 80% is an interesting approach, but it might be overkill for a simple application update. Seems like a lot of extra complexity.
upvoted 0 times
Howard
2 days ago
Converting to a StatefulSet might be too complex for this situation.
upvoted 0 times
...
Allene
20 days ago
C) Convert the Deployment to a StatefulSet, and perform a rolling update with a PodDisruptionBudget of 80%.
upvoted 0 times
...
Micaela
21 days ago
A) Perform a rolling update with a PodDisruptionBudget of 80%.
upvoted 0 times
...
...
Willow
2 months ago
Using a HorizontalPodAutoscaler scale-down policy value of 0 might be a bit overkill. That would prevent any pods from being scaled down during the update, which could lead to a lot of unnecessary resource usage.
upvoted 0 times
Luis
2 months ago
Using a PodDisruptionBudget of 80% is a safer option to minimize risk.
upvoted 0 times
...
Mendy
2 months ago
A) Perform a rolling update with a PodDisruptionBudget of 80%.
upvoted 0 times
...
...
Haydee
2 months ago
Rolling update with a PodDisruptionBudget of 80% sounds like a good way to minimize the risk. It'll ensure that a certain percentage of the pods are always available during the update.
upvoted 0 times
...
Katlyn
2 months ago
Why do you think option D is better?
upvoted 0 times
...
Denny
2 months ago
I disagree, I believe option D is the best choice.
upvoted 0 times
...
Katlyn
2 months ago
I think we should go with option A.
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