# Service Level Objectives

Service level objectives are measurable targets for the reliability and performance of a service over a defined evaluation period.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/service-level-objectives

> A service level objective (SLO) translates business expectations into a measurable target, such as successful request percentage or response time. SLOs guide architecture, monitoring, incident response, and spending by defining how much reliability a workload actually needs.

Practice exams covering Service Level Objectives: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Service Level Objectives

Effective SLOs combine business-aligned targets, precise measurements, error budgets, and tested resilience choices to manage service quality at an appropriate cost.

1. **Business-driven service targets**: Choose availability, latency, correctness, or freshness targets according to the impact of degraded service. Define different objectives for critical production journeys, internal tools, and non-production workloads when their business requirements differ.
2. **Precisely defined indicators**: Specify the SLI, eligible population, success threshold, and evaluation window so different teams calculate the same result. Prefer measurements that represent user outcomes rather than relying solely on infrastructure health.
3. **Clear separation of SLI, SLO, and SLA**: An SLI measures service behavior, an SLO sets its target, and an SLA establishes agreed commitments and consequences. A cloud provider's SLA does not guarantee that an application built on that provider meets its own objective.
4. **Error budgets and burn rates**: Convert the objective into an allowed amount of failure and track how quickly it is consumed. Use burn-rate alerts and an agreed error-budget policy to balance delivery speed with reliability work.
5. **Cost-proportionate resilience**: Select redundancy, capacity, and failover mechanisms that meet the required target without unnecessary complexity. Higher targets can justify multi-zone or multi-Region designs, but only when the business benefit outweighs their costs and operational risks.
6. **End-to-end validation**: Include dependencies, partial failures, and failover behavior when evaluating whether the service can meet its objective. Test recovery procedures and measure customer-visible behavior rather than assuming redundant resources guarantee availability.

## Cloud services for Service Level Objectives

Amazon CloudWatch measures service behavior and tracks objectives, while Elastic Load Balancing and Amazon EC2 Auto Scaling help maintain healthy application capacity across Availability Zones. Amazon RDS Multi-AZ deployments address database availability, and Amazon Route 53 can support endpoint failover where the architecture requires it. These mechanisms must be configured and tested together: database reconnection, scaling delays, health-check thresholds, and DNS caching all affect customer-visible outcomes. Use end-to-end measurements to confirm that the combined design meets its SLO, and add resilience only where the required service level justifies the cost and operational complexity.

- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Collect application metrics, logs, and synthetic transaction results to measure service behavior. CloudWatch Application Signals supports defining and monitoring SLOs, while alarms help teams detect failures and respond to error-budget consumption.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: Maintain desired instance capacity, replace unhealthy instances, and scale capacity with demand. Appropriate health checks, scaling policies, and multi-zone placement help protect availability and latency objectives during failures or traffic increases.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Multi-AZ database deployments provide standby or replica capacity and managed failover, depending on the deployment type. Evaluate failover interruption, connection recovery, and database capacity against application SLOs rather than assuming managed failover eliminates downtime.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Health checks and DNS failover routing can direct clients toward healthy application endpoints. Account for health-check detection time, DNS caching, and application readiness when estimating whether failover can meet the service objective.

## Service Level Objectives exam questions

Real practice exam questions on Service Level Objectives, with the correct answer and its explanation.

### Question 1 (SAA-C03)

**Question:**

A company is designing the compute tier for an internal reporting application on Amazon EC2. The business requires 99.9% time-based availability during each 30-day month, measured continuously from the user's perspective. Planned maintenance counts as downtime. There is no separate requirement for uninterrupted service during an Availability Zone failure.

The application stores its state outside the instances. Failure testing and operational modeling produce the monthly downtime estimates in the proposed designs below, including maintenance and recovery. The company has approved these estimates for architecture planning. All designs use the same instance type and maintain their stated instance count continuously. Costs outside EC2 compute are identical.

Which design meets the availability objective at the LOWEST EC2 compute cost?

**Correct answer:** Run one instance in an EC2 Auto Scaling group with desired capacity 1, automatic replacement of unhealthy instances, and automated maintenance. Estimated total downtime is 35 minutes per month.

**Explanation:** A 30-day month contains 43,200 minutes. An availability objective of 99.9% permits 43.2 minutes of downtime. The estimated 35 minutes stays within this budget while requiring only one continuously running instance. Additional redundancy is not required by the stated business requirements.

### Question 2 (SAP-C03)

**Question:**

A SaaS company uses Amazon CloudWatch Application Signals to monitor a public API. Its availability SLO is 99.9% over a rolling 30-day interval. As an additional operational guardrail, the company requires a CloudWatch alarm when availability is below 99.9% for one completed 5-minute period. The guardrail must use the same response classification and request weighting as the Application Signals dashboard availability metric.

For a single completed 5-minute validation period, the service-level metrics record exactly 100,000 latency samples: 79,910 HTTP 2XX responses, 20,000 HTTP 4XX responses, and 90 HTTP 5XX responses. For that same period and metric scope, the Fault metric records 90 faults, and the Error metric records 20,000 client errors. There are no missing observations or other response types. The alarm evaluates only this completed period, with one evaluation period and one datapoint required to alarm.

Which calculation and evaluation result meet the requirements?

**Correct answer:** Use 100 × (1 − Sum(Fault) / SampleCount(Latency)) over the 5-minute period. The calculated availability is 99.91%, which does not breach the alarm threshold.

**Explanation:** Application Signals calculates availability as (1 − Faults / Total) × 100. Total comes from SampleCount(Latency) and includes all responses, including HTTP 4XX responses. Therefore, availability for this completed period is (1 − 90 / 100,000) × 100 = 99.91%. This exceeds 99.9%, so the evaluated datapoint does not trigger the guardrail alarm.

### Question 3 (DOP-C02)

**Question:**

A company operates an asynchronous data-export service on AWS. The API normally returns HTTP 202 and queues an export job. Workers later generate a file that customers download. During an incident, the API continued returning HTTP 202, but many export jobs stalled. The existing API availability dashboard showed no degradation.

The business requires at least 99.9% of valid, authenticated logical export submissions to produce a correct, downloadable file within 5 minutes, evaluated over a rolling 30-day submission window. Submissions rejected because of service failures must count against the target. Retries with the same idempotency key represent one logical submission. Scheduled maintenance is not excluded. Traffic volume varies significantly throughout the day.

Which monitoring and objective configuration should a DevOps engineer implement?

**Correct answer:** Correlate submissions, rejections, and file-readiness events by idempotency key. Require at least 99.9% of eligible logical submissions to produce a correct, downloadable file within 5 minutes over rolling 30-day submission cohorts. Include maintenance and evaluate each submission after its deadline.

**Explanation:** This objective measures the required customer outcome with the specified target and window. Correlation prevents retries from inflating the denominator, includes service-side rejections and stalled jobs as failures, and allows each submission its full completion deadline before evaluation.

### Question 4 (ANS-C01)

**Question:**

A company connects 12 on-premises sites to an AWS-hosted application through redundant AWS Direct Connect connections. Each site runs a different number of synthetic transactions per minute. The network team's service level indicator (SLI) is the percentage of all synthetic transactions across all sites that complete successfully within 200 milliseconds. Every transaction must have equal weight, regardless of its originating site. Each site's monitoring collector produces two counters every minute: total transactions and transactions that meet the success and latency criteria. The team must receive a notification when the SLI is below 99.5% for three consecutive 5-minute periods. Which monitoring design meets these requirements?

**Correct answer:** Publish each site's counters as custom CloudWatch metrics. For each 5-minute period, use the Sum statistic and metric math to calculate 100 times the sum of qualifying transactions across all sites divided by the sum of total transactions across all sites. Configure an alarm below 99.5% with three evaluation periods and three datapoints to alarm, with an Amazon SNS notification action.

**Explanation:** Summing the qualifying and total transaction counts before dividing produces the required transaction-weighted SLI. The Sum statistic accumulates the minute-level counts over each 5-minute period. Requiring three breaching datapoints out of three evaluation periods implements the consecutive-period notification requirement.

## Practice Service Level Objectives in a full exam

Questions on Service Level Objectives in each practice exam, with every answer option and an explanation for each:

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 5 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 4 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Service Level Objectives

A service level objective (SLO) defines an acceptable level of service using a measurement, a target, and an evaluation window. For example, a checkout API might require at least 99.9% of eligible requests to succeed over a rolling 30-day period. A separate latency objective might require 99% of eligible requests to complete within 500 milliseconds. These targets express customer expectations more directly than infrastructure measurements such as CPU utilization.

Distinguish an SLO from a service level indicator (SLI) and a service level agreement (SLA). The SLI is the measured behavior, such as the proportion of successful checkout requests. The SLO is the target for that indicator. An SLA is an agreement that establishes service commitments and commonly specifies consequences, such as service credits, when those commitments are missed. An internal SLO is often stricter than the corresponding SLA to provide an operational safety margin, but this is a design choice rather than a requirement.

Start with business outcomes and define exactly what counts as good service. Specify the user journey, eligible requests, success criteria, measurement location, evaluation window, and treatment of maintenance and missing data. An HTTP success response does not necessarily prove that an order was recorded correctly. Similarly, a server-side latency metric may omit network delays that customers experience. Use application instrumentation and external synthetic transactions where appropriate, and document any exclusions rather than silently removing failures.

The error budget is the allowed amount of failure implied by the objective. For a request-based 99.9% success SLO, one million eligible requests permit 1,000 unsuccessful requests within the evaluation window. For a time-based availability SLO measured continuously across 30 days, 99.9% allows 43.2 minutes of unavailability, while 99.99% allows 4.32 minutes. Request-based and time-based budgets are not interchangeable because traffic varies and partial failures affect different users.

Use the target to select a proportionate cloud architecture. A revenue-generating production service may justify multiple Availability Zones, redundant application instances, load balancing, database failover, and spare capacity. A development environment may tolerate a single instance and scheduled shutdowns if its agreed service hours and recovery expectations allow them. Non-production systems that support critical releases or shared testing can still require high availability. Workload classification should reflect business impact, not labels alone.

Higher objectives usually increase infrastructure cost and operational complexity. Multi-Region deployment can address regional failures, but adds replication, routing, consistency, and failover challenges. It is not automatically necessary for every production workload. Recovery time objectives and recovery point objectives complement SLOs by specifying restoration time and acceptable data loss; they do not replace measurements of ongoing service quality.

Provider SLAs do not automatically become the application's SLA or SLO. Review each dependency's coverage, deployment prerequisites, exclusions, and failure behavior. Dependencies in a serial request path can reduce end-to-end availability, while redundancy only helps when failures are sufficiently independent and failover actually works. Multiple instances in one Availability Zone do not protect against that zone becoming unavailable.

Operationalize SLOs through dashboards, error-budget consumption alerts, and tested response procedures. Burn rate measures how quickly the service consumes its allowed failure budget relative to the expected rate; sustained rapid consumption should trigger investigation before the entire budget is exhausted. Teams can use explicit policies to prioritize reliability work or pause risky changes when the budget is depleted. Review targets with business owners as usage and consequences change, rather than treating 100% availability as a practical default.

## Learn Service Level Objectives in lessons

7 short lessons on Service Level Objectives in 3 certification courses.

- SAA-C03: Service Level Indicators vs Service Level Objectives (Premium), https://app.blowstack.com/lessons/service-level-indicators-vs-service-level-objectives-saa-c03
- SAP-C03: Error Budgets vs Service Level Objectives (Premium), https://app.blowstack.com/lessons/error-budgets-vs-service-level-objectives-sap-c03
- DOP-C02: Error Budgets vs. Service Level Objectives (Premium), https://app.blowstack.com/lessons/error-budgets-vs-service-level-objectives-dop-c02
- SAA-C03: Service Level Objectives: setting business-aligned reliability targets (Premium), https://app.blowstack.com/lessons/service-level-objectives-setting-business-aligned-reliability-targets-saa-c03
- SAP-C03: Service Level Indicators vs Service Level Objectives (Premium), https://app.blowstack.com/lessons/service-level-indicators-vs-service-level-objectives-sap-c03
- DOP-C02: Service Level Objectives: SLA-aligned availability targets (Premium), https://app.blowstack.com/lessons/service-level-objectives-sla-aligned-availability-targets-dop-c02
