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 Exam Professional Cloud Architect Topic 5 Question 90 Discussion

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

You have deployed an application on Anthos clusters (formerly Anthos GKE). According to the SRE practices at your company you need to be alerted if the request latency is above a certain threshold for a specified amount of time. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

https://cloud.google.com/service-mesh/docs/overview

https://cloud.google.com/service-mesh/docs/observability/slo-overview


by Karol at Aug 27, 2024, 06:49 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Major
10 months ago
Option D, where the Google Cloud Console does all the work for me? Sign me up! I'll call that the 'Netflix and chill' approach to SRE.
upvoted 0 times
Timothy
8 months ago
Samira: That's true, but sometimes it's nice to have a hands-off approach with Option D.
upvoted 0 times
...
Isreal
9 months ago
I prefer Option A, enabling Cloud Trace API and using Cloud Monitoring Alerts. It gives me more control.
upvoted 0 times
...
Samira
9 months ago
Yeah, it's like Netflix and chill for SRE. Set it and forget it.
upvoted 0 times
...
Jacqueline
9 months ago
Option D sounds like the easy way out. Just let Google Cloud Console handle everything.
upvoted 0 times
...
...
Tesha
10 months ago
That's a good point, Twana. We should consider all options before making a decision.
upvoted 0 times
...
Rima
10 months ago
Option C is interesting, but using Cloud Profiler just to create a custom metric feels a bit overkill. Why not just use Anthos Service Mesh like in Option D?
upvoted 0 times
...
Rhea
10 months ago
Option B is the way to go. Anthos Config Management - the Swiss Army knife of Kubernetes config management!
upvoted 0 times
Margart
9 months ago
That's a great choice! Anthos Config Management is really powerful for managing configurations in Kubernetes.
upvoted 0 times
...
Corinne
9 months ago
B) Configure Anthos Config Management on your cluster and create a yaml file that defines the SLO and alerting policy you want to deploy in your cluster
upvoted 0 times
...
...
Twana
10 months ago
I see your point, Lashon. But I think option C is also a good option. Cloud Profiler can provide valuable insights for creating custom metrics.
upvoted 0 times
...
Lashon
10 months ago
I disagree, I believe option B is more suitable. Anthos Config Management allows us to define SLO and alerting policy.
upvoted 0 times
...
Tesha
10 months ago
I think option A is the best choice. Cloud Trace API can help us monitor request latency.
upvoted 0 times
...
Julieta
10 months ago
Option A seems like a good choice, but I'm not sure if it covers the 'specified amount of time' requirement. Cloud Trace might just give us instant metrics.
upvoted 0 times
Sheron
9 months ago
A) Cloud Trace does provide the ability to set up alerts based on specific conditions, including duration. It should cover the 'specified amount of time' requirement.
upvoted 0 times
...
Barrie
9 months ago
C) Use Cloud Profiler to follow up the request latency. Create a custom metric in Cloud Monitoring based on the results of Cloud Profiler, and create an Alerting Policy in case this metric exceeds the threshold
upvoted 0 times
...
Nichelle
10 months ago
B) Configure Anthos Config Management on your cluster and create a yaml file that defines the SLO and alerting policy you want to deploy in your cluster
upvoted 0 times
...
Golda
10 months ago
A) Enable the Cloud Trace API on your project and use Cloud Monitoring Alerts to send an alert based on the Cloud Trace metrics
upvoted 0 times
...
...

Save Cancel