# High availability

High availability is the design and operation of a system to remain accessible and usable despite component failures or maintenance.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/high-availability

> High availability reduces service interruptions by combining redundant components, isolated failure domains, health monitoring, and recovery mechanisms. In the cloud, it commonly involves distributing workloads across multiple Availability Zones so that a failure in one location does not stop the entire application.

Practice exams covering High availability: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [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 High availability

High availability combines isolated redundancy, health-aware routing, resilient state, automated recovery, and tested capacity to minimize service interruptions.

1. **Redundancy without single points of failure**: Provide alternative components for critical parts of the request path, including application instances, databases, and network dependencies. Verify that replicas do not all depend on the same unprotected component.
2. **Failure-domain isolation**: Distribute resources across multiple Availability Zones to reduce exposure to a single-zone disruption. Use multiple Regions when the workload must also withstand a regional disruption and the added complexity is justified.
3. **Health-aware traffic distribution**: Use load balancing and meaningful health checks to direct requests toward functioning application targets. Health checks should indicate readiness to serve requests without causing unnecessary removal of otherwise usable capacity.
4. **Automated recovery and resilient clients**: Automate replacement of failed compute resources and failover of supported stateful components. Configure clients to recover connections and retry transient failures safely, using bounded retries and backoff.
5. **Resilient state and sufficient capacity**: Keep important state in data stores designed for the required failure scenarios rather than only on individual application instances. Ensure surviving resources have enough capacity to maintain acceptable service after a failure.
6. **Measured and tested availability**: Define availability objectives using successful user operations, not just infrastructure uptime. Test failure scenarios and maintenance procedures to confirm that routing, recovery, and capacity behave as intended.

## Cloud services for High availability

Elastic Load Balancing provides the application entry point and distributes requests across instances in multiple Availability Zones. Amazon EC2 Auto Scaling maintains compute capacity and replaces unhealthy instances, while an Amazon RDS Multi-AZ deployment protects the database tier through replication and automated failover. Amazon CloudWatch helps operators detect errors, capacity shortages, and recovery failures. For workloads deployed in multiple Regions, Amazon Route 53 can steer clients toward healthy regional endpoints. These services must be configured together with resilient session storage, appropriate client retries, and enough surviving capacity; no individual service makes the complete application highly available.

- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: Amazon EC2 Auto Scaling maintains desired instance capacity and replaces instances identified as unhealthy. An Auto Scaling group spanning multiple Availability Zones distributes compute capacity across failure domains; Elastic Load Balancing health checks can also be enabled for replacement decisions.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon RDS offers Multi-AZ deployment options that replicate database data across Availability Zones and provide automated failover. A traditional Multi-AZ DB instance deployment uses a standby for availability rather than read scaling; application connections can still experience a brief interruption during failover.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Amazon Route 53 supports DNS routing policies and health evaluation that can direct clients toward healthy application endpoints, including endpoints in different Regions. DNS-based failover is not instantaneous because detection time, DNS caching, and client behavior affect recovery.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon CloudWatch provides metrics, alarms, logs, and application monitoring capabilities that help detect availability problems. Monitoring can support automated responses, but it does not itself supply redundant application capacity.

## High availability exam questions

Real practice exam questions on High availability, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company runs a customer booking application on redundant application servers across two Availability Zones. All application servers connect to one database server. When the database server fails, customers cannot make bookings even though the application servers are healthy. Which change would best reduce interruptions from this type of failure?

**Correct answer:** Maintain a replicated standby database in another Availability Zone and configure automatic failover.

**Explanation:** A replicated standby and automatic failover provide an alternative when the primary database fails. Separating the databases across Availability Zones also reduces their exposure to the same location-level disruption.

### Question 2 (DEA-C01)

**Question:**

A company runs an event-processing application in two AWS Regions. The application stores job status in Amazon DynamoDB. Each Region processes a different set of jobs, so concurrent updates to the same item do not occur. Both Regions must be able to read and update the shared dataset through local database endpoints. If either Region becomes unavailable, the application in the surviving Region must continue reading and writing without restoring data or promoting a database. Asynchronous replication and eventual consistency between Regions are acceptable. Application traffic routing and sufficient processing capacity are already configured.

Which database configuration meets these requirements with the least operational overhead?

**Correct answer:** Configure a DynamoDB global table with a replica in each Region and multi-Region eventual consistency. Configure each application's DynamoDB client to use its local Regional endpoint.

**Explanation:** DynamoDB global tables provide managed, multi-Region replication with writable replicas. Each application can use its local replica, and the surviving Region can continue reading and writing without a restore or database promotion. Multi-Region eventual consistency meets the stated consistency requirement.

### Question 3 (SAP-C03)

**Question:**

A financial services company runs an application behind Application Load Balancers (ALBs) in two AWS Regions. Amazon Route 53 failover alias records provide active-passive routing. The secondary Region has sufficient capacity, is independently monitored, and is healthy.

The primary Region can process transactions only when its identity service and at least two of three independent transaction gateways are healthy. Each dependency exposes a separate public HTTPS health endpoint with a Region-specific hostname. These endpoints accurately report dependency health. The ALB target health checks monitor only application process liveness and remain successful during dependency failures.

The company requires automatic DNS failover whenever the primary Region cannot process transactions. A single transaction gateway failure must not trigger failover if the identity service and the other two gateways remain healthy. The solution must use native Route 53 health checks without custom automation.

Which configuration should a solutions architect apply to the primary failover record?

**Correct answer:** Create HTTPS health checks for all four dependencies. Create a calculated health check that requires at least two healthy gateway checks. Create another calculated health check that requires both the identity check and the gateway calculated check to be healthy. Associate the outer calculated health check with the primary record.

**Explanation:** Nested calculated health checks implement the required condition: identity service healthy AND at least two gateways healthy. Associating the outer check with the primary failover record makes Route 53 select the healthy secondary when this condition fails, subject to DNS caching and health-check detection time.

### Question 4 (SAA-C03)

**Question:**

A company runs a stateless customer portal on four EC2 instances in an Auto Scaling group. The group has a minimum and desired capacity of four and uses two private subnets. An Application Load Balancer (ALB) is enabled in two Availability Zones and forwards requests to the group's attached target group.

During a resilience review, a solutions architect discovers that both subnets selected for the Auto Scaling group are in the same Availability Zone. A suitable private subnet already exists in the second Availability Zone. Two application instances can handle the portal's full workload, and all application dependencies can tolerate an Availability Zone failure.

The company requires the portal to continue serving its full workload after either Availability Zone fails, without waiting for replacement instances to launch. Which change should the solutions architect make?

**Correct answer:** Update the Auto Scaling group to use one private subnet in each Availability Zone. Keep its minimum and desired capacity at four, and allow the group to rebalance before completing the resilience review.

**Explanation:** An Auto Scaling group distributes instances across its configured Availability Zones. After rebalancing, the group will normally have two instances in each zone. The surviving zone therefore has enough already-running capacity to serve the full workload while Auto Scaling attempts to replace lost instances.

### Question 5 (DOP-C02)

**Question:**

A company operates a stateless API in three AWS Regions. Each regional deployment has independent dependencies and enough capacity to handle the entire workload. Each deployment has a unique public hostname and a public HTTPS readiness endpoint that accurately reports whether that Region can process requests. Amazon Route 53 hosts the public zone for api.example.com, which is not the zone apex.

During normal operation, approximately 70% of DNS responses must select the deployment in us-east-1 and 30% must select the deployment in eu-west-1. If either of these deployments becomes unhealthy, the other must receive all new DNS responses. The deployment in ap-southeast-2 must be selected only when both other deployments are unhealthy and it remains healthy. These requirements apply after health checks detect failures and cached DNS answers expire.

Which Route 53 configuration meets these requirements without custom failover automation?

**Correct answer:** Create weighted CNAME records for api.example.com with weights of 70, 30, and 0 for us-east-1, eu-west-1, and ap-southeast-2, respectively. Associate each record with an HTTPS health check of its Region's readiness endpoint.

**Explanation:** Route 53 distributes responses among healthy nonzero-weight records according to their relative weights. If one active Region fails, the remaining healthy nonzero-weight record receives the responses. When all nonzero-weight records are unhealthy, Route 53 considers zero-weight records and can select the healthy ap-southeast-2 deployment. Checking all three records ensures that the standby's readiness is evaluated too.

### Question 6 (ANS-C01)

**Question:**

A company centralizes hybrid DNS in a networking account. A shared-services VPC contains a Route 53 Resolver inbound endpoint and an outbound endpoint. Each endpoint has one IP address in each of two Availability Zones. Private hosted zones are associated with the shared-services VPC, and application VPCs use a shared forwarding rule for corp.example.com through the outbound endpoint.

On-premises DNS servers conditionally forward the AWS private namespace to only the inbound endpoint IP address in Availability Zone A. The outbound forwarding rule targets only DNS server DC1. A second on-premises server, DC2, independently serves the same corporate zones from another data center.

The company must maintain DNS resolution in both directions after the loss of either AWS Availability Zone or either on-premises DNS server, without operator intervention. Surviving components have sufficient capacity. Redundant network connectivity, routes, and DNS filtering are already configured for all endpoint IP addresses and both on-premises servers. The on-premises forwarding software can retry another configured destination when a destination does not respond.

Which change meets these requirements?

**Correct answer:** Configure the on-premises conditional forwarders with both inbound endpoint IP addresses. Update the existing outbound forwarding rule to include both DC1 and DC2 as target IP addresses.

**Explanation:** This removes the single configured destination in each direction. On-premises forwarders can retry the surviving inbound endpoint IP after an Availability Zone failure. The outbound endpoint already spans Availability Zones, and including both corporate DNS servers as rule targets preserves an available destination if either server fails.

## Practice High availability in a full exam

Questions on High availability in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 21 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 20 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 17 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 4 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions

## What is High availability

High availability means keeping a service usable for the required proportion of time, including when infrastructure fails or maintenance occurs. Availability should be measured from the user's perspective: a running server does not make an application available if users cannot log in or complete transactions. An availability target of 99.9% allows approximately 43 minutes of unavailability in a 30-day month. Higher targets generally require additional redundancy, automation, testing, and operational effort.

The central design principle is to avoid single points of failure. Two application servers provide limited protection if both depend on one database, one network appliance, or one power source. Engineers must examine the entire request path, including traffic routing, compute, storage, authentication, and external dependencies. Redundant capacity must also be sufficient to serve the required workload after a component or location fails.

Cloud infrastructure provides failure domains that help separate redundant components. In AWS, a Region is a geographic area containing multiple Availability Zones. Each Availability Zone consists of one or more discrete data centers with redundant power, networking, and connectivity. Deploying application instances across at least two Availability Zones in one Region is a common approach to surviving an instance failure or an Availability Zone disruption. Several instances in one Availability Zone do not provide the same protection.

A load balancer distributes incoming traffic across registered application targets and uses health checks to identify targets that should receive requests. For example, an online store can run application instances in two Availability Zones behind a load balancer. When one instance fails, the load balancer can direct requests to other healthy instances while an automated scaling group replaces the failed instance. This behavior depends on correct health checks, routing configuration, and sufficient healthy capacity; a load balancer alone does not make the entire application highly available.

Application state needs equal attention. Storing shopping carts only in an instance's memory can cause users to lose their carts when traffic moves elsewhere. Externalizing session state to an appropriately resilient data store makes application instances easier to replace. A database deployment with synchronous replication and automated failover can protect against certain infrastructure failures, although failover can still briefly interrupt connections. Clients need suitable timeouts, retries, and connection recovery.

Multiple Regions provide protection against a broader class of disruptions, including loss of an entire Region. An application might actively serve traffic in two Regions or maintain a standby environment in another Region. However, multi-Region operation introduces additional cost, replication delay, data consistency decisions, routing complexity, and failover procedures. It is not necessary for every highly available workload. Choose it when business requirements justify regional failure protection, and define recovery time and acceptable data loss explicitly.

High availability is related to, but different from, elasticity and agility. Elasticity adjusts capacity as demand changes, while agility enables teams to provision resources and deliver changes quickly. Elastic scaling can support availability during demand spikes, but it does not replace redundancy. Backups support recovery but do not keep a failed service immediately accessible. Fault tolerance generally aims to continue operating without interruption through specified failures, whereas high availability can allow brief recovery periods.

Practical operation includes monitoring successful user transactions, testing failover, deploying changes gradually, and checking that surviving resources can handle peak demand. Redundancy increases cost and complexity, and shared configuration errors can affect every replica at once. High availability is therefore an end-to-end engineering outcome, not a guarantee obtained simply by selecting multiple locations or buying a service with an availability commitment.

## Learn High availability in lessons

24 short lessons on High availability in 5 certification courses.

- CLF-C02: Failover and high availability: mechanism versus objective (Premium), https://app.blowstack.com/lessons/failover-and-high-availability-mechanism-versus-objective-clf-c02
- DEA-C01: High availability vs. resiliency (Premium), https://app.blowstack.com/lessons/high-availability-vs-resiliency-dea-c01
- SAP-C03: Fault Tolerance vs High Availability (Premium), https://app.blowstack.com/lessons/fault-tolerance-vs-high-availability-sap-c03
- SAA-C03: Data Durability vs. High Availability (Premium), https://app.blowstack.com/lessons/data-durability-vs-high-availability-saa-c03
- DOP-C02: Disaster recovery vs. high availability (Premium), https://app.blowstack.com/lessons/disaster-recovery-vs-high-availability-dop-c02
- CLF-C02: High availability and disaster recovery: continuity versus restoration (Premium), https://app.blowstack.com/lessons/high-availability-and-disaster-recovery-continuity-versus-restoration-clf-c02
