Examkin

Soru

Zorluk: OrtaDefining and Managing SLOs, SLIs, and Error Budgets

A healthcare organization operates a patient scheduling service hosted on Google Cloud Run backed by Cloud Spanner. The Site Reliability Engineering (SRE) team needs to establish a reliability strategy that balances release velocity with an availability SLO of 99.9% per 30-day rolling window. The team wants to ensure that on-call engineers are paged only for significant reliability risks while transient spikes are ignored. Which TWO practices should the SRE team implement? (Select TWO.)

  1. Configure multi-window, multi-burn-rate alerting based on the consumption speed of the 30-day error budget.Cevap
  2. Define the Service Level Indicator (SLI) as the ratio of successful HTTP request executions (non-5xx responses) over the total number of valid incoming HTTP requests.Cevap
  3. C
    Set up a static metric threshold alert in Cloud Monitoring to page on-call engineers whenever Cloud Run CPU utilization exceeds 90% for more than 5 minutes.
  4. D
    Configure an alert to page engineers immediately whenever the error rate exceeds 0.1% in any single 1-minute window.

Cevap

The SRE team should implement multi-window, multi-burn-rate alerts based on error budget consumption speed and define the SLI as the ratio of successful HTTP requests over total valid incoming requests.
Defining the SLI as a ratio of successful user requests over total valid requests accurately measures customer experience. Applying multi-window, multi-burn-rate alerting ensures on-call engineers are paged strictly when consumption of the error budget threatens the 30-day SLO target.

Adım Adım Çözüm

1
Identify the proper formula and scope for a Service Level Indicator (SLI).
The SLI should quantify user-facing success as the count of good events divided by total valid events (e.g., non-5xx responses over total requests).
SLIs must reflect direct user experience rather than internal server resource metrics.
2
Select an effective alerting strategy tied to Service Level Objectives (SLOs) and Error Budgets.
Multi-window, multi-burn-rate alerts page engineers only when error budget is consuming at a rate that threatens to exhaust the 30-day budget.
Burn-rate alerting balances alert sensitivity and specificity, preventing alert fatigue from transient errors.

Anahtar Kavram

SRE SLO, SLI, and Error Budget Alerting Best Practices
Bu soruyu puanla

Konular

Defining and Managing SLOs, SLIs, and Error Budgets

Bu konudan daha fazla soru