Question

Difficulty: MediumAligning Technical Service Level Objectives (SLAs/SLOs/SLIs) with Business Objectives

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?

  1. 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
  2. B
    Define 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.
  3. C
    Define 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.
  4. D
    Define 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

1
Identify the primary business requirement and impact
The core business constraint is delivering payroll results before 06:00 AM local time on payday. Intermediate retries or infrastructure metrics do not impact business outcomes.
SLIs must reflect true user/business experience rather than low-level infrastructure health.
2
Differentiate SLI (measurement metric) from SLO (target goal)
The SLI is the ratio of successful batch completions before deadline over total batch executions. The SLO is the target goal percentage set over a specific compliance window.
Confusing SLI and SLO leads to misconfigured monitoring and alerting.
3
Select the option that maps technical service levels to business objectives
Measuring successful payroll completions prior to 06:00 AM directly reflects business impact.
Aligning error budget consumption with business risk ensures operations teams focus on events that harm users.

Key Concept

Aligning Technical SLIs and SLOs with Business Objectives
Rate this question