Examkin

Soru

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

An international airline runs two major microservices on Google Cloud: a passenger Flight Seat Reservation API and a post-flight Partner Loyalty Points Reconciliation worker. Interruption of seat reservations directly causes severe financial loss and customer churn, whereas delays in processing loyalty points reconciliation by several hours have minimal business impact. The organization aims to align technical metrics and operational procedures with business risk. Which TWO Site Reliability Engineering (SRE) decisions correctly align technical service level objectives (SLOs/SLIs/SLAs) with business impact? (Select TWO.)

  1. Define a high-availability SLO (99.99%99.99\%) measured over a tight 11-minute SLI evaluation window for the Flight Seat Reservation API, while assigning a lower availability target (99.0%99.0\%) with a multi-hour latency SLI for the Loyalty Points Reconciliation worker.Cevap
  2. Implement error budget policy enforcement that automatically freezes new feature deployments on the Flight Seat Reservation API when its budget depletes, while permitting non-critical deployments on the Loyalty Points Reconciliation worker even under low error budgets.Cevap
  3. C
    Set the Service Level Indicator (SLI) for both services as a target percentage of 99.9%99.9\%, and utilize the Service Level Objective (SLO) to log the real-time count of successful requests divided by total requests.
  4. D
    Configure identical static threshold alerts that instantly page the on-call engineer whenever any single HTTP request fails across either the reservation API or the loyalty reconciliation worker.

Cevap

The two correct decisions are: 1) Defining a high-availability SLO (99.99%99.99\%) for the critical seat reservation API while establishing a lower availability SLO (99.0%99.0\%) for the non-critical loyalty points worker; and 2) Enforcing strict deployment freezes based on error budget depletion for the reservation API while permitting feature deployments on low-impact background services.
Aligning service levels with business impact requires setting higher SLOs and strict error budget enforcement on revenue-impacting user flows (Seat Reservation API) while setting relaxed SLOs on low-risk asynchronous background workers (Loyalty Points Reconciliation).

Adım Adım Çözüm

1
Analyze business impact differences between the microservices
The Flight Seat Reservation API is a critical revenue path requiring maximum reliability, whereas the Loyalty Points Reconciliation worker is an asynchronous background process where temporary delay incurs minimal business risk.
Technical objectives (SLOs) must be proportional to the business consequences of failure to optimize engineering spend and maintain velocity.
2
Evaluate SLO targets and SLI window alignment
Assigning a strict 99.99%99.99\% SLO to the reservation API and a 99.0%99.0\% SLO to the reconciliation worker aligns reliability targets with user impact.
Over-engineering availability for non-critical services wastes financial resources and developer productivity.
3
Establish error budget governance policies
Tie release gating to error budget exhaustion specifically on high-impact services.
Freezing deployments on revenue-critical services protects user experience, while allowing background services flexibility preserves development speed.

Anahtar Kavram

Business-Aligned Service Level Objectives and Error Budget Governance
Bu soruyu puanla

Konular

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