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-Developer Topic 14 Question 91 Discussion

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

You are developing an online gaming platform as a microservices application on Google Kubernetes Engine (GKE). Users on social media are complaining about long loading times for certain URL requests to the application. You need to investigate performance bottlenecks in the application and identify which HTTP requests have a significantly high latency span in user requests. What should you do9

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Ngoc
3 days ago
Configuring GKE workload metrics in Cloud Monitoring could also help us identify performance bottlenecks.
upvoted 0 times
...
Valentin
4 days ago
I think we should also consider installing the Open Telemetry tracing package to analyze user requests.
upvoted 0 times
...
Rupert
6 days ago
Hmm, option D seems the most comprehensive. Monitoring the GKE cluster metrics in Cloud Monitoring could give you a wide range of insights into the performance issues.
upvoted 0 times
...
Azalee
10 days ago
I'd go with option A. Logging is a good start, and analyzing the logs in Cloud Logging should give you a good idea of which requests are taking too long.
upvoted 0 times
...
Hyman
13 days ago
Option C sounds like the way to go. Tracing is crucial for identifying performance bottlenecks in a microservices architecture. I'm glad they mentioned Open Telemetry, it's a great tool for this.
upvoted 0 times
...
Golda
14 days ago
I agree with Trinidad. Using logs to evaluate latency across different methods and URL paths is a good idea.
upvoted 0 times
...
Trinidad
24 days ago
I think we should update our microservices to log HTTP requests and analyze the latency.
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