Examkin

Question

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

An enterprise financial audit platform processes transaction verification requests using a GraphQL API on Google Kubernetes Engine (GKE). The Site Reliability Engineering (SRE) team needs to establish an alerting strategy to preserve the service's availability Service Level Objective (SLO) of 99.9% over a 30-day rolling window. The team wants to ensure they receive immediate notifications for rapid error budget depletion while avoiding alert fatigue from minor, transient error spikes. Which alerting configuration should the SRE team implement?

  1. Implement multi-window, multi-burn-rate alerting that measures short-term and long-term error budget consumption rates.Answer
  2. B
    Configure a static threshold alert on Cloud Monitoring whenever HTTP 5xx error rates exceed 0.1% over a 5-minute window.
  3. C
    Set up an alert on GKE node CPU utilization when aggregate node pool usage exceeds 85% for more than 10 minutes.
  4. D
    Define the 99.9% successful response target as the Service Level Indicator (SLI) and alert when total HTTP 5xx errors exceed 100 in an hour.

Answer

The SRE team should implement multi-window, multi-burn-rate alerting that measures short-term and long-term error budget consumption rates.
Implementing multi-window, multi-burn-rate alerting is the recommended GCP SRE best practice for managing error budgets. By monitoring multiple time windows simultaneously (such as short windows for fast burn and long windows for slow burn), SRE teams can quickly catch catastrophic failures before the error budget is exhausted while avoiding noisy alerts from brief, transient error spikes.

Step-by-Step Solution

1
Analyze the service availability SLO requirement.
The target availability is 99.9% over a 30-day rolling window, meaning the allowable error budget is 0.1% of total requests.
The alerting strategy must protect this specific budget without causing false positives.
2
Evaluate alerting approaches against SRE best practices for error budget management.
Static threshold alerts cause alert fatigue or miss slow burns, whereas burn-rate alerts measure how quickly the budget is consumed.
Burn rates standardize alerting based on the severity of the threat to the SLO.
3
Select multi-window, multi-burn-rate configuration.
Using multiple time windows (short and long) combined with burn-rate thresholds allows precise detection of both rapid budget exhaustion and sustained slow leaks.
Multi-window multi-burn-rate alerting is the Google SRE benchmark standard for SLO reliability monitoring.

Key Concept

Multi-window, multi-burn-rate alerting for error budgets
Estimated Time:1m 30s
Rate this question

Topics

Defining and Managing SLOs, SLIs, and Error Budgets

More questions from this topic