Examkin

Soru

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

An online retail enterprise operating on Google Cloud experiences direct financial losses whenever customer order placement fails or suffers severe latency during peak promotional periods. The business leadership requires that 99.5% of critical customer transactions succeed within acceptable response times, while secondary background operations like inventory synchronization can tolerate lower availability without impacting user revenue. The Site Reliability Engineering (SRE) team must align technical monitoring and SLO management with these specific business goals. Which TWO architectural and operational strategies should the team implement? (Select TWO.)

  1. Define distinct Service Level Indicators (SLIs) specifically measuring successful user transaction requests separately from non-critical background data sync operations.Cevap
  2. Configure error budget burn-rate alerts evaluated across multiple time windows to trigger operational responses before the business-critical SLO is breached.Cevap
  3. C
    Define the primary checkout SLI as backend Compute Engine CPU utilization and establish an SLO targeting average utilization below 75%.
  4. D
    Establish a unified global availability SLO target of 99.99% across all service endpoints and trigger immediate high-priority pages on any individual request failure.

Cevap

The team should define distinct SLIs for high-impact user transaction requests versus non-critical background operations, and configure multi-window error budget burn-rate alerts for the critical checkout service.
Correct alignment of SLAs, SLOs, and SLIs requires measuring metrics that directly correlate with user experience and business outcomes (such as checkout transaction success rates) rather than system-level metrics. Furthermore, managing availability through error budget burn-rate alerting ensures that engineering efforts focus on protecting business objectives without inducing operational noise.

Adım Adım Çözüm

1
Categorize service endpoints based on business revenue impact
Order placement is identified as critical (revenue-impacting) while inventory sync is non-critical.
Technical service objectives must directly reflect distinct business criticality levels.
2
Establish user-centric SLIs measuring successful request rates for critical flows
SLIs track successful HTTP transactions over total requests for the order endpoint.
SLIs must evaluate actual user experience rather than raw infrastructure metrics like CPU utilization.
3
Implement error budget burn-rate alerting
Alerts trigger dynamically when error budget consumption rate threatens the 99.5% SLO target.
Burn-rate alerting prevents alert fatigue while ensuring timely operational intervention during severe incidents.

Anahtar Kavram

Aligning user-centric SLIs and multi-window burn-rate SLO alerting with business impact
Bu soruyu puanla

Konular

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