Cyber Monday 2024! 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 3 Question 96 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 96
Topic #: 3
[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 Cornell at Sep 15, 2024, 01:18 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Ernest
2 months ago
I'm all about efficiency, so Option B gets my vote. Defining the SLO and alerts in a YAML file and deploying it with Anthos Config Management is a nice clean approach.
upvoted 0 times
...
Eloisa
2 months ago
Haha, I bet the SRE team is always on the lookout for any excuse to use more GCP services. Option A sounds like a classic 'throw more tools at the problem' solution.
upvoted 0 times
Kirby
1 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
...
Vilma
1 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
...
Barbra
1 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
...
...
Tegan
2 months ago
Option C looks interesting, but using Cloud Profiler and custom metrics might be overkill for this use case. I'd stick with the more streamlined approaches in Options B or D.
upvoted 0 times
Basilia
1 months ago
D) Install Anthos Service Mesh on your cluster. Use the Google Cloud Console to define a Service Level Objective (SLO)
upvoted 0 times
...
Lorean
2 months ago
Option C looks interesting, but using Cloud Profiler and custom metrics might be overkill for this use case. I'd stick with the more streamlined approaches in Options B or D.
upvoted 0 times
...
Dwight
2 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
...
Devorah
2 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
...
Ardella
2 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
...
Milly
2 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
...
...
Frederica
3 months ago
I see both points, but I think option C could also work. Using Cloud Profiler to create custom metrics and set up alerts seems efficient.
upvoted 0 times
...
Deja
3 months ago
I disagree, I believe option B is more suitable. Anthos Config Management allows us to define SLO and alerting policies easily.
upvoted 0 times
...
Felicidad
3 months ago
I'd go with Option D. Anthos Service Mesh provides a comprehensive solution for managing service-level objectives and generating alerts. Seems like the most robust option.
upvoted 0 times
...
Gwenn
3 months ago
Option B seems like the most straightforward approach to handle the SRE requirements. Anthos Config Management makes it easy to define and deploy the necessary SLO and alerting policies.
upvoted 0 times
Sherman
2 months ago
I see, using Cloud Trace API and Cloud Monitoring Alerts is another valid option for monitoring request latency.
upvoted 0 times
...
Ben
2 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
...
Tambra
2 months ago
That sounds like a good plan. Anthos Config Management simplifies the process of setting up SLOs and alerts.
upvoted 0 times
...
Elbert
2 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
...
Jamal
2 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
...
Daniel
3 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
...
...
Gwenn
3 months ago
I think option A is the best choice. Cloud Trace API can help us monitor request latency and set up alerts.
upvoted 0 times
...

Save Cancel