Cloud concept · Updated

Fault Isolation - Fault isolation is the design principle of containing failures within defined boundaries so they do not disrupt otherwise healthy parts of a system.

In short

Cloud systems use fault isolation to limit the scope of infrastructure failures, software defects, and resource exhaustion. Separating components into independent failure domains reduces correlated outages, but applications also need healthy alternatives and recovery mechanisms to remain available.

Cloud Concepts Hub →

5 key aspects of Fault Isolation

Effective fault isolation combines independent failure domains, containment controls, dependency-aware design, and tested recovery paths.

01
Explicit failure domains

Identify which resources can fail together because they share a host, facility, zone, dependency, or operational change. Choose deployment boundaries that match the failures the workload must survive.

02
Independent infrastructure boundaries

Availability Zones are physically separated and designed not to share infrastructure single points of failure. Place redundant components across zones when protection against a zone outage is required.

03
Limited failure propagation

Use separate resource pools, bounded queues, timeouts, and circuit breakers to keep a localized problem from exhausting healthy components. Apply these controls to software dependencies as well as infrastructure.

04
End-to-end dependency separation

Trace compute, data, networking, and supporting services across the full request path. A shared dependency in one failure domain can defeat otherwise well-distributed application servers.

05
Redundancy and tested recovery

Combine isolation with healthy alternatives, traffic redirection, and sufficient surviving capacity. Validate failure behavior through controlled tests, including database reconnection and recovery under increased load.

Cloud services for Fault Isolation

EC2 supplies application instances placed across Availability Zones, while EC2 Auto Scaling manages their distribution and replacement. Elastic Load Balancing uses health checks to route requests to healthy application targets. RDS Multi-AZ extends protection to the database tier through cross-zone deployment and managed failover. Together, these services help a workload use infrastructure isolation boundaries, but they do not remove every shared dependency. Engineers must also verify outbound connectivity, session handling, database reconnection, and surviving capacity so that a zone failure does not become an application-wide outage.

Amazon EC2Amazon EC2

EC2 lets engineers place instances in different Availability Zones to separate compute resources across infrastructure failure domains. Multiple instances in a single zone do not provide protection against loss of that zone.

Amazon RDSAmazon RDS

RDS Multi-AZ deployments maintain database resources across Availability Zones and support automatic failover for supported configurations. Applications must still handle interrupted connections and reconnect after failover; a Single-AZ database remains a zonal dependency.

Amazon EC2 Auto ScalingAmazon EC2 Auto Scaling

An Auto Scaling group configured across multiple Availability Zones distributes instances and attempts to maintain desired capacity as conditions change. Maintain sufficient surviving capacity rather than assuming replacement instances will become available immediately during an outage.

Fault Isolation exam questions

Real practice exam questions on Fault Isolation, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SOA-C03

A company runs application instances in private subnets in Availability Zones A and B. The applications must call the regional AWS Security Token Service (AWS STS) API to obtain credentials. The VPC has no NAT gateway or other internet access path. An AWS STS interface VPC endpoint has private DNS enabled and an endpoint network interface only in Zone A.

During a Zone A outage, applications in Zone B remained healthy but could not refresh their credentials. The endpoint security group and network ACLs already permit the required traffic from both application subnets. The applications use the standard regional AWS STS hostname and retry failed requests with fresh DNS lookups.

Which change should a CloudOps engineer make so that applications in a surviving zone can continue obtaining credentials after either zone becomes unavailable?

Show answerCORRECT ANSWER

Modify the existing AWS STS interface endpoint to include a subnet in Zone B while retaining its subnet in Zone A and private DNS configuration.

Adding a subnet in Zone B creates an endpoint network interface there. The endpoint then provides private connectivity through network interfaces in both zones. With private DNS and application DNS refresh and retries, applications can use a surviving endpoint interface without depending exclusively on Zone A.

SAP-C03

A logistics company processes shipment updates for 20 external partners. Updates enter one Amazon SQS Standard queue. An Amazon EC2 Auto Scaling group spans three Availability Zones, and every worker can process updates for any partner. Processing an update requires a synchronous call to that partner's API.

During an incident, one partner's API began responding very slowly. Updates for that partner occupied nearly all worker execution slots, and its growing backlog delayed updates for healthy partners. The workers remained healthy. Adding instances helped temporarily, but the affected partner eventually consumed the additional capacity.

The company requires healthy partners to continue meeting their processing latency targets throughout another partner's prolonged API degradation. Updates must remain queued for eventual processing during outages of up to 24 hours. Each partner's normal peak workload is known, and sufficient capacity can be provisioned in advance. The ingestion tier and other dependencies have sufficient capacity and are not bottlenecks.

Which architecture change meets these requirements?

Show answerCORRECT ANSWER

Create one SQS queue and one dedicated Auto Scaling group for each partner. Route updates to the appropriate queue, and restrict each group to consuming only its partner's queue. Preprovision each group for that partner's normal peak and configure queue retention to exceed the outage and recovery period.

Separating both queues and worker fleets contains the degraded partner's backlog and occupied execution slots. Healthy partners retain their own preprovisioned processing capacity. Sufficient queue retention preserves affected updates until the partner recovers and the backlog can be processed.

DVA-C02

A Python AWS Lambda function handles synchronous requests for both shipment tracking and shipping-label creation. The handler routes requests to the appropriate third-party API. The function has reserved concurrency of 100. Tracking requests require no more than 20 concurrent executions at peak load.

When the label provider becomes slow, label requests occupy all 100 concurrent executions, and tracking requests are throttled even though the tracking provider is healthy. The two request types share no other constrained resources. The application must support peak tracking traffic during a label-provider slowdown while limiting the combined concurrency of these workloads to 100.

Which change should the developer make?

Show answerCORRECT ANSWER

Deploy tracking and label creation as separate Lambda functions and route requests accordingly. Set reserved concurrency to 20 for tracking and 80 for label creation.

Separate functions with independent reserved concurrency allocations create capacity boundaries between the workloads. Label creation cannot consume tracking's 20 reserved executions, and the two function limits keep combined concurrency at or below 100.

Practice Fault Isolation in a full exam

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

Start a free practice exam

What is Fault Isolation

2 min read

Fault isolation limits how far a failure can spread. A failure domain is a set of resources that can be affected by the same event, such as a host failure, power interruption, or faulty deployment. Good architecture identifies these domains and separates resources so that one localized failure does not disable every component needed to serve a request. The scope of the resulting impact is often called the blast radius.

Cloud infrastructure provides several isolation boundaries, including physical hosts, Availability Zones, and Regions. In AWS, an Availability Zone consists of one or more discrete data centers with redundant power, networking, and connectivity. Availability Zones within a Region are physically separated and designed not to share single points of failure in their supporting infrastructure. Consequently, a localized infrastructure failure affecting one zone should not also disable another zone through the same failed infrastructure component. Low-latency links between zones support applications that distribute compute and replicate data across these boundaries.

For example, consider an application with web servers in two Availability Zones behind a load balancer. If one zone becomes unavailable, the load balancer can direct requests to healthy servers in the other zone. This only preserves the application if its other dependencies also remain usable. A database, shared file system, outbound network path, or authentication dependency confined to the failed zone can still interrupt the entire workload. Engineers must examine the complete request path rather than count only the number of web servers.

Isolation and redundancy solve related but different problems. Isolation contains a failure; redundancy supplies alternatives. Two virtual machines on the same physical host provide less protection from host failure than machines on separate hosts. Similarly, multiple servers in one zone do not protect against loss of that zone. Deploying across zones does not automatically configure database replication, traffic failover, or adequate surviving capacity. These require explicit architectural choices or appropriately configured managed services.

Fault isolation also applies to software and operations. Separate worker pools can prevent one customer's expensive jobs from exhausting every worker. Timeouts and circuit breakers can stop a failed dependency from consuming all application connections. Staggered deployments can keep a defective release from reaching every zone simultaneously. Infrastructure separation cannot contain a configuration error that is deliberately applied everywhere at once.

The trade-offs include additional infrastructure cost, cross-zone transfer charges where applicable, replication latency, and greater operational complexity. Surviving resources need enough capacity to absorb redirected traffic, and database failover may interrupt connections even when data remains protected. Test zone-loss scenarios, connection recovery, and dependency behavior rather than assuming that a multi-zone diagram proves resilience. For certification questions, recognize Availability Zones as isolated infrastructure failure domains within a Region, not as individual servers or synonyms for Regions. Their separation reduces shared failure exposure; it does not guarantee that every application failure or regional event is isolated.

Learn Fault Isolation in lessons

7 short lessons on Fault Isolation in 5 certification courses.

and 1 more lesson

Open the lessons