Examkin

Soru

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

An enterprise IoT platform ingests telemetry from connected vehicles and serves real-time data to fleet analytics dashboards via a Cloud Load Balancer and backend service. The Site Reliability Engineering (SRE) team defines a Service Level Objective (SLO) requiring 99.9% successful HTTP responses over a rolling 30-day window. The SRE team needs an operational alerting mechanism that detects active, severe budget consumption promptly while eliminating alert fatigue from brief transient errors or slow, non-critical budget consumption. Which alerting strategy should the Cloud Architect recommend?

  1. Configure a multi-window, multi-burn-rate alert policy in Cloud Monitoring that evaluates error budget consumption across both short-term and long-term lookback windows simultaneously.Cevap
  2. B
    Set up a static threshold alert policy in Cloud Monitoring that triggers an immediate page whenever the error rate exceeds 0.1% within any 5-minute window.
  3. C
    Create an automated metric alert based on CPU and memory utilization thresholds of the backend instances supporting the analytics service.
  4. D
    Establish a single static alert that notifies the team when total monthly error budget consumption reaches a fixed 50% threshold.

Cevap

Configure a multi-window, multi-burn-rate alert policy in Cloud Monitoring that evaluates error budget consumption across both short-term and long-term lookback windows simultaneously.
The correct recommendation is to implement a multi-window, multi-burn-rate alerting policy. This approach checks both short-term lookback windows (to quickly detect high-severity, rapid budget depletion) and longer lookback windows (to confirm the burn is sustained and avoid alerting on brief self-resolving spikes). This matches Google Cloud SRE standards for reliable SLO alerting without triggering alert fatigue.

Adım Adım Çözüm

1
Analyze the reliability requirement and SLO parameters.
The target SLO is 99.9% availability over a 30-day rolling window, allowing a total 0.1% error budget.
Alerting logic must align directly with error budget consumption velocity rather than raw infrastructure metrics.
2
Evaluate alerting strategies against SRE best practices to prevent alert fatigue while maintaining quick response times.
Static single-window threshold alerts produce false positives on transient spikes and delay notifications during rapid outages.
Google SRE best practices recommend multi-window, multi-burn-rate alerts to balance alert speed and precision.
3
Select the optimal alerting policy mechanism in GCP Cloud Monitoring.
Combining short lookback windows (for high burn rate detection) and long lookback windows (to ensure sustained budget consumption) ensures alerts fire only when the 30-day budget is genuinely threatened.
This satisfies the requirement to notify promptly during critical events while avoiding alert fatigue.

Anahtar Kavram

Multi-window, multi-burn-rate alerting for SRE Error Budget management in Cloud Monitoring
Bu soruyu puanla

Konular

Defining and Managing SLOs, SLIs, and Error Budgets

Bu konudan daha fazla soru