Disaster Recovery practice questions

A retail platform needs disaster recovery across AWS Regions. The business requirement is: RTO up to 6 hours, RPO up to 1 hour, and they want the ability to start serving quickly during a Region outage but do not want to run full production capacity continuously. Which DR strategy best fits these requirements?

Trap 1: Backup and restore only, with no continuously running…

Backups with no warm infrastructure typically lead to longer recovery times and may miss a 6-hour RTO target.

Trap 2: Pilot light, keeping only the minimum resources needed to bootstrap…

Pilot light usually provides very limited capacity and may still take too long to become fully operational within 6 hours.

Trap 3: Multi-site active-active, serving production traffic from both…

Active-active involves running full production in both Regions, which is more operationally complex and costlier than required.

A
Backup and restore only, with no continuously running infrastructure in the secondary Region.
Why wrong: Backups with no warm infrastructure typically lead to longer recovery times and may miss a 6-hour RTO target.
B
Pilot light, keeping only the minimum resources needed to bootstrap the environment.
Why wrong: Pilot light usually provides very limited capacity and may still take too long to become fully operational within 6 hours.
C
Warm standby, keeping a reduced but ready-to-scale environment in the secondary Region.
Warm standby maintains enough infrastructure to reduce recovery time, while not fully running production capacity continuously.
D
Multi-site active-active, serving production traffic from both Regions at all times.
Why wrong: Active-active involves running full production in both Regions, which is more operationally complex and costlier than required.

Question 2mediummultiple choice

A trading dashboard stores uploaded documents in S3. The business requires a copy in another AWS Region for disaster recovery. What should be configured?

Trap 1: An EBS snapshot schedule

EBS snapshots do not apply to S3 objects.

Trap 2: S3 lifecycle transition to Glacier Flexible Retrieval

Lifecycle transition changes storage class, not Region.

Trap 3: A CloudFront distribution

CloudFront caches content but is not a durable DR copy.

A
An EBS snapshot schedule
Why wrong: EBS snapshots do not apply to S3 objects.
B
S3 Cross-Region Replication with versioning enabled
CRR asynchronously replicates objects to a bucket in another Region and requires versioning.
C
S3 lifecycle transition to Glacier Flexible Retrieval
Why wrong: Lifecycle transition changes storage class, not Region.
D
A CloudFront distribution
Why wrong: CloudFront caches content but is not a durable DR copy.

Question 3mediummultiple choice

A trading dashboard uses Aurora MySQL. The company wants fast cross-Region disaster recovery with low RPO. Which architecture should be considered?

Trap 1: A single-AZ Aurora cluster

Single-AZ design does not provide cross-Region DR.

Trap 2: Manual snapshots copied monthly

Monthly snapshots create high RPO and slow recovery.

Trap 3: An ElastiCache Redis replica

ElastiCache is not an Aurora database DR mechanism.

A
A single-AZ Aurora cluster
Why wrong: Single-AZ design does not provide cross-Region DR.
B
Aurora Global Database
Aurora Global Database replicates with low latency to secondary Regions and supports faster disaster recovery than snapshot-only approaches.
C
Manual snapshots copied monthly
Why wrong: Monthly snapshots create high RPO and slow recovery.
D
An ElastiCache Redis replica
Why wrong: ElastiCache is not an Aurora database DR mechanism.

Question 4mediummultiple choice

A payments platform requires disaster recovery across Regions. Requirements: RPO of 15 minutes and RTO of about 1 hour. The business cannot afford full duplicate capacity in both Regions all the time, but the team wants automated readiness so failover is mostly operationally guided rather than a slow rebuild. Which DR strategy is the best fit?

Trap 1: Backup and restore only, relying on scheduled snapshots and manual…

Backup/restore can meet data-loss tolerance in some cases, but RTO of 1 hour is often too aggressive for manual restores.

Trap 2: Pilot light, keeping only minimal infrastructure in the secondary…

Pilot light is cheaper, but RTO of 1 hour may not be achievable if full compute/services must be brought up from near-zero.

Trap 3: Active/active, routing production traffic to both Regions…

Active/active best fits very low RTO and high availability, but it usually costs more than the stated budget constraints.

A
Backup and restore only, relying on scheduled snapshots and manual restores during incidents.
Why wrong: Backup/restore can meet data-loss tolerance in some cases, but RTO of 1 hour is often too aggressive for manual restores.
B
Pilot light, keeping only minimal infrastructure in the secondary Region and starting full services after failover.
Why wrong: Pilot light is cheaper, but RTO of 1 hour may not be achievable if full compute/services must be brought up from near-zero.
C
Warm standby, keeping core infrastructure and a partially provisioned environment ready in the secondary Region with frequent data replication.
Warm standby balances cost and readiness by keeping enough capacity and services running to shorten recovery time while meeting RPO needs.
D
Active/active, routing production traffic to both Regions continuously and accepting dual-region complexity.
Why wrong: Active/active best fits very low RTO and high availability, but it usually costs more than the stated budget constraints.

Question 5mediummultiple choice

A trading dashboard stores uploaded documents in S3. The business requires a copy in another AWS Region for disaster recovery. What should be configured? The design must avoid adding custom operational scripts.

Trap 1: An EBS snapshot schedule

EBS snapshots do not apply to S3 objects.

Trap 2: S3 lifecycle transition to Glacier Flexible Retrieval

Lifecycle transition changes storage class, not Region.

Trap 3: A CloudFront distribution

CloudFront caches content but is not a durable DR copy.

A
An EBS snapshot schedule
Why wrong: EBS snapshots do not apply to S3 objects.
B
S3 Cross-Region Replication with versioning enabled
CRR asynchronously replicates objects to a bucket in another Region and requires versioning.
C
S3 lifecycle transition to Glacier Flexible Retrieval
Why wrong: Lifecycle transition changes storage class, not Region.
D
A CloudFront distribution
Why wrong: CloudFront caches content but is not a durable DR copy.

Question 6mediummulti select

A company is designing a multi-Region disaster recovery (DR) strategy for a stateless web application running on Amazon EC2 instances behind an Application Load Balancer (ALB). The application uses an Amazon RDS for MySQL database as its data store. The architecture must provide rapid failover with the lowest possible Recovery Point Objective (RPO) and Recovery Time Objective (RTO). Which of the following design choices will help achieve these objectives? (Choose four.)

Trap 1: Set up Amazon RDS Multi-AZ deployment to enable automatic failover…

While Amazon RDS Multi-AZ deployments provide high availability and automatic failover within a single AWS Region, they do not protect against a regional disaster. If the entire primary AWS Region becomes unavailable, the Multi-AZ standby replica in a different Availability Zone within that same region would also be affected, failing to meet the multi-region disaster recovery requirement.

Trap 2: Use an Amazon RDS for MySQL single-AZ deployment in the primary…

A single-AZ RDS deployment lacks high availability within the primary region, making it vulnerable to AZ failures. Furthermore, relying on daily snapshots for multi-region disaster recovery results in a high Recovery Point Objective (RPO), meaning up to 24 hours of data could be lost. The manual restoration process from snapshots also leads to a high Recovery Time Objective (RTO), making this approach unsuitable for robust DR.

A
Configure an active-passive failover strategy by deploying the application stack in two AWS Regions and using Amazon Route 53 health checks with a failover routing policy.
This strategy establishes a primary active region and a secondary passive region, where the application stack is fully deployed but not actively serving traffic. Amazon Route 53 health checks continuously monitor the primary region's health. If a failure is detected, the failover routing policy automatically redirects traffic to the healthy secondary region, ensuring business continuity with minimal downtime.
B
Set up Amazon RDS Multi-AZ deployment to enable automatic failover to a standby replica in a different Availability Zone within the primary Region.
Why wrong: While Amazon RDS Multi-AZ deployments provide high availability and automatic failover within a single AWS Region, they do not protect against a regional disaster. If the entire primary AWS Region becomes unavailable, the Multi-AZ standby replica in a different Availability Zone within that same region would also be affected, failing to meet the multi-region disaster recovery requirement.
C
Use Amazon RDS cross-Region read replicas with automatic failover to promote a read replica to a primary instance in the secondary Region.
For stateful applications relying on databases, Amazon RDS cross-Region read replicas continuously replicate data from the primary database in one region to a read replica in a secondary region. In a disaster scenario, this read replica can be quickly promoted to a standalone primary instance, minimizing data loss and providing a fully functional database in the secondary region for recovery.
D
Deploy the application and ALB in an active-active configuration across two AWS Regions using Amazon Route 53 latency-based routing.
An active-active configuration involves deploying the full application stack in two or more AWS Regions, with both regions simultaneously serving traffic. Amazon Route 53 latency-based routing directs user requests to the region that provides the lowest network latency, effectively distributing the load and providing inherent disaster recovery as traffic automatically shifts away from an unhealthy region.
E
Store static assets and application state in Amazon S3 with cross-Region replication enabled, and serve them via Amazon CloudFront.
Storing static assets and application state in Amazon S3 with cross-Region replication ensures data durability and availability across multiple regions. Amazon CloudFront, a global content delivery network, can then serve these assets from the nearest edge location, improving performance and providing resilience by automatically pulling content from the healthy S3 bucket in either region during a disaster.
F
Use an Amazon RDS for MySQL single-AZ deployment in the primary Region and take daily snapshots copied to the secondary Region.
Why wrong: A single-AZ RDS deployment lacks high availability within the primary region, making it vulnerable to AZ failures. Furthermore, relying on daily snapshots for multi-region disaster recovery results in a high Recovery Point Objective (RPO), meaning up to 24 hours of data could be lost. The manual restoration process from snapshots also leads to a high Recovery Time Objective (RTO), making this approach unsuitable for robust DR.

Question 7mediummultiple choice

Your media processing pipeline writes original uploads to an S3 bucket and later generates derivative files. An operator accidentally deletes a subset of original uploads in production. You need to (1) restore the deleted objects with minimal data loss and (2) protect against both regional disasters and future operator mistakes. The company requires recovery even if objects are deleted and later overwritten.

What is the most effective change to meet these requirements?

Trap 1: Move all objects to S3 Glacier Instant Retrieval and apply a…

Glacier storage tiers do not prevent deletion of the latest version, and keeping only the latest copy fails the recovery requirement.

Trap 2: Use S3 server-side encryption with KMS keys and rely on access logs…

Encryption protects confidentiality but does not retain deleted data, and access logs do not reconstruct object contents.

Trap 3: Enable S3 bucket policies that deny DeleteObject, but do not enable…

A deny policy can reduce future mistakes, but it does not provide recovery for the already-deleted objects or disaster resilience.

A
Enable S3 versioning on the bucket and configure cross-Region replication so previous versions are available after regional loss and accidental deletion.
Versioning retains prior object versions, and cross-Region replication provides redundancy across Regions for recovery after deletion or disaster.
B
Move all objects to S3 Glacier Instant Retrieval and apply a lifecycle policy to keep only the latest object copy.
Why wrong: Glacier storage tiers do not prevent deletion of the latest version, and keeping only the latest copy fails the recovery requirement.
C
Use S3 server-side encryption with KMS keys and rely on access logs to manually recover the deleted objects.
Why wrong: Encryption protects confidentiality but does not retain deleted data, and access logs do not reconstruct object contents.
D
Enable S3 bucket policies that deny DeleteObject, but do not enable versioning or replication.
Why wrong: A deny policy can reduce future mistakes, but it does not provide recovery for the already-deleted objects or disaster resilience.

Question 8mediummultiple choice

A payments platform requires disaster recovery across Regions. Requirements: RPO of 15 minutes and RTO of about 1 hour. The business cannot afford full duplicate capacity in both Regions all the time, but the team wants automated readiness so failover is mostly operationally guided rather than a slow rebuild. Which DR strategy is the best fit?

Trap 1: Backup and restore only, relying on scheduled snapshots and manual…

Backup/restore can meet data-loss tolerance in some cases, but RTO of 1 hour is often too aggressive for manual restores.

Trap 2: Pilot light, keeping only minimal infrastructure in the secondary…

Pilot light is cheaper, but RTO of 1 hour may not be achievable if full compute/services must be brought up from near-zero.

Trap 3: Active/active, routing production traffic to both Regions…

Active/active best fits very low RTO and high availability, but it usually costs more than the stated budget constraints.

A
Backup and restore only, relying on scheduled snapshots and manual restores during incidents.
Why wrong: Backup/restore can meet data-loss tolerance in some cases, but RTO of 1 hour is often too aggressive for manual restores.
B
Pilot light, keeping only minimal infrastructure in the secondary Region and starting full services after failover.
Why wrong: Pilot light is cheaper, but RTO of 1 hour may not be achievable if full compute/services must be brought up from near-zero.
C
Warm standby, keeping core infrastructure and a partially provisioned environment ready in the secondary Region with frequent data replication.
Warm standby balances cost and readiness by keeping enough capacity and services running to shorten recovery time while meeting RPO needs.
D
Active/active, routing production traffic to both Regions continuously and accepting dual-region complexity.
Why wrong: Active/active best fits very low RTO and high availability, but it usually costs more than the stated budget constraints.

Question 9easymultiple choice

A team uses an S3 bucket to store important customer-generated exports. They need protection against accidental overwrites and also want copies of the data in another AWS Region for disaster recovery. Which S3 configuration best satisfies both requirements?

Trap 1: Enable S3 lifecycle policies to automatically move objects to…

Lifecycle transitions help with cost and retention, but they do not protect against overwrites or provide cross-Region copies.

Trap 2: Disable all versioning and rely on AWS Backup to restore objects…

Relying on backups may introduce recovery delays and does not give immediate protection from overwrites as versioning does.

Trap 3: Enable S3 Block Public Access and SSE-S3 encryption, without using…

Block Public Access and encryption improve security, but they do not address resilience to overwrites or Region-level failures.

A
Enable S3 lifecycle policies to automatically move objects to Glacier after 30 days only.
Why wrong: Lifecycle transitions help with cost and retention, but they do not protect against overwrites or provide cross-Region copies.
B
Enable S3 versioning and configure Cross-Region Replication to a destination bucket in another Region.
Versioning preserves previous object states against overwrites and deletes, while replication provides an additional Region copy for recovery.
C
Disable all versioning and rely on AWS Backup to restore objects from a scheduled backup window.
Why wrong: Relying on backups may introduce recovery delays and does not give immediate protection from overwrites as versioning does.
D
Enable S3 Block Public Access and SSE-S3 encryption, without using versioning or replication.
Why wrong: Block Public Access and encryption improve security, but they do not address resilience to overwrites or Region-level failures.

Question 10mediummatching

Match the disaster recovery strategy to the recovery posture it best fits for a Regional outage.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Lowest cost option where the environment is rebuilt from backups and hours of downtime are acceptable.

Keep only the critical core running in the secondary Region, then scale out after failover.

Run a scaled-down but functional environment in another Region for faster cutover.

Serve production traffic from more than one Region at the same time for the fastest recovery.

Trap 1: Backup & Restore: RPO seconds, RTO minutes

This option is incorrect because the Backup & Restore strategy fundamentally relies on periodic data backups, which inherently leads to an RPO measured in hours, not seconds. Furthermore, the extensive process of provisioning new infrastructure and restoring data from backups means the RTO is typically 24 hours or more, making a recovery time of minutes unachievable for this method.

Trap 2: Multi-Site Active/Active: RPO hours, RTO 24+ hours

This option is incorrect as the Multi-Site Active/Active strategy is designed for maximum availability and minimal disruption. It employs synchronous data replication and active traffic distribution across multiple regions, which inherently results in a near-zero RPO and RTO. An RPO of hours and an RTO of 24+ hours are characteristic of the least resilient Backup & Restore strategy, not an active/active setup.

A
Backup & Restore: RPO hours, RTO 24+ hours
This strategy relies on periodic backups of data and infrastructure configurations. The Recovery Point Objective (RPO) is typically measured in hours, reflecting the data loss since the last successful backup. The Recovery Time Objective (RTO) is the longest among DR strategies, often exceeding 24 hours, as it involves restoring data, provisioning new infrastructure, and reconfiguring applications from scratch.
B
Pilot Light: RPO minutes, RTO hours
The Pilot Light strategy maintains a minimal, core set of infrastructure components, such as databases, running in a standby region. This allows for a Recovery Point Objective (RPO) in minutes, as critical data can be replicated or frequently synchronized. However, the Recovery Time Objective (RTO) is still measured in hours because the full application environment needs to be provisioned and scaled up before traffic can be redirected.
C
Warm Standby: RPO seconds, RTO minutes
Warm Standby involves maintaining a scaled-down, but fully functional, replica of the production environment in a secondary region. This enables a Recovery Point Objective (RPO) in seconds due to continuous data replication. The Recovery Time Objective (RTO) is significantly reduced to minutes, as it primarily involves scaling up the existing standby resources and redirecting traffic, rather than provisioning new infrastructure.
D
Multi-Site Active/Active: RPO near zero, RTO near zero
This highly resilient strategy operates a full production environment concurrently across multiple geographic regions, with traffic distributed between them. Data is synchronously replicated, achieving a near-zero Recovery Point Objective (RPO) with virtually no data loss. Automated failover mechanisms ensure a near-zero Recovery Time Objective (RTO), as user traffic is instantly routed away from any failing region to the healthy active site.
E
Backup & Restore: RPO seconds, RTO minutes
Why wrong: This option is incorrect because the Backup & Restore strategy fundamentally relies on periodic data backups, which inherently leads to an RPO measured in hours, not seconds. Furthermore, the extensive process of provisioning new infrastructure and restoring data from backups means the RTO is typically 24 hours or more, making a recovery time of minutes unachievable for this method.
F
Multi-Site Active/Active: RPO hours, RTO 24+ hours
Why wrong: This option is incorrect as the Multi-Site Active/Active strategy is designed for maximum availability and minimal disruption. It employs synchronous data replication and active traffic distribution across multiple regions, which inherently results in a near-zero RPO and RTO. An RPO of hours and an RTO of 24+ hours are characteristic of the least resilient Backup & Restore strategy, not an active/active setup.

Question 11mediummulti select

A customer portal must recover from a regional outage within a few hours. The business wants lower ongoing cost than a fully active second Region and does not want to rebuild everything from scratch during the outage. Which two DR patterns best fit that goal? Select two.

Trap 1: Backup and restore

This is the lowest-cost option, but recovery usually requires rebuilding much of the environment after a disaster.

Trap 2: Multi-site active-active

Active-active improves availability, but it runs production in multiple Regions continuously and costs more than the stated goal.

Trap 3: Single-AZ deployment

A single-AZ design is not a regional disaster recovery strategy and does not meet the recovery objective.

A
Backup and restore
Why wrong: This is the lowest-cost option, but recovery usually requires rebuilding much of the environment after a disaster.
B
Pilot light
Pilot light keeps only core components running in the secondary Region, which lowers cost while reducing recovery time.
C
Warm standby
Warm standby keeps a scaled-down but functional environment ready, which shortens recovery while avoiding full active-active cost.
D
Multi-site active-active
Why wrong: Active-active improves availability, but it runs production in multiple Regions continuously and costs more than the stated goal.
E
Single-AZ deployment
Why wrong: A single-AZ design is not a regional disaster recovery strategy and does not meet the recovery objective.

Question 12mediummulti select

A company is designing a disaster recovery plan for a critical application hosted on AWS. The application runs on EC2 instances with data stored in Amazon EBS volumes and Amazon S3. The recovery time objective (RTO) is 15 minutes, and the recovery point objective (RPO) is 1 hour. Which three strategies would help meet these objectives? (Choose three.)

Trap 1: Pre-provision EC2 instances in the disaster recovery region and…

Pre-provisioning and continuously running EC2 instances in a disaster recovery region represents a 'hot standby' strategy. While this approach offers the lowest possible Recovery Time Objective (RTO), it is significantly more expensive due to the ongoing operational costs of maintaining duplicate, fully scaled infrastructure 24/7. For many applications, a more cost-effective strategy like pilot light or warm standby can achieve acceptable RTOs without such high expenditure.

Trap 2: Store Amazon Machine Images (AMIs) in the source region and use AWS…

Storing Amazon Machine Images (AMIs) only in the source region and attempting to copy them via AWS Lambda *after* a disaster introduces significant delays, severely impacting the Recovery Time Objective (RTO). AMIs are region-specific, and for an effective disaster recovery strategy, pre-copying or regularly replicating AMIs to the DR region is essential. Relying on post-disaster replication would prolong recovery efforts unnecessarily.

Trap 3: Set up an AWS Direct Connect link between the primary and DR…

AWS Direct Connect establishes a dedicated, private network connection from an on-premises data center directly to AWS. It is designed for hybrid cloud architectures, not for inter-region connectivity *between* two AWS Regions. Data transfer and communication between different AWS Regions occur over the highly resilient AWS global network, often utilizing services like VPC peering or AWS Transit Gateway, making Direct Connect irrelevant for this specific inter-region DR scenario.

A
Use AWS Backup to create hourly snapshots of EBS volumes and copy them to a different AWS Region.
AWS Backup provides a centralized service to manage backups for various AWS resources, including EBS volumes. Creating hourly snapshots ensures a low Recovery Point Objective (RPO), minimizing potential data loss. Copying these snapshots to a different AWS Region is a fundamental strategy for disaster recovery, enabling the restoration of EBS volumes and associated EC2 instances in an alternate region should the primary region become unavailable.
B
Pre-provision EC2 instances in the disaster recovery region and keep them running 24/7.
Why wrong: Pre-provisioning and continuously running EC2 instances in a disaster recovery region represents a 'hot standby' strategy. While this approach offers the lowest possible Recovery Time Objective (RTO), it is significantly more expensive due to the ongoing operational costs of maintaining duplicate, fully scaled infrastructure 24/7. For many applications, a more cost-effective strategy like pilot light or warm standby can achieve acceptable RTOs without such high expenditure.
C
Replicate critical data to S3 in the disaster recovery region using S3 Cross-Region Replication (CRR).
S3 Cross-Region Replication (CRR) automatically and asynchronously replicates objects between specified S3 buckets in different AWS Regions. This ensures that critical application data stored in S3, such as user-generated content or application assets, is continuously available in the disaster recovery region. CRR is a highly effective and managed service for maintaining data durability and availability, crucial for rapid recovery during a regional outage.
D
Store Amazon Machine Images (AMIs) in the source region and use AWS Lambda to copy them after a disaster.
Why wrong: Storing Amazon Machine Images (AMIs) only in the source region and attempting to copy them via AWS Lambda *after* a disaster introduces significant delays, severely impacting the Recovery Time Objective (RTO). AMIs are region-specific, and for an effective disaster recovery strategy, pre-copying or regularly replicating AMIs to the DR region is essential. Relying on post-disaster replication would prolong recovery efforts unnecessarily.
E
Configure Amazon Route 53 with a failover routing policy and health checks to redirect traffic to the DR region.
Amazon Route 53's failover routing policy, combined with robust health checks, is a critical component for automated disaster recovery. It continuously monitors the health of resources in the primary region and, upon detecting a failure, automatically redirects DNS traffic to the healthy resources in the disaster recovery region. This mechanism ensures high availability and minimizes downtime by transparently directing users to the operational application endpoint.
F
Set up an AWS Direct Connect link between the primary and DR regions for faster data transfer.
Why wrong: AWS Direct Connect establishes a dedicated, private network connection from an on-premises data center directly to AWS. It is designed for hybrid cloud architectures, not for inter-region connectivity *between* two AWS Regions. Data transfer and communication between different AWS Regions occur over the highly resilient AWS global network, often utilizing services like VPC peering or AWS Transit Gateway, making Direct Connect irrelevant for this specific inter-region DR scenario.

Question 13mediummultiple choice

A fintech startup uses AWS to run a web API and a PostgreSQL database. They must meet an RPO of 15 minutes and an RTO of 2 hours for a Region-wide disaster. Budget allows running a small, always-on set of infrastructure in a secondary Region, but not full production capacity. The team wants a DR approach that is regularly testable without large manual effort.

Which disaster recovery strategy is the best fit?

Trap 1: Pilot light: replicate databases and store backups, keep only…

Pilot light can work for some RTO goals, but fully scaling dependencies within 2 hours may be difficult depending on application initialization and data warm-up.

Trap 2: Backup and restore only: rely on daily automated backups and…

Daily backups cannot meet a 15-minute RPO, and restoration time would likely exceed the 2-hour RTO.

Trap 3: Multi-site active-active: run both Regions at full capacity and…

Active-active typically costs more than allowed, and it adds complexity beyond what the budget and requirements describe.

A
Pilot light: replicate databases and store backups, keep only minimal infrastructure in the secondary Region, and scale up fully during failover.
Why wrong: Pilot light can work for some RTO goals, but fully scaling dependencies within 2 hours may be difficult depending on application initialization and data warm-up.
B
Warm standby: keep a scaled-down application environment and database replication active in the secondary Region, using automated failover controls.
Warm standby aligns with moderate RTO requirements by having ready-to-run resources plus continuous replication to meet the RPO target during failover.
C
Backup and restore only: rely on daily automated backups and restore into the secondary Region during an incident.
Why wrong: Daily backups cannot meet a 15-minute RPO, and restoration time would likely exceed the 2-hour RTO.
D
Multi-site active-active: run both Regions at full capacity and route live traffic to both simultaneously.
Why wrong: Active-active typically costs more than allowed, and it adds complexity beyond what the budget and requirements describe.