Examkin

Question

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

A SaaS logistics company operating on Google Cloud provides two core features: a real-time fleet GPS tracking API and an end-of-month regulatory compliance report generator. The business incurs financial penalties if the real-time tracking API availability drops below 99.9%99.9\%, whereas compliance report generation allows a 24-hour delivery window without penalty. Currently, the engineering team applies a single composite availability goal of 99.99%99.99\% across the entire platform, causing frequent false-alarm pages and unnecessary over-engineering costs. Which approach should the Cloud Architect recommend to properly align technical SLOs and SLIs with business impact?

  1. Decouple the platform into distinct services, defining a target availability SLO of 99.9%99.9\% based on successful HTTP request ratio SLIs for real-time tracking, and a completion-time SLO based on a 24-hour latency SLI for batch report generation.Answer
  2. B
    Set the measured SLI target to 99.99%99.99\% availability for both services, and trigger high-priority alerts whenever the monthly compliance report pipeline execution duration varies by more than 1%1\%.
  3. C
    Increase the unified composite availability SLO to 99.999%99.999\% for all system components to eliminate any possibility of contractual SLA breach.
  4. D
    Replace service-level availability metrics with a unified aggregate CPU utilization threshold alert set at 80%80\% across all compute instances.

Answer

Decouple the platform into distinct services, defining a target availability SLO of 99.9% based on successful HTTP request ratio SLIs for real-time tracking, and a completion-time SLO based on a 24-hour latency SLI for batch report generation.
The correct strategy decouples heterogeneous workloads (real-time streaming vs. asynchronous batch processing) so their technical SLOs reflect their respective business requirements. Real-time GPS tracking requires high availability to avoid financial penalties, whereas compliance reporting requires a throughput or latency-based metric within a 24-hour window.

Step-by-Step Solution

1
Analyze business impact and requirements for each workload
Real-time tracking requires high availability (99.9%99.9\%) due to financial SLA penalties. Compliance reporting is batch-oriented with a 24-hour tolerance window.
SLOs must directly reflect user expectations and contractual business consequences rather than arbitrary technical defaults.
2
Define appropriate Service Level Indicators (SLIs) for each service
Real-time tracking SLI = (Successful tracking requests) / (Total tracking requests). Compliance report SLI = (Reports completed within 24 hours) / (Total generated reports).
SLIs quantify actual performance in terms that map directly to functional requirements (availability vs batch completion latency).
3
Set Service Level Objectives (SLOs) and manage error budgets independently
Real-time tracking SLO is set to 99.9%99.9\% monthly availability. Reporting SLO is set to 99%99\% of jobs completed within 24 hours.
Separating SLOs prevents non-critical batch jobs from depleting the error budget of critical real-time features.

Key Concept

Aligning SLAs, SLOs, and SLIs with Business Impact
Rate this question

Topics

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