An enterprise travel platform hosted on Google Cloud experiences significant user churn during flash sales. While infrastructure monitoring reports 99.99% VM uptime, business stakeholders note that high latency during the payment validation step causes customers to abandon their bookings. The Site Reliability Engineering (SRE) team needs to realign operational monitoring to directly reflect business impact and prevent revenue loss. Which TWO actions should the SRE team take to align technical service levels with business objectives? (Select TWO)
- Define a latency Service Level Indicator (SLI) measured as the proportion of successful payment API requests completed in under at the user-facing load balancer.Cevap
- BDefine the Service Level Indicator (SLI) target as an availability goal of over a rolling 30-day window to set operational alerting thresholds.
- Establish a Service Level Objective (SLO) tied to an error budget policy that freezes non-urgent feature releases when payment latency breaches threaten checkout conversion rates.Cevap
- DConfigure static CPU utilization alerts on backend Compute Engine instances to trigger PagerDuty notifications whenever CPU usage exceeds for 5 minutes.
Cevap
The team should define a user-facing latency SLI based on successful payment calls completed within and establish an SLO tied to an error budget policy that governs feature deployment velocity based on checkout impact.
Defining a latency SLI at the user-facing load balancer accurately captures customer experience for payment validation. Tying that SLI to an SLO with an error budget policy ensures that when user experience degrades, engineering effort is redirected from new features to service reliability, directly mitigating business revenue loss.
Adım Adım Çözüm
Anahtar Kavram
Aligning user-centric SLIs and error-budget-driven SLOs with business impact