Examkin

Soru

Zorluk: OrtaAligning Technical Service Level Objectives (SLAs/SLOs/SLIs) with Business Objectives

A digital logistics enterprise operates an automated order-routing engine hosted on Google Cloud. Contractual agreements with major enterprise clients define a Service Level Agreement (SLA) requiring 99.9%99.9\% of order-routing requests to be processed in under 200 ms200\text{ ms} each month, with financial penalties enforced for non-compliance. The Site Reliability Engineering (SRE) team must align technical metrics with business goals without over-engineering operational overhead. Which strategy correctly establishes the Service Level Indicator (SLI) and Service Level Objective (SLO) to protect business interests?

  1. Define the SLI as the proportion of valid requests completed within 150 ms150\text{ ms}, and set an internal SLO target of 99.95%99.95\%, creating a performance buffer before breaching the external SLA.Cevap
  2. B
    Define the SLO as the metric ratio of requests completed under 200 ms200\text{ ms} captured in Cloud Monitoring, and use the business SLA target of 99.9%99.9\% as the SLI measurement.
  3. C
    Configure static Cloud Monitoring alert thresholds that trigger immediate on-call pages whenever request latency exceeds 200 ms200\text{ ms} over a 5-minute window, bypassing internal SLO error budget tracking.
  4. D
    Deploy a multi-region active-active architecture targeting 99.999%99.999\% continuous availability to guarantee that latency thresholds are never exceeded under any failure condition.

Cevap

The correct strategy defines the SLI as the percentage of valid requests completed within a tighter response time (150 ms150\text{ ms}) and sets an internal SLO (99.95%99.95\%) tighter than the external SLA (99.9%99.9\% at 200 ms200\text{ ms}) to establish a protective error budget buffer.
Defining the SLI as a specific measurable request metric (≤150 ms\le 150\text{ ms}) and setting an internal SLO (99.95%99.95\%) tighter than the business SLA (99.9%99.9\% at 200 ms200\text{ ms}) aligns engineering objectives with business risk. The margin creates an actionable error budget buffer, enabling engineering teams to detect and fix performance degradation before external SLA breaches and financial penalties occur.

Adım Adım Çözüm

1
Differentiate SLI, SLO, and SLA roles in SRE practice.
SLI is the metric measuring actual performance, SLO is the internal target percentage for that metric, and SLA is the external business contract with financial penalties.
Clear layer separation ensures technical metrics directly track operational risks against business impact.
2
Establish protective margin between internal goals and external commitments.
Setting an internal SLO target of 99.95%99.95\% at 150 ms150\text{ ms} provides proactive alerting and error budget management prior to reaching the contractual SLA boundary of 99.9%99.9\% at 200 ms200\text{ ms}.
Allows SRE teams to mitigate issues before business penalties are triggered.

Anahtar Kavram

Aligning Technical SLOs/SLIs with Business SLAs
Bu soruyu puanla

Konular

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