Deal of The Day! 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 9 Question 68 Discussion

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?
A) Perform a rolling update with a PodDisruptionBudget of 80%.
B) Perform a rolling update with a HorizontalPodAutoscaler scale-down policy value of 0.
C) Convert the Deployment to a StatefulSet, and perform a rolling update with a PodDisruptionBudget of 80%.
D) Convert the Deployment to a StatefulSet, and perform a rolling update with a HorizontalPodAutoscaler scale-down policy value of 0.

Google Professional Cloud Developer Exam - 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

by Eun at Apr 24, 2023, 12:49 AM

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
Ronny
7 months ago
B doesn't make sense, scale-down policy should be more flexible!
upvoted 0 times
...
Lucille
7 months ago
Rolling updates are definitely the best practice here.
upvoted 0 times
...
Rene
7 months ago
Wait, why would you convert to a StatefulSet? Isn't that overkill?
upvoted 0 times
...
Madelyn
8 months ago
I disagree, C seems more reliable for stateful apps.
upvoted 0 times
...
Jacquline
8 months ago
A is the way to go for minimizing risk!
upvoted 0 times
...
Stefania
8 months ago
I practiced a similar question where we had to minimize downtime during updates. I think a rolling update is definitely the way to go, but I can't recall the exact details about the PodDisruptionBudget.
upvoted 0 times
...
Jacinta
8 months ago
I feel like the HorizontalPodAutoscaler scale-down policy might not be the best choice here. We want to ensure availability during the update, right?
upvoted 0 times
...
Peter
8 months ago
I think a StatefulSet is more for applications that require stable identities, so I'm leaning towards just using a Deployment for this question.
upvoted 0 times
...
Novella
8 months ago
I remember we discussed rolling updates in class, but I'm not sure about the specifics of using a PodDisruptionBudget.
upvoted 0 times
...
Anisha
8 months ago
The license plate is probably the Technical Resource, since that's the physical asset being used for the rental service.
upvoted 0 times
...
Lon
8 months ago
Okay, let's see. Confidentiality is important to protect sensitive information and prevent misuse. I think option C is the best answer here.
upvoted 0 times
...
Detra
8 months ago
I think the key here is understanding the replication and search factor settings. With a replication factor of 2, the cluster would need at least two indexers to be able to ingest data. So my guess is that the cluster would be "Indexing Ready" after Step 6, when the second indexer has joined.
upvoted 0 times
...
Melodie
1 year 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 year 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
Phung
11 months ago
Let's go with the rolling update with a PodDisruptionBudget then. It's the safest bet.
upvoted 0 times
...
Maricela
11 months ago
I would go with option A as well. It's better to minimize risk.
upvoted 0 times
...
Pauline
11 months ago
Yeah, I agree. It's a cautious approach without being too conservative.
upvoted 0 times
...
Emerson
12 months ago
I think option A sounds like a good choice.
upvoted 0 times
...
...
Devorah
1 year 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
12 months ago
Converting to a StatefulSet might be too complex for this situation.
upvoted 0 times
...
Allene
1 year ago
C) Convert the Deployment to a StatefulSet, and perform a rolling update with a PodDisruptionBudget of 80%.
upvoted 0 times
...
Micaela
1 year ago
A) Perform a rolling update with a PodDisruptionBudget of 80%.
upvoted 0 times
...
...
Willow
1 year 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
1 year ago
Using a PodDisruptionBudget of 80% is a safer option to minimize risk.
upvoted 0 times
...
Mendy
1 year ago
A) Perform a rolling update with a PodDisruptionBudget of 80%.
upvoted 0 times
...
...
Haydee
1 year 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
1 year ago
Why do you think option D is better?
upvoted 0 times
...
Denny
1 year ago
I disagree, I believe option D is the best choice.
upvoted 0 times
...
Katlyn
1 year ago
I think we should go with option A.
upvoted 0 times
...

Save Cancel