Examkin

Question

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

A financial enterprise processes high-volume trade settlement requests using Google Cloud Pub/Sub, Dataflow, and Cloud Spanner. The business operations team determines that any settlement request taking longer than 500 ms500\text{ ms} to complete creates regulatory non-compliance exposure, but the business can tolerate up to 0.05%0.05\% of monthly transactions exceeding this threshold before financial penalties occur. As a Cloud Architect aligning technical operations with business risk, how should you structure the service level metrics for this pipeline?

  1. Define the SLI as the proportion of settlement requests completed in under 500 ms500\text{ ms} divided by total valid requests, and set the SLO target at 99.95%99.95\% over a rolling 30-day window.Answer
  2. B
    Define the SLI as 99.95%99.95\% of settlement requests completed within 500 ms500\text{ ms}, and set the SLO as the real-time measured latency metric captured by Cloud Monitoring.
  3. C
    Define the SLI as average CPU utilization of Dataflow workers, and set the SLO target to maintain worker CPU utilization below 80%80\% to prevent processing backlogged messages.
  4. D
    Define the SLI as the percentage of HTTP 200 responses from the ingress load balancer, and set the SLO target to 99.99%99.99\% to guarantee baseline infrastructure availability.

Answer

The Service Level Indicator (SLI) should be defined as the ratio of settlement requests completed within 500 ms500\text{ ms} over total valid settlement requests, with the Service Level Objective (SLO) set at 99.95%99.95\% over a rolling 30-day window.
The correct approach defines a Service Level Indicator (SLI) as the empirical ratio of successful latency events (≤500 ms\le 500\text{ ms}) over total requests, and pairs it with a Service Level Objective (SLO) of 99.95%99.95\% over 30 days. This directly reflects the business risk tolerance (0.05%0.05\% maximum non-compliant trades) while using standard SRE metric practices.

Step-by-Step Solution

1
Identify the core business requirement and risk threshold.
Processing latency >500 ms> 500\text{ ms} causes compliance issues; allowable failure rate is 0.05%0.05\% per month (100%−0.05%=99.95%100\% - 0.05\% = 99.95\% target).
SLOs must directly align with business tolerance limits to protect revenue and regulatory status.
2
Formulate the Service Level Indicator (SLI).
SLI=Good EventsTotal Events=Settlement requests completed in ≤500 msTotal valid settlement requests\text{SLI} = \frac{\text{Good Events}}{\text{Total Events}} = \frac{\text{Settlement requests completed in } \le 500\text{ ms}}{\text{Total valid settlement requests}}.
An SLI is a quantified, empirical ratio measuring actual service performance against a specific user-centric or business metric.
3
Set the Service Level Objective (SLO) target over a compliance window.
Set the SLO at ≥99.95%\ge 99.95\% evaluated over a rolling 30-day period.
The SLO establishes the target threshold for the SLI that technical teams maintain to remain within the business risk envelope.

Key Concept

Aligning technical SLIs and SLOs with business impact
Rate this question

Topics

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