Examkin

Soru

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

A financial technology company operates a real-time payment authorization API. The business team identifies that authorization latencies exceeding 200 ms200\text{ ms} lead to increased checkout abandonment and direct revenue loss. The company has a contractual SLA with merchants guaranteeing 99.5%99.5\% monthly service availability. To align operational engineering metrics with these business goals while enabling safe release velocity, how should the Cloud Architect define the SLI and SLO strategy?

  1. Define the SLI as the proportion of valid requests served in less than 200 ms200\text{ ms}, set an internal SLO target of 99.9%99.9\% for this SLI, and use the error budget to manage deployment risk.Cevap
  2. B
    Define the SLO as the actual measured ratio of fast requests, set the SLI target percentage to 99.9%99.9\%, and configure deployment gates to block releases whenever the SLI drops below the external 99.5%99.5\% SLA limit.
  3. C
    Define the SLI strictly as the ratio of HTTP 200 responses to total requests, set the SLO to 99.5%99.5\% to match the merchant SLA, and issue immediate page alerts whenever average latency spikes over 200 ms200\text{ ms} for 5 minutes.
  4. D
    Define the SLI by using backend database transaction query times from Cloud Load Balancer health checks, and set a target SLO of 99.99%99.99\% to guarantee zero transaction latency issues.

Cevap

The correct strategy is to define the SLI as the proportion of valid requests served under 200 ms200\text{ ms}, establish an internal SLO target of 99.9%99.9\%, and utilize the remaining error budget to govern deployment velocity.
The correct option correctly aligns the technical metric (SLI measuring requests under 200 ms200\text{ ms}) with the specific business risk (cart abandonment). It sets an internal SLO (99.9%99.9\%) that is stricter than the external contractual SLA (99.5%99.5\%), giving the team a buffer to detect and resolve incidents before breaching SLA commitments. Furthermore, it uses the error budget to balance operational stability with feature deployments.

Adım Adım Çözüm

1
Identify the critical user-centric metric tied to business impact.
Latency exceeding 200 ms200\text{ ms} impacts revenue; therefore, the Service Level Indicator (SLI) must measure the proportion of requests completing within 200 ms200\text{ ms}.
SLIs must reflect actual user experience directly linked to business outcomes.
2
Establish the Service Level Objective (SLO) target above the Service Level Agreement (SLA).
An internal SLO of 99.9%99.9\% provides a 0.4%0.4\% buffer above the external 99.5%99.5\% SLA.
Setting internal SLOs tighter than external SLAs ensures teams receive early warnings and can remediate issues before violating commercial contracts.
3
Implement error budget governance for feature releases.
The difference between 100%100\% and the 99.9%99.9\% SLO target establishes an error budget (0.1%0.1\%) that dictates when releases can occur.
Error budgets align product development and operations by allowing rapid innovation when budget is available and prioritizing stability when budget is exhausted.

Anahtar Kavram

Aligning user-centric SLIs/SLOs with business revenue impact and establishing error budget buffers above SLAs.
Bu soruyu puanla

Konular

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