Examkin

Question

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

An enterprise financial technology platform processes high-throughput asynchronous ledger events via a pipeline powered by Google Cloud Pub/Sub, Cloud Run microservices, and Cloud Spanner. The Site Reliability Engineering (SRE) team defines a Service Level Objective (SLO) requiring 99.9%99.9\% of event processing requests to succeed over a 30-day rolling window. The team needs to implement an alerting strategy that reliably detects severe outages exhausting the monthly error budget rapidly while suppressing false-positive alerts caused by brief, self-correcting transient spikes. Which alerting policy should the Cloud Architect recommend?

  1. A
    Configure static threshold alerts in Cloud Monitoring that fire whenever the 5-minute average HTTP 5xx error rate exceeds 0.1%0.1\%.
  2. Implement multi-window, multi-burn-rate alerts based on error budget consumption, triggering critical notifications when 2%2\% of the 30-day budget is burned within a 1-hour window.Answer
  3. C
    Define the Service Level Indicator (SLI) directly as the fixed target percentage of 99.9%99.9\%, and set up an alert that triggers immediately whenever instantaneous availability falls below 99.9%99.9\%.
  4. D
    Configure alerts based on CPU and memory utilization thresholds of the processing compute infrastructure exceeding 85%85\% for more than 10 minutes.

Answer

Implement multi-window, multi-burn-rate alerts based on error budget consumption, triggering critical notifications when 2%2\% of the 30-day budget is burned within a 1-hour window.
According to Google SRE principles and GCP Cloud Monitoring standards, multi-window multi-burn-rate alerting is the recommended pattern for SLO management. A 1-hour window detecting 2%2\% budget consumption represents a 14.4×14.4\times burn rate. Using multiple windows (e.g., 1-hour short window and 6-hour long window) ensures alerts trigger only when significant budget is actively being spent, providing high precision and recall.

Step-by-Step Solution

1
Analyze the operational objective
The system requires an alerting strategy aligned with SRE best practices to protect a 99.9%99.9\% 30-day availability SLO without generating false positives.
Alerting directly on error budget consumption rate prevents both alert fatigue and delayed incident response.
2
Evaluate alerting mechanism choices against SRE error budget principles
Multi-window, multi-burn-rate alerts measure consumption rate (e.g., 14.4×14.4\times burn rate over 1 hour consuming 2%2\% of budget) across short and long lookback windows.
This guarantees that high burn rates trigger immediate escalations while smaller, self-healing events reset without paging on-call engineers.
3
Eliminate flawed alerting practices
Static metric thresholds, resource saturation metrics (CPU/RAM), and instantaneous target checks fail to measure cumulative budget consumption accurately.
Resource metrics monitor capacity rather than reliability, and static thresholds do not adapt to multi-day SLO budget windows.

Key Concept

Error Budget Burn-Rate Alerting
Rate this question

Topics

Defining and Managing SLOs, SLIs, and Error Budgets

More questions from this topic