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

Google Professional Cloud DevOps Engineer Exam - Topic 12 Question 58 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 58
Topic #: 12
[All Professional Cloud DevOps Engineer Questions]

You deployed an application into a large Standard Google Kubernetes Engine (GKE) cluster. The application is stateless and multiple pods run at the same time. Your application receives inconsistent traffic. You need to ensure that the user experience remains consistent regardless of changes in traffic. and that the resource usage of the cluster is optimized.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Carey
4 months ago
B is the best choice, it scales based on demand!
upvoted 0 times
...
Virgina
4 months ago
Surprised no one mentioned D, cluster autoscaling can really help too!
upvoted 0 times
...
Tracey
4 months ago
A cron job? That seems outdated for this scenario.
upvoted 0 times
...
Ciara
4 months ago
I disagree, C might be better for optimizing resource usage.
upvoted 0 times
...
Garry
4 months ago
Definitely go with B, Horizontal Pod Autoscaler is the way to handle inconsistent traffic.
upvoted 0 times
...
Vincent
5 months ago
Cluster autoscaling sounds useful, but I feel like it’s more about managing nodes rather than ensuring consistent user experience with pod scaling.
upvoted 0 times
...
Paris
5 months ago
I practiced a similar question where we had to optimize resource usage. I think the Vertical Pod Autoscaler might help, but it focuses more on resource limits rather than scaling pods.
upvoted 0 times
...
Brittney
5 months ago
I'm a bit unsure about the cron job option. It seems like it wouldn't handle the inconsistent traffic as effectively as an autoscaler would.
upvoted 0 times
...
James
5 months ago
I remember studying about autoscalers, and I think the Horizontal Pod Autoscaler would be the right choice here since it adjusts the number of pods based on traffic.
upvoted 0 times
...
Clorinda
5 months ago
Cluster autoscaling seems like the most comprehensive solution. It can scale both the pods and the underlying nodes. I'd probably go with that to optimize the whole cluster.
upvoted 0 times
...
Shawna
5 months ago
Vertical Pod Autoscaler could be an interesting option here. It can automatically adjust the resources for each pod based on usage. Might be worth exploring that.
upvoted 0 times
...
Lonny
5 months ago
Hmm, not sure about that. Cron jobs might be a simpler solution to scale on a schedule. I'll have to think this through a bit more.
upvoted 0 times
...
Rosio
5 months ago
This looks like a classic Kubernetes scaling problem. I'd go with the Horizontal Pod Autoscaler to automatically scale the pods based on resource usage.
upvoted 0 times
...
Aliza
5 months ago
I'm a little unsure about this one. The wording is a bit tricky, and I'm not entirely sure what the "licensing issue" refers to. I'll need to read through the options carefully and try to figure out the best approach.
upvoted 0 times
...
Alyce
5 months ago
Hmm, I'm a bit confused by this question. I'm not sure if "Run" or "Robot defaults" would be the right options for publishing locally. I'll have to think this through carefully.
upvoted 0 times
...
Providencia
6 months ago
I'm a bit confused here. Do I need to add a network interface to VMSS1 or a public IP address to each member? I'll have to double-check the requirements.
upvoted 0 times
...
Lon
2 years ago
Definitely, the HPA is the clear winner here. Although the cluster autoscaling option might work as well, it's overkill for this scenario and would involve more complexity than necessary.
upvoted 0 times
...
Mona
2 years ago
Yeah, the HPA is definitely the way to go. A cron job to scale the deployment on a schedule wouldn't be flexible enough to handle the inconsistent traffic, and the Vertical Pod Autoscaler is more for scaling the resources of individual pods, not the overall deployment.
upvoted 0 times
...
Moira
2 years ago
I agree, the HPA sounds like the most appropriate solution here. It can dynamically scale the number of pods up and down based on the resource utilization, which should help maintain a consistent user experience even with fluctuating traffic.
upvoted 0 times
...
Delmy
2 years ago
Hmm, this seems like a tricky one. The question is asking how to ensure consistent user experience and optimize resource usage in a GKE cluster with inconsistent traffic. I'm leaning towards the Horizontal Pod Autoscaler (HPA) option, as that seems like the best way to automatically scale the number of pods based on the traffic demand.
upvoted 0 times
Marion
2 years ago
I think we've found the solution to the problem with the HPA option.
upvoted 0 times
...
Bethanie
2 years ago
Using HPA will keep things running smoothly regardless of traffic changes.
upvoted 0 times
...
Corrinne
2 years ago
The Horizontal Pod Autoscaler ensures the user experience remains consistent.
upvoted 0 times
...
Desirae
2 years ago
It definitely seems like the best option for optimizing resource usage.
upvoted 0 times
...
Laura
2 years ago
I agree. It sounds like the most efficient way to handle varying traffic.
upvoted 0 times
...
Carla
2 years ago
That's a good choice. HPA can adjust the number of pods based on traffic.
upvoted 0 times
...
Ryan
2 years ago
B) Configure a Horizontal Pod Autoscaler.
upvoted 0 times
...
...

Save Cancel