You manage a critical API running on Cloud Run that serves an average of 10,000 requests per minute. You need to define service level objectives (SLOs) for availability and latency to ensure that the

Question

Options

• AConfigure Cloud Monitoring to send alerts when average API latency exceeds 150 ms or the error
• BPrioritize latency as the only SLO, targeting 100 ms for 99% of requests.
• CSet SLOs for 99% availability at 99% and 500 ms latency for 90% of requests. Use Cloud
• DSet SLOs for the API by using availability and latency service level indicators. Use Cloud

• A
  8% (2)
• B
  17% (4)
• C
  4% (1)
• D
  71% (17)

Explanation

Meeting the stated user expectations requires defining SLOs that match them exactly: 99.9% availability and p95 latency ≤ 200 ms. These are measured using Service Level Indicators (SLIs), and Cloud Monitoring's SLO features provide the tooling to define, track, and alert on SLOs using burn rate alerts. Option A configures alerts but not formal SLOs, and the thresholds (150 ms average, unspecified availability) don't match requirements. Option B ignores availability entirely and sets stricter/different latency targets. Option C uses incorrect targets (99% availability, 500 ms latency at p90) that are weaker than what users expect.

No community discussion yet for this question.