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

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?
D) Install Anthos Service Mesh on your cluster. Use the Google Cloud Console to define a Service Level Objective (SLO)
A) Enable the Cloud Trace API on your project and use Cloud Monitoring Alerts to send an alert based on the Cloud Trace metrics
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
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

Google Professional Cloud Architect (PR000213) Exam - Topic 5 Question 90 Discussion

Actual exam question for Google's Professional Cloud Architect (PR000213) exam
Question #: 90
Topic #: 5
[All Professional Cloud Architect (PR000213) 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 (PR000213) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Belen
9 months ago
C might be overkill for just latency tracking.
upvoted 0 times
...
Garry
9 months ago
D is solid if you're already using Anthos Service Mesh.
upvoted 0 times
...
Barb
10 months ago
Wait, can you really use Cloud Profiler for this? Sounds odd.
upvoted 0 times
...
Elbert
10 months ago
I think B could work too, but it seems more complex.
upvoted 0 times
...
Sol
10 months ago
A is the way to go for latency alerts!
upvoted 0 times
...
Kimberlie
10 months ago
I’m a bit confused about whether to use Anthos Config Management or just set up alerts directly in Cloud Monitoring. Both seem relevant to the question.
upvoted 0 times
...
Silvana
11 months ago
I feel like we did a similar question where we had to choose between Cloud Trace and Cloud Profiler. I think Cloud Trace might be the right choice here.
upvoted 0 times
...
Kimi
11 months ago
I think option D sounds familiar because we practiced setting up SLOs with Anthos Service Mesh, but I can't recall the exact steps.
upvoted 0 times
...
Ivory
11 months ago
I remember we talked about using Cloud Monitoring for alerts, but I'm not sure if it was specifically for request latency.
upvoted 0 times
...
In
11 months ago
I'm leaning towards option C. Using Cloud Profiler to track the request latency and then creating a custom metric and alerting policy in Cloud Monitoring seems like a comprehensive solution. I'll make sure I understand how to set that up properly.
upvoted 0 times
...
Arlette
11 months ago
Option B looks interesting - using Anthos Config Management to define the SLO and alerting policy. That could be a good way to manage the configuration as code. I'll need to research that approach a bit more.
upvoted 0 times
...
Karon
11 months ago
This seems like a straightforward question about monitoring and alerting on Anthos clusters. I think I'll go with option A - enabling the Cloud Trace API and using Cloud Monitoring Alerts.
upvoted 0 times
...
Marsha
11 months ago
Hmm, I'm a bit unsure about this one. The options seem to cover different tools and approaches. I'll need to think through the details of each one to decide which is the best fit for the given requirements.
upvoted 0 times
...
Vincent
11 months ago
This looks like a classic IAM management question. I think the best approach here is to use IAM groups to organize access based on department or job function. That way we can easily add and remove users from groups as needed.
upvoted 0 times
...
Owen
11 months ago
I've got this one! Class C is the answer for fires involving energized electrical equipment.
upvoted 0 times
...
Major
2 years 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
2 years ago
Samira: That's true, but sometimes it's nice to have a hands-off approach with Option D.
upvoted 0 times
...
Isreal
2 years ago
I prefer Option A, enabling Cloud Trace API and using Cloud Monitoring Alerts. It gives me more control.
upvoted 0 times
...
Samira
2 years ago
Yeah, it's like Netflix and chill for SRE. Set it and forget it.
upvoted 0 times
...
Jacqueline
2 years ago
Option D sounds like the easy way out. Just let Google Cloud Console handle everything.
upvoted 0 times
...
...
Tesha
2 years ago
That's a good point, Twana. We should consider all options before making a decision.
upvoted 0 times
...
Rima
2 years 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
2 years ago
Option B is the way to go. Anthos Config Management - the Swiss Army knife of Kubernetes config management!
upvoted 0 times
Margart
2 years ago
That's a great choice! Anthos Config Management is really powerful for managing configurations in Kubernetes.
upvoted 0 times
...
Corinne
2 years 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
2 years 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
2 years 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
2 years ago
I think option A is the best choice. Cloud Trace API can help us monitor request latency.
upvoted 0 times
...
Julieta
2 years 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
2 years 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
2 years 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
2 years 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
2 years 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