Disaster recovery prepares a workload for a serious disruption. Start with acceptable downtime and data loss, then prepare and test the data, application resources and traffic changes needed to restore service.
RTO and RPO
Disaster recoveryThe preparation and actions used to restore a workload after a serious disruption. restores a workload after a serious disruption. Recovery time objectiveThe longest service interruption a business is prepared to accept. (RTO) is the downtime the business can accept. Recovery point objectiveThe oldest recoverable data a business can accept at interruption, measured as a time gap. (RPO) is the data loss it can accept, expressed as time.
How it works
- Set both objectives from business impact, dependencies and compliance needs.
- Choose a backup interval or replication design that can preserve recent enough data. Asynchronous replicationCopying changes to another data store after the source accepts them. copies changes after the source accepts them, so some changes can still be in transit when it fails.
- Choose a recovery procedure that restores service within the downtime target.
- Test the procedure. Compare the time until service returns with RTO and the age of recoverable data with RPO.
Exam cues
- If the question says data loss must stay within a stated interval, think RPO, because it limits the age of the recovery point.
- If the question says service must return within a stated interval, think RTO, because it limits downtime.
- If the question says asynchronous replication guarantees no lost writes, think replication lagThe delay between a source change and its arrival at a replica., because unreplicated changes can be lost.
Remember
- RTO measures time forward from interruption to restoration.
- RPO measures the acceptable gap between the recoverable data and interruption.
- Backup frequency affects the recoverable point. A configured schedule still needs a recovery test.
Trap: A low RPO does not prove fast service restoration. Data freshness and recovery duration are separate targets.
From the AWS docs (8)
- Recovery time objective (RTO) is the longest acceptable interval from service interruption to service restoration.
- Recovery point objective (RPO) limits the acceptable age of the last recoverable data when service is interrupted.
- Set recovery objectives from business impact, cost, dependencies and compliance requirements.
- Backup frequency determines the recoverable point for a backup-based recovery plan.
- Aurora Global Database asynchronous replication can lose unreplicated changes during unplanned failover; loss depends on replication lag.
- Test recovery paths to show that the workload recovers within its time target and to the required data state.
- RTO constrains downtime while RPO constrains lost data; choosing a stricter target than the business needs adds cost and complexity.
- Disaster recovery prepares a workload to respond to a serious disruption using business objectives for downtime and data loss.
Recovery strategy selection
A disaster recoveryThe preparation and actions used to restore a workload after a serious disruption. strategy determines how much of a workload is ready at the recovery site before a failure. Choose it from acceptable downtime, acceptable data loss and the cost of maintaining that readiness.
How it works
- Set recovery time objectiveThe longest service interruption a business is prepared to accept. (RTO), the acceptable downtime, and recovery point objectiveThe oldest recoverable data a business can accept at interruption, measured as a time gap. (RPO), the acceptable data loss in time.
- Select the preparation level below. Infrastructure as codeInfrastructure definitions stored as templates that can deploy the required resources. (IaC) means templates that can recreate infrastructure; keep application code, configuration and machine images available too.
- Test data recovery and the application’s ability to handle the failoverThe move of production traffic from the primary environment to a recovery environment. load. The ranges below describe patterns, not a guaranteed workload result.
| Strategy | Ready before failure | Recovery action | Indicative RPO / RTO |
|---|---|---|---|
| Backup and restore | Backups and deployment material | Rebuild and restore | Hours / up to a day |
| Pilot lightA recovery design with data and core infrastructure ready but more resources needed to process requests. | Data replication and core infrastructure | Deploy or start the missing application resources, then scale | Minutes / tens of minutes |
| Warm standbyA working recovery deployment kept at reduced capacity until it must take over. | Working workload at reduced capacity | Scale up | Seconds / minutes |
| Multi-site active-activeA design in which workloads in multiple Regions serve traffic during normal operation. | Workloads serving traffic in multiple RegionsA separate geographic area containing multiple isolated Availability Zones. | Use surviving Regions | Toward zero / toward zero, at the highest cost |
Hot standbyA warm standby scaled to serve the full production load. is a warm standby scaled to serve the full production load. Multi-site active-active also needs data synchronization and a way to handle concurrent write conflicts. DynamoDB global tables accept regional writes. Their default multi-Region eventual consistency (MREC) mode copies changes asynchronously and resolves concurrent changes with last writer winsConflict handling that retains the item update with the latest internal timestamp., which keeps the item version with the latest internal timestamp. Aurora global database write forwarding sends secondary writes to the primary cluster.
Exam cues
- If the question says the recovery copy cannot process requests until application resources start, think pilot light, because only core resources are ready.
- If the question says a small working stack already serves requests, think warm standby, because recovery mainly needs more capacity.
- If the question says each Region must accept database writes, think DynamoDB global tables, because Aurora write forwarding still changes data at its primary.
- If the question says cost is tight and rebuilding meets the targets, think backup and restore, because a stricter strategy adds unnecessary cost.
- If the question says lowest-cost DR where only the data and server images may run in the recovery Region, think pilot light with infrastructure as code, because servers are deployed from templates only at failover.
Remember
- Warm standby becomes hot standby when fully scaled and serving the full production load.
- Aurora unplanned recovery can take minutes and lose unreplicated changes. RDS read replicaA read-only database copy that receives changes from a source database. promotion includes a reboot and can take several minutes or longer.
- Measure full recovery, including data, application capacity and traffic movement.
Trap: A strategy’s typical RTO is not a promise. A database promotion time alone does not establish the application’s RTO.
Replicate data continuously while keeping core infrastructure ready in the recovery Region.
During normal operation, Route 53 directs clients to the primary Region.
On failover, promote the replica, scale up the standby fleet and shift traffic to the recovery Region.
Box details (5)
- App fleet
Serves all traffic during normal operation.
- Primary database
The primary database accepts writes. This example uses asynchronous replication to a recovery Region.
- Route 53 / ARC
Route 53 health checks can fail over automatically. Application Recovery Controller routing controls give a data plane on/off switch for manual failover.
- Standby app
Pilot light: servers are not running, only core pieces exist, so you start and scale them. Warm standby: a small working fleet already runs, so you only scale up.
- Replica database
The replica receives changes asynchronously. Unreplicated changes can be lost during failover. Keep point-in-time backups as well.
From the AWS docs (24)
- Backup and restore keeps backups and redeploys infrastructure, configuration and application code during recovery.
- Infrastructure as code (IaC) defines infrastructure in deployable templates; recovery also needs code, configuration and machine images.
- Pilot light keeps replicated data and core resources available but needs additional actions before it can process requests.
- Warm standby keeps a working workload at reduced capacity and scales it up for recovery.
- A warm standby that is fully scaled and serving full production load is a hot standby.
- Multi-site active-active serves traffic from multiple Regions and must handle data synchronization and write conflicts.
- Select a recovery strategy that meets business recovery objectives without unnecessary cost or complexity.
- AWS illustrates backup and restore with RPO in hours and RTO of up to a day; these are indicative strategy ranges.
- AWS illustrates pilot light with RPO in minutes and RTO in tens of minutes.
- AWS illustrates warm standby with RPO in seconds and RTO in minutes.
- AWS illustrates multi-site active-active as pushing RPO and RTO toward zero at the highest operational cost.
- Aurora Global Database recovery can take minutes, with potential data loss determined by asynchronous replication lag.
- RDS read replica promotion reboots the instance and can take several minutes or longer, depending on replica size.
- DynamoDB global tables accept writes in replica Regions and copy changes to other replicas.
- DynamoDB global tables default to multi-Region eventual consistency (MREC), which uses asynchronous replication and last-writer-wins conflict resolution.
- Aurora global database write forwarding sends writes from secondary clusters to the primary cluster; data changes first at the primary.
- Recovery testing must establish that the secondary site can handle the failover load and meet the recovery targets.
- RTO is the maximum acceptable downtime between interruption and service restoration.
- RPO is the maximum acceptable time gap between the last recoverable data and interruption.
- Route 53 health checks and ARC routing controls provide failover through data plane operations.
- Keep point-in-time backups or versioned data in the recovery site because continuous replication can copy destructive changes.
- In pilot light, data stores replicate continuously to the recovery Region while application servers stay switched off; AWS recommends not deploying them at all and deploying them from infrastructure as code such as CloudFormation when failover starts.
- For EC2 in pilot light, golden AMIs, for example from an EC2 Image Builder pipeline, are copied to the recovery Region ahead of time so servers can be launched there.
- Failing over to a cross-Region RDS read replica means promoting it to the primary; for engines other than Aurora this takes a few minutes and includes a reboot.
Availability, replication, and backup
Availability, replication and backups address different failures. An Availability ZoneAn isolated location within an AWS Region. (AZ) is an isolated location inside an AWS RegionA separate geographic area containing multiple isolated Availability Zones.. Keeping a standby in another AZ helps availability; keeping recoverable data outside the Region addresses regional loss.
How it works
- For an RDS Multi-AZ DB instance, synchronous replicationReplication that keeps a standby database synchronized with its primary. keeps a standby copy synchronized with the primary in another AZ for instance or AZ disruption. That standby does not serve application reads.
- For supported RDS engines, asynchronous read replicasA read-only database copy that receives changes from a source database., read-only database copies, receive changes after the primary. Promote a replica when using it for recovery, then direct database traffic to the promoted instance.
- For regional recovery, keep the recovery data and workload outside the affected Region.
- Retain point-in-time backups as well. Point-in-time recoveryRestoring data to an earlier recoverable state. means returning data to an earlier recoverable state, before a destructive change.
- For S3 replication, a delete markerA marker in a versioned S3 bucket that makes the object appear deleted without removing its earlier versions., which hides the current object version, stays in the source by default. Enabling marker replication copies it unless the rule is tag-based or the marker comes from lifecycle expiration.
- Pass AWS Backup a service role that trusts the service and permits the resource operations. An organization service control policy (SCP) can still deny tag-based selection.
- A logically air-gapped vaultAn AWS Backup vault with compliance-mode vault lock that can be shared with other accounts for recovery. holds locked backups that can be shared across accounts. Since November 2026, AWS Backup can archive EBS snapshots there using a backup rule that runs monthly or less often.
| Requirement | Mechanism | Boundary to remember |
|---|---|---|
| RDS instance or AZ availability | Multi-AZ DB instance standby | Same Region; standby cannot serve reads |
| RDS read scaling | Supported read replica | Asynchronous copies can be stale |
| Regional database recovery | Cross-Region replica or Aurora Global Database | Promotion and replication lagThe delay between a source change and its arrival at a replica. matter |
| Recovery before corruption | Point-in-time backups or versioning | Replication alone can copy the damage |
Aurora does not support the native RDS instance feature that replicates automated snapshots and transaction logs across Regions. Use copied cluster snapshots, AWS Backup cross-Region copies or Aurora Global Database as the design requires.
Exam cues
- If the question says an RDS instance or AZ fails, think Multi-AZ, because its standby is in another AZ.
- If the question says the entire Region is unavailable, think a recovery site in another Region, because the Multi-AZ standby shares the Region.
- If the question says a replicated delete destroyed valid data, think point-in-time recovery, because another current replica may contain the same damage.
- If an AWS Backup tag-based plan cannot select RDS resources despite role permissions, check for an SCP denying
tag:GetResources. - If infrequent EBS backups in a logically air-gapped vault need archival storage, configure the archive lifecycle on an eligible AWS Backup rule.
Remember
- Multi-AZ DB instance standby and read replica are different roles.
- Keep point-in-time backups in the recovery site alongside replicated data.
- Aurora regional backup recovery uses cluster snapshot copies or AWS Backup copies, not native cross-Region automated backup replication.
Trap: Replication is not a history of good states. It can carry a damaging change into the recovery site.
The application sends writes to the primary DB instance.
A Multi-AZ DB instance maintains a synchronous standby in another AZ for failover.
A supported cross-Region read replica receives asynchronous changes and can be promoted for regional recovery.
Box details (4)
- Application
After promoting a read replica, direct the application to the new standalone database.
- Primary DB
The primary serves writes. Multi-AZ protects against an AZ or instance failure within the Region.
- Standby DB
A Multi-AZ DB instance standby is for failover, not application reads.
- Read replica
A cross-Region read replica uses asynchronous replication and can be promoted for disaster recovery, subject to engine support.
From the AWS docs (15)
- An RDS Multi-AZ DB instance maintains a synchronous standby in another Availability Zone to protect against instance or AZ disruption.
- The standby of an RDS Multi-AZ DB instance deployment does not serve application reads.
- RDS DB instance read replicas receive changes asynchronously; supported replicas can be promoted for disaster recovery.
- Regional disaster recovery requires a recovery design outside the affected Region; multi-AZ availability operates inside one Region.
- Continuous replication can copy corruption or destructive changes; add versioning or point-in-time backups in the recovery site.
- Point-in-time recovery restores data to an earlier recoverable state, which helps recover from destructive changes.
- Aurora does not support native cross-Region automated backup replication of snapshots and transaction logs; copy DB cluster snapshots for regional recovery.
- AWS Backup can copy backups across Regions, including backups for Aurora.
- Aurora Global Database can promote a secondary regional cluster during an unplanned outage, with data loss dependent on replication lag.
- An RDS replica promoted for recovery becomes standalone; direct database traffic to it after promotion.
- Availability Zones are isolated locations within an AWS Region.
- S3 replication leaves delete markers in the source bucket by default; enabling delete marker replication copies them to the destination, except for tag-based rules and lifecycle expiration.
- AWS Backup requires a service role that trusts AWS Backup and permits the underlying backup or restore operations on the selected resources.
- An SCP denying tag:GetResources prevents AWS Backup tag-based backup plan selections even when the role has that permission.
- Since November 2026, AWS Backup supports archiving EBS snapshots in a logically air-gapped vault through a backup rule that runs monthly or less often.
Data plane and control plane failover
FailoverThe move of production traffic from the primary environment to a recovery environment. moves traffic to a recovery deployment. The data planeThe part of a service that performs its ongoing operational work. performs ongoing service work, such as answering DNS queries. The control planeThe part of a service used to create or change its configuration. creates or changes configuration. Preparing failover before an incident reduces the configuration work needed during it.
How it works
- Prepare recovery capacity and traffic routing ahead of failure. More standby capacity reduces the need to scale through control plane operations.
- Use Route 53 health-check failover or Application Recovery Controller (ARC) routing controls. A routing control is an on-off switch linked to a Route 53 health check and DNS records.
- Clients receive the resulting DNS answers. DNS time to liveThe interval for which a DNS resolver can cache an answer before querying again. (TTL) is how long a resolver can cache an answer before querying again, so cached answers affect the transition.
- For fixed client IP addresses, Global Accelerator reroutes traffic between application endpoints without changing its client-facing addresses.
CloudFront originThe server or storage location CloudFront contacts to obtain uncached content. failover operates at the request level. A cache hit is served from the cache. A cache miss tries the primary origin, the server holding the content, and a configured failure can send an eligible request to the secondary. Later origin requests try the primary again.
Exam cues
- If the question says DNS configuration APIs might be unavailable during recovery, think preconfigured health checks or ARC routing controls, because failover can use the data plane.
- If the question says clients must keep fixed IP addresses during regional failover, think Global Accelerator, because it preserves its client-facing IP addresses.
- If the question says CloudFront should retry a failed POST at the secondary, think unsupported method, because origin failover only supports GET, HEAD and eligible OPTIONS requests.
Remember
- ARC routing control still uses Route 53 DNS; it does not remove resolver caching.
- OPTIONS origin failover needs OPTIONS included in the cached HTTP methods.
- CloudFront’s secondary origin is a retry destination, not a permanent switch after one failure.
Trap: Changing DNS record weights during an incident is a configuration operation. Prepare the failover mechanism and capacity beforehand.
On an eligible cache miss, CloudFront tries the primary origin.
If the primary fails according to the configured criteria, CloudFront retries the eligible request at the secondary. Later origin requests try the primary again.
From the AWS docs (9)
- A service data plane handles ongoing service operations; its control plane configures resources. Data planes typically have higher availability design goals.
- Route 53 health checks and ARC routing controls support DNS failover through their data planes, without depending on record configuration changes.
- ARC routing controls are on-off switches connected to Route 53 health checks and DNS records to move traffic between regional replicas.
- DNS time to live (TTL) specifies how long resolvers cache a record before querying again; lower TTLs let resolvers notice changes sooner.
- Global Accelerator keeps static client-facing IP addresses and reroutes traffic when a regional application endpoint fails.
- CloudFront serves cache hits from its cache and sends cache misses to the primary origin of the configured origin group.
- CloudFront origin failover sends a request to the secondary after a configured primary failure; later origin requests try the primary again.
- CloudFront origin failover supports GET, HEAD and OPTIONS, not POST or PUT; OPTIONS must be included in cached HTTP methods.
- Increasing warm standby capacity in advance reduces reliance on control plane scaling during recovery.
Recovery runbooks and failback
A recovery runbook is a repeatable procedure for restoring service. FailbackThe return of a recovered workload to its original source infrastructure. is the later return to the original site. Plan both directions so the team can recover without depending on the failed environment.
How it works
- Define who decides to recover, the conditions for that decision and responder responsibilities. Prepare standby permissions and service quotas, the account limits on resource use.
- Identify hard dependencies, components the application cannot operate without. Recover dependent server groups in their required order. Soft dependencies can use substitutes or reduced functionality.
- Recover the data and application resources. Prepare caches, temporary copies that help serve application data, where the workload needs them.
- Redirect traffic and check restored service and data. Elastic Disaster Recovery launches recovery instances; traffic redirection remains a separate action.
- Observe the recovery workflow and stop it if it creates further risk. Systems Manager Automation or Step Functions can coordinate the steps.
- After the original site is safe, follow the tested failback procedure. For Elastic Disaster Recovery, reverse replication sends changes from recovery instances back to the source infrastructure.
Exam cues
- If the question says recovery instances are running but users still reach the failed site, think traffic redirection, because launching DRS instances does not perform that step.
- If the question says a recovery script requires the primary site’s API, think an independent recovery path, because the site and its control planeThe part of a service used to create or change its configuration. may both be unavailable.
- If the question says the original site is repaired, think failback with data synchronization, because production changes have continued at the recovery site.
Remember
- Prepare permissions and quotas before the incident.
- Regional failoverThe move of production traffic from the primary environment to a recovery environment. guidance calls for automated actions and an explicit human activation decision.
- Include service checks and an abort mechanism in recovery automation.
- Test failback as part of recovery drillsA rehearsal that launches recovery resources to test the recovery procedure..
Trap: A server launch is not the whole recovery. Dependencies, traffic redirection and service checks still determine whether users can work.
DRS launches recovery instances from replicated data in the required dependency order.
The recovery procedure separately redirects production traffic.
Check that users can use the recovered application and its data.
From the AWS docs (11)
- Document recovery roles, initiation criteria, dependency handling and a way to stop unsafe recovery automation.
- A hard dependency is required for operation with no substitute; a soft dependency can use a substitute or reduced functionality.
- Recovery planning should identify missing or corrupt data, prepare caches and define checks that confirm successful restoration.
- Recovery procedures must work when the primary site and its control plane are inaccessible.
- Systems Manager Automation and Step Functions can orchestrate complex recovery workflows.
- Prepare regional permissions and service quotas before relying on a standby Region.
- AWS multi-Region guidance recommends automated failover actions with a human activation decision for regional recovery.
- Elastic Disaster Recovery launches recovery instances from replicated data; traffic redirection is performed outside the service.
- Elastic Disaster Recovery recovery plans can recover dependent server groups in a defined order with wait times between groups.
- Failback returns workloads to their original infrastructure after recovery; Elastic Disaster Recovery supports reverse data replication for this return.
- Regular drills should include failback and feed findings back into the recovery plan.
Recovery drills and game days
A game dayA planned failure exercise involving the teams and procedures used for real incidents. rehearses a failure with the people who would respond to it. A recovery drillA rehearsal that launches recovery resources to test the recovery procedure. exercises the restoration procedure. Both expose problems in dependencies, capacity and communication before the team relies on the plan.
How it works
- Choose a business-critical workload, failure scenario and exercise objectives. Notify the technical responders and business stakeholders.
- Run the recovery procedure and observe the application. Elastic Disaster Recovery drill instances can exercise recovery without redirecting production traffic or interrupting replication.
- Measure recovery time objectiveThe longest service interruption a business is prepared to accept. (RTO), the downtime target, and recovery point objectiveThe oldest recoverable data a business can accept at interruption, measured as a time gap. (RPO), the permitted data loss in time. Check the secondary site’s ability to carry the recovery load.
- Exercise failures as well as clean switches. For fault injection with AWS Fault Injection Service (FIS), use a CloudWatch alarm as a stop conditionA configured threshold that stops an FIS experiment through a CloudWatch alarm., a threshold that stops the experiment.
- Review findings, update the runbook and track fixes. Include failbackThe return of a recovered workload to its original source infrastructure., the return to the original site, in the initial DRS drill and some later drills.
Exam cues
- If the question says replication is healthy so recovery is proven, think a recovery test, because copying data does not demonstrate restoration time or usable capacity.
- If the question says EC2 recovery must be rehearsed without moving user traffic, think DRS drill instances, because they can launch without traffic redirection.
- If the question says a fault experiment must stop at an application threshold, think an FIS stop condition backed by a CloudWatch alarm, because it stops the experiment when triggered.
Remember
- Involve business stakeholders as well as technical responders.
- Test present failoverThe move of production traffic from the primary environment to a recovery environment. load; earlier capacity results can become stale.
- A stopped FIS experiment cannot resume.
- Incorporate findings into the recovery process.
Trap: A successful clean RegionA separate geographic area containing multiple isolated Availability Zones. switch does not prove recovery under a fault. Test the expected failure scenarios too.
From the AWS docs (10)
- A game day rehearses workload-impacting failures with the teams and procedures that would handle a real incident.
- Plan game day scope and objectives, notify participants and involve technical and business stakeholders.
- Observe the exercise, stop or roll back harmful tests and incorporate findings into procedures and systems.
- Regular failover tests must establish that the recovery site works and meets RTO and RPO.
- A secondary site that handled a previous test may be too small for the present failover load.
- Elastic Disaster Recovery drills launch test instances through the recovery process without affecting source servers or ongoing replication.
- Elastic Disaster Recovery can launch drill instances without redirecting production traffic.
- Elastic Disaster Recovery guidance recommends including failback in the initial drill and some regular drills.
- An AWS FIS stop condition uses a CloudWatch alarm to stop an experiment if a defined threshold is reached; a stopped experiment cannot resume.
- Testing a clean Region switch alone does not establish behavior during failure; inject expected failure scenarios and test recovery under them.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 35 cards as a list
What do RPO and RTO measure in AWS disaster recovery?
RPO limits lost data in units of time. RTO limits how long service can remain unavailable.
Does asynchronous cross-Region replication in Aurora Global Database guarantee zero data loss during an unplanned outage?
No. Changes not yet replicated can be lost; inspect replication lag when assessing recovery.
How should a business set RTO and RPO for an AWS workload?
Use business impact and recovery requirements, including dependencies, cost and compliance. Then test the recovery path.
An AWS application replicates its data frequently but takes hours to rebuild. Does a low RPO prove a low RTO?
No. RPO limits data loss; RTO limits downtime. Measure the entire recovery path.
An AWS workload requirement limits the age of recoverable data and the delay until service returns. Which recovery objective corresponds to each limit?
RPO limits the age of recoverable data; RTO limits the delay until service returns. Test both against the business targets.
An AWS workload resumes service within its downtime target but restores data older than its permitted loss window. Which objective did it miss?
RPO. Meeting RTO does not establish that the recovered data is recent enough.
How do AWS disaster recovery strategies progress from lower cost to faster typical recovery?
Backup and restore, pilot light, warm standby, then multi-site active-active. These patterns trade cost and complexity for lower typical RTO and RPO; measure the workload.
What must an AWS backup-and-restore recovery plan preserve besides application data?
Infrastructure templates, application code, configuration and machine images needed to redeploy the workload.
What separates AWS pilot light from warm standby disaster recovery?
Warm standby can process traffic immediately at reduced capacity. Pilot light needs additional resources started or deployed first.
How do warm standby, hot standby and multi-site active-active differ in AWS disaster recovery?
Warm standby runs at reduced capacity. Hot standby has full capacity ready. Multi-site active-active serves traffic from multiple Regions during normal operation.
How should a recovery plan compare Aurora Global Database failover with RDS read replica promotion?
Aurora recovery can take minutes and can lose unreplicated changes. RDS promotion reboots the replica and can take several minutes or longer. Test the complete workload rather than assuming a fixed duration.
How do DynamoDB global table writes differ from Aurora global database write forwarding?
DynamoDB replicas accept writes in their own Regions. Aurora secondary clusters forward writes to a single primary cluster. Default DynamoDB MREC tables resolve concurrent conflicts using last writer wins.
An AWS workload has a tight recovery budget and can tolerate rebuilding from backups. Which disaster recovery pattern should the team assess first?
Backup and restore. Preserve the recovery data, infrastructure templates and application configuration, then test that rebuilding meets both objectives.
An AWS application needs a working secondary Region before a failure, but cannot justify full standby capacity. Which disaster recovery pattern fits?
Warm standby. Keep a functioning copy at reduced capacity and test scaling it to the failover load.
An AWS active-active application loses a Region. Is recovery complete simply because the other Region was already serving traffic?
No. Verify that the surviving deployment can handle the failover load and that data synchronization and write conflict handling meet requirements.
A company wants the lowest-cost DR for an EC2 web tier and an RDS database whose RTO allows minutes to rebuild servers. What should exist in the recovery Region before a disaster, and what happens at failover?
Keep a cross-Region RDS read replica and copies of the golden AMIs there. At failover, deploy the web tier from a CloudFormation template, promote the replica and point DNS at the new stack.
Does an RDS Multi-AZ DB instance deployment replace cross-Region disaster recovery?
No. Its synchronous standby protects against instance or AZ disruption inside a Region. Regional recovery needs a recovery site outside that Region.
An AWS database continuously replicates to its recovery Region. Why retain point-in-time backups too?
Replication can copy destructive changes. Backups let the team recover an earlier data state.
An RDS Multi-AZ DB instance needs more read capacity. Can the application query its standby?
No. Use a supported read replica for read scaling. The Multi-AZ DB instance standby is reserved for availability.
An Aurora team wants to replicate automated snapshots and transaction logs to another Region using the native RDS instance feature. What should it use for regional recovery?
Use copied Aurora cluster snapshots, AWS Backup cross-Region copies, or Aurora Global Database where appropriate. Native cross-Region automated backup replication is not supported for Aurora.
An Amazon S3 bucket replicates to a disaster recovery Region. What happens when a source object is deleted with default replication settings?
The delete marker stays in the source bucket, so the destination remains accessible. Enable delete marker replication to copy markers, subject to rule and lifecycle limitations.
An AWS Backup plan selects Amazon RDS resources by tags, but an organization SCP denies tag:GetResources. Does granting the service role that action fix the selection?
No. Remove the SCP denial too. AWS Backup also needs a trusted service role with permissions for the underlying backup operations.
A team uses AWS Backup to retain infrequent Amazon EBS backups in a logically air-gapped vault. Can it archive them?
Yes. Since November 2026, configure EBS snapshot archiving in a backup rule that runs monthly or less often.
Which traffic-switching approach reduces control plane dependence during cross-Region AWS disaster recovery?
Preconfigure Route 53 health-check failover or ARC routing controls and recovery capacity. They avoid needing DNS record configuration changes during the incident.
How does CloudFront origin failover differ from Route 53 failover during AWS recovery?
CloudFront retries eligible failed origin requests against a secondary but tries the primary again for later origin requests. Route 53 failover changes DNS answers; resolvers can retain cached answers until TTL expires.
A team configures CloudFront origin failover for an API. Will a failed POST request automatically retry against the secondary origin?
No. Origin failover supports GET, HEAD and eligible OPTIONS requests, not POST or PUT.
An AWS application needs regional endpoint failover while keeping the IP addresses embedded in clients. Which service fits?
Global Accelerator. Its static client-facing IP addresses stay the same as traffic is rerouted to a healthy endpoint.
What should an AWS regional recovery runbook coordinate?
Initiation criteria and responders, required dependencies, data and application recovery, traffic movement, checks for restored service, and a tested return to the original site. Provide a way to halt unsafe automation.
Elastic Disaster Recovery has launched all recovery instances. Must the team still arrange production traffic redirection?
Yes. DRS launches recovery instances; failover traffic redirection is performed separately, for example through Route 53.
An AWS regional recovery workflow depends on an API hosted only in the failed primary site. What design change is needed?
Make recovery executable independently of the primary site and its control plane. Prepare the required dependencies and regional permissions in advance.
After an AWS disaster recovery event, the original site is repaired. What must happen before returning the workload?
Use the tested failback procedure to replicate recovery-site data back and return the workload. A repaired site alone does not contain changes made during recovery.
What is an AWS resilience game day?
A planned rehearsal of a workload-impacting event using the people, procedures and systems that would respond to a real incident. Record findings and improve the recovery process.
An AWS team monitors successful replication but has never restored its workload. Has it demonstrated its RTO and RPO?
No. Run recovery tests, measure restored service and data, and confirm the secondary can handle the failover load.
An EC2 workload needs a recovery rehearsal without redirecting production traffic or interrupting replication. What feature fits?
Elastic Disaster Recovery drill instances. They exercise the recovery launch process without affecting source servers or ongoing replication.
An AWS FIS game day must stop when application latency breaches the allowed threshold. What should the team configure?
A CloudWatch alarm used as an FIS stop condition. FIS stops the experiment when the condition is triggered.