BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Architect Topic 6 Question 92 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 92
Topic #: 6
[All Professional Cloud Architect Questions]

You company has a Kubernetes application that pulls messages from Pub/Sub and stores them in Firestore. Because the application is simple, it was deployed as a single pod. The infrastructure team has analyzed Pub/Sub metrics and discovered that the application cannot process the messages in real time. Most of them wait for minutes before being processed. You need to scale the elaboration process that is I/O-intensive. What should you do?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Anabel
1 months ago
I'm picturing the poor Kubernetes cluster trying to process all those messages like a hamster on a wheel. Option C for the win!
upvoted 0 times
...
Louvenia
1 months ago
Wait, there's a --enable-autoscaling flag? That sounds too good to be true. I'm sticking with C, it's the most straightforward way to scale based on the actual problem.
upvoted 0 times
Lashanda
21 days ago
I see your point, but I still think C is the most straightforward option to address the issue.
upvoted 0 times
...
Orville
21 days ago
I disagree, I believe D is the way to go. It allows you to configure the autoscaling parameters easily.
upvoted 0 times
...
Stephen
26 days ago
I think A is the best option, it scales based on the actual message processing metric.
upvoted 0 times
...
...
Tatum
1 months ago
Option A is tempting, but I think C is the better choice. I don't want to end up with a bunch of pods that can't keep up with the message load.
upvoted 0 times
Erinn
9 days ago
A) Configure a Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...
Tyra
10 days ago
C) Configure a Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...
Noah
18 days ago
A) Configure a Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...
...
Lizette
2 months ago
That's a good point, but I still think configuring based on the num_undelivered message metric would be more effective.
upvoted 0 times
...
Wilford
2 months ago
I disagree, I believe we should use kubectl autoscale deployment APP_NAME --max 6 --min 2 --cpu-percent 50 to configure autoscaling.
upvoted 0 times
...
Latosha
2 months ago
Haha, I bet the infrastructure team is pulling their hair out trying to keep up with all those messages! Option D looks good, but I'd probably go with C to be safe.
upvoted 0 times
Ilona
1 months ago
Yeah, it's a tough call between Option C and Option D. Both could potentially solve the issue.
upvoted 0 times
...
Tiffiny
2 months ago
I think Option D could also work well, but I see your point about going with Option C for safety.
upvoted 0 times
...
Lacey
2 months ago
I agree, the infrastructure team must be stressed out. Option C does seem like a safer choice.
upvoted 0 times
...
...
Naomi
2 months ago
Option C seems like the way to go. Scaling based on the num_undelivered message metric makes sense for an I/O-intensive application.
upvoted 0 times
Pansy
23 days ago
I agree, scaling based on the num_undelivered message metric makes perfect sense.
upvoted 0 times
...
Shaniqua
1 months ago
Option C is definitely the best choice for an I/O-intensive application.
upvoted 0 times
...
Melvin
1 months ago
C) Configure a Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...
Mica
2 months ago
A) Configure a Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...
...
Lizette
2 months ago
I think we should configure Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...

Save Cancel