Examkin

Question

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

A video streaming provider operates a high-throughput live event broadcasting service on Google Cloud. Executive leadership wants to ensure that technical reliability targets directly reflect subscriber retention while avoiding unnecessary operational over-engineering. The product and SRE teams are defining Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budget policies for the video chunk serving pipeline. Which TWO engineering practices effectively align technical service level metrics with business impact? (Select TWO.)

  1. Define the Service Level Indicator (SLI) as the proportion of video chunk requests served within 200 milliseconds, and calibrate the SLO target based on customer churn thresholds.Answer
  2. Establish an error budget policy that automatically freezes non-critical feature deployments when the multi-window burn rate indicates budget depletion before major live events.Answer
  3. C
    Set the monitored Service Level Indicator (SLI) value directly to the contractual Service Level Agreement (SLA) percentage to trigger operational paging when contractual limits are reached.
  4. D
    Configure static 85% CPU utilization alerting rules across backend media converter instances as the core Service Level Objective (SLO) metric for buffering performance.

Answer

To align technical metrics with business impact, the team should define the Service Level Indicator (SLI) as the proportion of video chunk requests served within 200 milliseconds calibrated against customer churn thresholds, and establish an error budget policy that freezes non-critical deployments when burn rates indicate impending budget depletion before peak events.
Defining an SLI based on user-perceived latency (video chunk requests served within 200 ms) directly measures user experience, and calibrating the corresponding SLO target against customer churn ensures business alignment. Furthermore, implementing an error budget policy based on multi-window burn rate allows product teams to protect critical business events by pausing non-essential releases when reliability is at risk.

Step-by-Step Solution

1
Identify metrics measuring user-perceived performance rather than internal infrastructure metrics.
Selected the proportion of successful low-latency requests as the SLI.
SLIs must reflect actual user experience (latency of video chunks) tied to business goals (subscriber retention).
2
Establish governance policies that connect technical reliability to release cadence.
Implemented burn-rate based error budget policies to pause deployments.
Error budget consumption controls feature release velocity to protect high-stakes business events.

Key Concept

Aligning technical service level metrics (SLIs/SLOs) and error budgets with business objectives and customer experience.
Rate this question

Topics

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