Examkin

Soru

Zorluk: ZorAligning Technical Service Level Objectives (SLAs/SLOs/SLIs) with Business Objectives

A pharmaceutical enterprise hosts two core workloads on Google Cloud: a synchronous Clinical Trial Adverse Event Notification Service that directly impacts regulatory compliance and patient safety, and an asynchronous Batch Genomic Sequence Alignment Pipeline used for long-term discovery research. Executive leadership demands a reliability engineering framework that aligns Service Level Objectives (SLOs) and error budgets with real business impact. How should a Cloud Architect structure the Service Level Indicators (SLIs) and SLOs for these distinct workloads?

  1. Define an availability and latency SLI measured at the application load balancer endpoint for the Adverse Event Notification Service with a stringent 99.95% SLO tied to an error budget policy that freezes non-critical releases upon budget exhaustion; define a pipeline completion time SLI over a multi-hour window for the Genomic Pipeline with a relaxed SLO to preserve developer velocity.Cevap
  2. B
    Set the Adverse Event Notification Service SLO as the real-time measured uptime percentage metric from Cloud Monitoring, while establishing the SLI as the target goal of 99.95% availability calculated over a 30-day rolling window.
  3. C
    Enforce a uniform 99.99% availability SLO across both the Adverse Event Notification Service and the Genomic Sequence Alignment Pipeline to standardize operational alerting and simplify infrastructure management.
  4. D
    Monitor cluster CPU and memory utilization on Compute Engine instances as the primary SLI for the Adverse Event Notification Service, setting an SLO requiring average resource usage to stay below 75%.

Cevap

Define an availability and latency SLI measured at the application load balancer endpoint for the Adverse Event Notification Service with a stringent 99.95% SLO tied to an error budget policy that freezes non-critical releases upon budget exhaustion; define a pipeline completion time SLI over a multi-hour window for the Genomic Pipeline with a relaxed SLO to preserve developer velocity.
Aligning service levels with business impact requires tailoring SLIs and SLOs to workload characteristics. High-priority synchronous APIs that directly affect regulatory compliance need user-facing endpoint SLIs (latency/error rates), strict SLO targets, and enforced error budget policies (such as deployment freezes). Conversely, asynchronous batch workloads should be measured by completion timeliness with lower SLO targets, avoiding unnecessary operational overhead.

Adım Adım Çözüm

1
Analyze business impact and workload characteristics
The Adverse Event Notification Service is synchronous and safety-critical, requiring high availability. The Genomic Pipeline is batch-oriented and latency-tolerant.
SLOs must reflect user-perceived reliability and business consequences of downtime.
2
Differentiate metrics (SLIs) from targets (SLOs)
SLIs measure specific user-facing capabilities (e.g., successful HTTP responses or batch execution duration). SLOs represent the target thresholds for those SLIs.
Correct metrics ensure operational monitoring aligns with customer experience rather than internal machine capacity.
3
Establish error budget policies aligned with operational risk
Exhausting the error budget on the critical notification service restricts deployment risk via release freezes, while the batch pipeline maintains lower target goals to maximize feature delivery speed.
Error budgets serve as the decision tool balancing reliability against feature velocity.

Anahtar Kavram

Business-Aligned SLO/SLI and Error Budget Strategy
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

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