An enterprise B2B SaaS company runs a monthly payroll processing service on Google Cloud. Executive leadership emphasizes that missing the deadline of 06:00 AM local time on payroll day causes severe legal penalties and customer churn, whereas transient failures during earlier processing retries carry zero business penalty as long as the final output is delivered on time. How should a Cloud Architect define the Service Level Indicator (SLI) and Service Level Objective (SLO) to align technical operational monitoring with this business impact?
- Define the SLI as the percentage of monthly payroll batches completed successfully before 06:00 AM local time, and set the SLO target to align with acceptable business risk over a monthly error budget window.Answer
- BDefine the SLO as the measured completion time of each batch script in Cloud Run, and set the SLI as a fixed target percentage of 99.9% batch completion.
- CDefine the SLI as the CPU utilization of individual worker virtual machines, setting an SLO alert whenever CPU usage exceeds 85% for more than five minutes.
- DDefine the SLI as total raw HTTP 200 response codes returned by backend microservices during batch retries, and set an SLO to trigger immediate pager alerts on any transient 5xx retries.
Answer
Define the SLI as the percentage of monthly payroll batches completed successfully before 06:00 AM local time, and set the SLO target to align with acceptable business risk over a monthly error budget window.
The option selecting the payroll completion percentage before 06:00 AM correctly identifies the Service Level Indicator (SLI) as the metric measuring business success, and the Service Level Objective (SLO) as the target percentage set against acceptable business risk.
Step-by-Step Solution
Key Concept
Aligning Technical SLIs and SLOs with Business Objectives