Google Exam Professional-Cloud-Architect Topic 3 Question 96 Discussion

Actual exam question for Google's Google Cloud Architect Professional exam

Question #: 96
Topic #: 3

[All Google Cloud Architect Professional 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?

AEnable the Cloud Trace API on your project and use Cloud Monitoring Alerts to send an alert based on the Cloud Trace metrics

BConfigure 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

CUse 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

DInstall Anthos Service Mesh on your cluster. Use the Google Cloud Console to define a Service Level Objective (SLO)

Show Suggested 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 days 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

3 days 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

...

Tegan

11 days 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

...

Frederica

14 days 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

18 days 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

22 days 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

25 days 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

Tambra

2 days ago

That sounds like a good plan. Anthos Config Management simplifies the process of setting up SLOs and alerts.

upvoted 0 times

...

Elbert

7 days 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

10 days 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

20 days 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

25 days 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

...