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 Exam Professional-Cloud-Architect Topic 6 Question 92 Discussion

Actual exam question for Google's Google Cloud Architect Professional exam
Question #: 92
Topic #: 6
[All Google Cloud Architect Professional 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:

Lizette
6 days 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
7 days 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
17 days 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
Tiffiny
5 days 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
6 days ago
I agree, the infrastructure team must be stressed out. Option C does seem like a safer choice.
upvoted 0 times
...
...
Naomi
21 days 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
Mica
13 days ago
A) Configure a Kubernetes autoscaling based on the subscription/num_undelivered message metric.
upvoted 0 times
...
...
Lizette
26 days ago
I think we should configure Kubernetes autoscaling based on the subscription/num_undelivered message metric.
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