Examkin

Question

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

An e-commerce company operates an automated order fulfillment pipeline using Cloud Functions and Cloud Pub/Sub on Google Cloud. The Site Reliability Engineering (SRE) team established a target Availability Service Level Objective (SLO) of 99.9% measured over a rolling 30-day window. The team requires an operational monitoring solution that triggers urgent notifications when significant portions of the 30-day error budget are being rapidly consumed, while remaining resilient against false alarms caused by brief, transient failures. Which alerting approach should the Cloud Architect recommend?

  1. Configure a multi-window, multi-burn-rate alerting strategy in Cloud Monitoring that monitors error budget consumption rates across both short and long lookback windows.Answer
  2. B
    Configure a static metric threshold alert in Cloud Monitoring that triggers a high-severity incident whenever the request failure rate exceeds 0.1% over a 5-minute evaluation window.
  3. C
    Define the target availability goal of 99.9% as the Service Level Indicator (SLI) and create a Cloud Monitoring alert that notifies engineers whenever the SLI metric drops below 99.9%.
  4. D
    Set up an automated Cloud Monitoring policy to scale out the underlying compute resources whenever CPU utilization exceeds 80% to protect the service availability target.

Answer

The Cloud Architect should recommend configuring a multi-window, multi-burn-rate alerting strategy in Cloud Monitoring that tracks error budget consumption rates.
According to Google Cloud SRE practices, monitoring reliability against an SLO requires alerting on error budget burn rate rather than instantaneous error thresholds. A multi-window, multi-burn-rate alerting approach uses multiple time windows (such as a 1-hour short window and a 6-hour long window) and burn-rate multipliers to ensure alerts fire promptly when significant budget is at risk while suppressing alerts for brief, self-healing metric blips.

Step-by-Step Solution

1
Identify the core operational requirement.
The team needs to detect severe error budget depletion in a 99.9% 30-day SLO without generating false positives from temporary metric fluctuations.
Traditional static threshold alerts trigger on brief spikes or fail to catch slow, persistent budget leaks.
2
Evaluate SRE best practices for Google Cloud SLO alerting.
Multi-window, multi-burn-rate alerts evaluate short (e.g., 1-hour) and long (e.g., 6-hour) lookback windows simultaneously.
This dual-window evaluation ensures alerts trigger quickly when a high percentage of the error budget is consumed while resetting quickly once the issue is mitigated.
3
Select the correct architectural recommendation.
Choose the option specifying multi-window, multi-burn-rate alerts.
It aligns precisely with GCP SRE principles for managing error budgets and SLIs effectively.

Key Concept

Multi-Window, Multi-Burn-Rate SLO Alerting
Estimated Time:1m 30s
Rate this question

Topics

Defining and Managing SLOs, SLIs, and Error Budgets

More questions from this topic