Examkin

Soru

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

An energy utility company operates two primary workloads on Google Cloud: a real-time Smart Grid Telemetry Ingestion microservice and an asynchronous Monthly Customer Billing Report Generator. Failure of real-time telemetry ingestion immediately threatens power grid stability, whereas delayed billing reports can be re-processed asynchronously within a 24-hour window without business loss. Which strategy correctly aligns technical operational metrics with business impact for these workloads?

  1. Define a stringent availability SLO (such as 99.99%) evaluated over short windows with burn-rate alerts for grid telemetry, and a lower SLO (such as 99.0%) based on job completion freshness over a monthly window for billing reports.Cevap
  2. B
    Enforce a uniform 99.99% availability SLO across both workloads because they run on the same shared Google Kubernetes Engine cluster.
  3. C
    Designate the 99.99% availability target itself as the SLI for real-time telemetry and configure static alerts whenever error rates briefly spike.
  4. D
    Establish a 99.999% SLA to end-user customers for billing report generation to ensure high customer satisfaction before defining internal SLOs and SLIs.

Cevap

Define a stringent availability SLO (such as 99.99%) evaluated over short windows with burn-rate alerts for grid telemetry, and a lower SLO (such as 99.0%) based on job completion freshness over a monthly window for billing reports.
The correct strategy differentiates the Service Level Objectives based on business impact: high-frequency real-time grid telemetry requires tight availability goals and rapid error-budget alert monitoring, while batch report generation only requires periodic freshness targets within a 24-hour window.

Adım Adım Çözüm

1
Analyze business impact for each service.
Grid telemetry has critical, immediate business impact (grid stability), whereas billing reports are asynchronous with a 24-hour tolerance.
SLOs and error budgets must directly map to user tolerance and business impact of downtime.
2
Select appropriate SLIs and SLO targets.
Assign high availability (e.g., 99.99%) with real-time latency/success SLIs for telemetry, and freshness/completion time SLOs (e.g., 99.0%) for batch billing.
Differentiating targets avoids over-engineering non-critical components and protects critical systems.
3
Differentiate SLI measurements from SLO target goals.
Ensure SLIs measure actual operational events (successful telemetry requests / total requests) while SLOs set the target threshold over a specific time window.
Confusing SLIs with SLOs undermines error budget tracking and operational alert design.

Anahtar Kavram

Aligning SLAs, SLOs, and SLIs with Business Impact
Bu soruyu puanla

Konular

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