Examkin

Question

Difficulty: EasyDefining and Managing SLOs, SLIs, and Error Budgets

An SRE team is managing a high-throughput payment microservice hosted on Google Cloud. They want to ensure they receive operational alerts before their monthly service availability target is breached. Which alerting strategy should the team implement?

  1. Configure alerts based on multi-window error budget burn rates.Answer
  2. B
    Configure static metric threshold alerts on backend compute CPU and memory utilization.
  3. C
    Configure immediate alert notifications whenever a single SLI measurement registers a failed request.
  4. D
    Configure load balancer health checks to mark backends unhealthy whenever database query latency increases.

Answer

Configure alerts based on multi-window error budget burn rates.
Burn rate alerting measures the speed at which a service consumes its error budget. Using multi-window burn rate alerts ensures that severe incidents consuming significant budget trigger immediate alerts, while minor transient errors do not create unnecessary alert noise.

Step-by-Step Solution

1
Identify the primary operational reliability goal.
The goal is to alert on rapid consumption of the error budget before violating the Service Level Objective (SLO).
SLO management relies on tracking error budget consumption rather than raw metric blips or resource usage.
2
Evaluate alerting approaches against SRE best practices.
Multi-window burn rate alerts calculate consumption velocity over both short and long time windows.
Burn rate alerting ensures severe incidents trigger urgent notifications while suppressing transient, non-critical noise.

Key Concept

Error Budget Burn Rate Alerting
Estimated Time:1m 0s
Rate this question

Topics

Defining and Managing SLOs, SLIs, and Error Budgets

More questions from this topic