Cloud concept · Updated

Resiliency - Resiliency is a system’s ability to withstand disruptions and recover while continuing to meet defined business requirements.

In short

Resiliency combines failure isolation, redundant resources, controlled recovery, and operational testing to limit the impact of failures. In the cloud, it requires deliberate architecture across independent failure domains rather than assuming that provider-managed infrastructure makes an application immune to outages.

Cloud Concepts Hub →

6 key aspects of Resiliency

Resiliency combines isolated failure domains, end-to-end redundancy, controlled failover, measurable recovery objectives, and tested operating procedures.

01
Independent failure domains

Distribute critical resources across boundaries that isolate infrastructure failures. AWS Availability Zones are designed to avoid shared infrastructure single points of failure, making multi-zone placement a foundation for surviving a zonal outage.

02
Redundancy across the dependency chain

Provide redundant compute, data, and network paths rather than duplicating only application servers. Check that a shared database, session store, or outbound network dependency does not undermine the design.

03
Health-aware failover

Detect unhealthy resources and redirect work to healthy ones. Ensure surviving resources have sufficient capacity and that clients can reconnect after failover.

04
Defined recovery objectives

Set recovery time and recovery point objectives based on business impact. Use them to choose replication, backup, and restoration approaches instead of assuming every workload needs the same architecture.

05
Controlled degradation

Keep essential functions available when optional dependencies fail. Use timeouts, bounded retries, and dependency isolation to reduce cascading failures.

06
Tested recovery procedures

Exercise failover and backup restoration under controlled conditions. Measure recovery results against objectives and correct gaps in automation, capacity, and operating procedures.

Cloud services for Resiliency

Elastic Load Balancing directs requests to healthy application instances, while Amazon EC2 Auto Scaling maintains compute capacity across configured Availability Zones. Amazon RDS Multi-AZ deployments extend zonal protection to the database layer. AWS Backup adds recovery points for scenarios where replication alone is insufficient, such as accidental data deletion. AWS Fault Injection Service helps validate selected failure scenarios under controlled conditions. Together, these services support a resilient architecture, but engineers must still configure dependencies, reserve sufficient surviving capacity, implement client recovery behavior, and test restoration against business objectives.

Amazon EC2 Auto ScalingAmazon EC2 Auto Scaling

Maintains desired instance capacity and can distribute instances across configured Availability Zones. It can replace unhealthy instances, but replacement depends on available capacity and application startup time.

Amazon RDSAmazon RDS

Supported Multi-AZ deployments replicate database data across Availability Zones and provide automatic failover. Failover can interrupt connections, so applications still need appropriate reconnection and retry behavior.

AWS BackupAWS Backup

Centralizes backup policies for supported resources and supports cross-Region or cross-account copies for supported resource types. Backups complement replication by providing recovery points, but successful recovery still requires tested restoration procedures.

Resiliency exam questions

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

AIB-C01 (beta)

An insurer is expanding an AI claims-classification pilot to all customer channels. The application currently waits for a shared AI service to classify each claim before confirming receipt. During a service interruption, waiting requests exhaust application capacity and prevent customers from submitting claims. Business leaders approve classification after submission, but require claim intake to remain available during AI service interruptions and submitted claims to be retained for later processing. Which approach should the AI business strategist recommend?

Show answerCORRECT ANSWER

Durably record claims and confirm receipt before classification, isolate AI processing through a durable queue, and test backlog recovery and duplicate-processing controls under peak demand.

This separates essential claim intake from the AI dependency. Claims remain available for later classification during an interruption, while recovery testing and duplicate-processing controls help ensure that queued work can be processed safely when service resumes.

DEA-C01

A company uses AWS Backup to create daily recovery points for an Amazon RDS for PostgreSQL database. All backup jobs report success. During a disaster recovery review, a data engineer must establish a recurring process to determine whether a selected recovery point can produce a usable database within the company's 60-minute recovery time objective. The process must run representative SQL queries against recovered data without modifying the production database and must remove temporary resources afterward.

Which solution meets these requirements with the least operational overhead?

Show answerCORRECT ANSWER

Configure scheduled AWS Backup restore testing for the database recovery points. Add an automated validation workflow that connects to the restored database, runs the SQL queries, and records recovery and validation timing. Use restore testing cleanup to remove the test resources.

AWS Backup restore testing periodically restores selected recovery points without modifying the source database. An automated validation workflow can verify the recovered data with SQL queries and measure whether recovery and validation complete within 60 minutes. Restore testing provides cleanup of the temporary restored resources, reducing custom orchestration.

AIP-C01

A company runs an Amazon Bedrock application in two AWS Regions behind an existing health-based traffic-routing layer. Both application deployments currently invoke the Bedrock Runtime endpoint in the primary Region by using a geography-scoped cross-Region inference profile. This configuration handles inference-capacity shortages successfully.

During a disaster recovery test, the primary Region's Bedrock Runtime endpoint becomes unreachable. Client traffic shifts successfully to the secondary application deployment, but inference requests still fail. The company must continue using the same approved foundation model without operating model-serving infrastructure. The model is available through supported cross-Region inference profiles from both application Regions, but it does not support direct in-Region invocation in the secondary Region. All destination Regions in the supported profiles are approved for processing the company's data, and the required permissions are configured.

Which change BEST addresses the failure demonstrated by the test?

Show answerCORRECT ANSWER

Configure each application deployment to use its local Bedrock Runtime endpoint and a cross-Region inference profile supported from that source Region. Use bounded retries against that configuration.

Cross-Region inference routes an accepted request to available inference capacity, but it does not make an unreachable source Region's Runtime endpoint available. Using the secondary Region's Runtime endpoint with a profile supported from that Region removes the primary endpoint dependency while preserving the approved model and managed inference.

Practice Resiliency in a full exam

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

Start a free practice exam

What is Resiliency

2 min read

Resiliency means designing a system to handle disruption without unacceptable loss of service or data. Disruptions include hardware failures, network interruptions, software defects, traffic spikes, and operator mistakes. A resilient system may continue operating normally, provide reduced functionality, or recover within an agreed time. The appropriate behavior depends on business requirements rather than an assumption that every component must remain available continuously.

A central cloud design principle is to distribute resources across independent failure domains. In AWS, a Region contains multiple Availability Zones. Each 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 to avoid shared infrastructure single points of failure, so a power or facility failure in one zone should not disable the others. They are connected through low-latency networking that supports applications spanning multiple zones.

This isolation is the key distinction tested in foundational certification questions: multiple servers in one Availability Zone do not provide the same protection as servers distributed across multiple Availability Zones. However, zone isolation does not guarantee that an application has no shared dependencies. A database deployed only in one zone, a shared external dependency, or a defective deployment applied everywhere can still disrupt the entire workload.

For example, an online store can run stateless application servers across two or more zones behind a load balancer. If servers in one zone become unreachable, health checks allow traffic to move to healthy targets. The remaining servers need enough capacity to carry the load, and the database and session storage must also support the intended failure scenario. Merely adding servers in another zone is insufficient when all requests depend on a single-zone database.

Recovery design must address both service restoration and data protection. A recovery time objective defines the target time to restore service, while a recovery point objective defines the acceptable amount of data loss measured in time. Replication can support rapid failover, but it may also propagate accidental deletion or corruption. Backups provide a separate recovery mechanism, and restore tests establish whether those backups can meet recovery objectives.

Resiliency has costs and operational trade-offs. Redundant capacity, replication, monitoring, and testing increase spending and complexity. Cross-zone communication can introduce data-transfer charges, while cross-Region designs add latency and data-consistency considerations. Multi-zone deployment addresses zonal failures; protection against a regional disruption requires a separate regional recovery strategy appropriate to the workload.

Resiliency is broader than high availability or fault tolerance alone: it also includes recovery and adaptation after disruption. Engineers should test failover, verify capacity after losing a zone, and practice restoration procedures. Bounded retries, timeouts, and graceful degradation help prevent a failing dependency from exhausting otherwise healthy components. Provider infrastructure supplies isolation mechanisms, but application configuration and operational practices determine whether the workload benefits from them.

Learn Resiliency in lessons

6 short lessons on Resiliency in 4 certification courses.

Open the lessons