Examkin

Soru

Zorluk: Çok zorAligning Technical Service Level Objectives (SLAs/SLOs/SLIs) with Business Objectives

A global logistics provider operates a real-time event-driven platform on Google Cloud that processes both high-priority shipment rerouting events and low-priority operational telemetry. The business contract specifies a steep financial penalty if shipment rerouting requests take longer than 55 seconds to complete, whereas operational telemetry can tolerate processing delays of up to 1010 minutes without incurring any business or financial impact. The engineering leadership team wants to establish a service level monitoring strategy that tightly couples operational alerting with actual business financial risk while avoiding unnecessary infrastructure over-provisioning and alert fatigue. Which strategy correctly aligns technical SLI measurement and SLO alerting with these business goals?

  1. Define the SLI specifically as the ratio of shipment rerouting events completed within 5 seconds to total shipment rerouting events measured at the ingress gateway. Set a monthly SLO of 99.9% for this specific pipeline, and configure multi-window, multi-burn-rate alerts based on error budget consumption speed.Cevap
  2. B
    Define the SLO as the actual measured latency percentage of all combined system traffic (rerouting and telemetry events) meeting the 5-second target, and configure alerts to trigger whenever the rolling 5-minute average processing time exceeds 5 seconds.
  3. C
    Define the SLI as worker pool CPU and memory utilization across all event-processing clusters, and configure high-priority paging alerts whenever any worker node exceeds 85% CPU utilization for more than 1 minute.
  4. D
    Establish a uniform 99.999% SLA across both shipment rerouting and operational telemetry pipelines by deploying active-active multi-region infrastructure for all event ingestion layers.

Cevap

The correct strategy is to define the SLI specifically as the ratio of high-priority shipment rerouting events completed within 5 seconds to total rerouting events at the ingress gateway, establish a 99.9% monthly SLO for that target, and deploy multi-window multi-burn-rate alerts based on error budget depletion rates.
The solution correctly separates business-critical transactions (rerouting) from low-impact background data (telemetry). Defining the SLI as a ratio of good requests to total requests at the entry point captures the actual user/business experience. Utilizing multi-window, multi-burn-rate alerting on the error budget provides timely notifications when financial penalties are threatened, while preventing false alarms caused by transient spikes.

Adım Adım Çözüm

1
Isolate high-impact business operations from non-critical background processes.
Identified that shipment rerouting events carry financial penalties when delayed past 5 seconds, while operational telemetry does not.
SLIs and SLOs must reflect actual business risk to prevent over-spending and false operational alarms.
2
Construct a valid Service Level Indicator (SLI).
Formulated the SLI as Successful events processed ≤5sTotal valid events\frac{\text{Successful events processed } \le 5\text{s}}{\text{Total valid events}} for critical rerouting events.
An SLI is a quantifiable ratio of good events over total events measured at a valid boundary (ingress gateway).
3
Establish an Error Budget Burn-Rate Alerting strategy.
Applied multi-window multi-burn-rate alerting to track consumption of the 99.9% SLO error budget.
Burn-rate alerting ensures operations teams are paged only when error budget consumption rates threaten a business SLO breach.

Anahtar Kavram

Aligning SLIs/SLOs with Business Impact and Error Budget Alerting
Bu soruyu puanla

Konular

Aligning Technical Service Level Objectives (SLAs/SLOs/SLIs) with Business Objectives