Soru

Zorluk: Çok zorDisaster Recovery Strategies

A financial services firm runs a critical transaction processing application on AWS. The application tier consists of stateless Amazon EC2 instances in an Auto Scaling group, while the data tier uses an Amazon Aurora PostgreSQL database. Transaction receipts are stored in an Amazon S3 bucket. A SysOps Administrator must establish a cross-region disaster recovery (DR) strategy that achieves a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 1 minute. The strategy must also minimize baseline infrastructure costs. Which of the following architectures meets these requirements?

  1. Configure an Amazon Aurora Global Database with the primary cluster in the active region and a secondary cluster in the recovery region. Enable versioning on both the source and recovery S3 buckets, and configure S3 Cross-Region Replication (CRR). Store AWS CloudFormation templates in the recovery region to provision the application tier with the Auto Scaling group capacity set to 0. Use Amazon Route 53 Application Recovery Controller (Route 53 ARC) routing controls to redirect traffic and programmatically scale up the Auto Scaling group during failover.Cevap
  2. B
    Configure daily cross-region copies of Amazon Aurora snapshots using AWS Backup. Enable versioning and configure S3 Cross-Region Replication (CRR) on the transaction receipts bucket. In the recovery region, maintain a pre-deployed Auto Scaling group with capacity set to 0. During a disaster, restore the Aurora database from the latest cross-region snapshot and update the Auto Scaling group capacity.
  3. C
    Configure Amazon S3 Cross-Region Replication (CRR) from the primary bucket to a new bucket in the recovery region without enabling versioning on the destination bucket. Create a cross-region Aurora Read Replica in the recovery region, and set up a Route 53 Failover routing policy pointing directly to the replica endpoint to automate database failover. Deploy the application tier via AWS CloudFormation with the Auto Scaling group capacity set to 0.
  4. D
    Configure an Amazon Aurora Global Database with a secondary cluster in the recovery region. Enable versioning on the source and recovery S3 buckets and configure S3 Cross-Region Replication. Deploy a fully scaled-out Auto Scaling group in the recovery region matching the primary region's capacity, and use a Route 53 Latency routing policy with health checks to route traffic in an active-active configuration.

Cevap

Configure an Amazon Aurora Global Database with the primary cluster in the active region and a secondary cluster in the recovery region. Enable versioning on both the source and recovery S3 buckets, and configure S3 Cross-Region Replication (CRR). Store AWS CloudFormation templates in the recovery region to provision the application tier with the Auto Scaling group capacity set to 0. Use Amazon Route 53 Application Recovery Controller (Route 53 ARC) routing controls to redirect traffic and programmatically scale up the Auto Scaling group during failover.
The correct architecture uses a Pilot Light strategy. Amazon Aurora Global Database provides sub-second replication (meeting the 1-minute RPO) and can be promoted to a primary cluster in less than a minute. S3 Cross-Region Replication, which requires versioning on both source and destination buckets, replicates transaction receipts in near real-time. To minimize baseline costs, the application tier's Auto Scaling group is kept at 0 capacity in the recovery region, which can easily be scaled up within the 15-minute RTO during a failover event managed by Route 53 Application Recovery Controller.

Adım Adım Çözüm

1
Evaluate the RPO requirement of less than 1 minute.
Identify that data replication mechanisms must be near real-time. Amazon Aurora Global Database provides sub-second replication, and S3 Cross-Region Replication (CRR) replicates objects within seconds, both meeting the RPO.
Traditional backup restore methods using daily snapshots cannot achieve an RPO of less than 1 minute.
2
Evaluate the RTO requirement of less than 15 minutes while minimizing cost.
Determine that keeping the application tier at zero capacity (Auto Scaling group capacity set to 0) in the recovery region satisfies the cost-minimization constraint while allowing enough time (under 15 minutes) to scale up compute instances using CloudFormation during a disaster.
Maintaining active compute resources in the secondary region (Warm Standby or Multi-site) is unnecessary and increases baseline costs.
3
Verify prerequisites for the required services.
Confirm that S3 Cross-Region Replication requires versioning to be enabled on both the source and destination buckets, and that Aurora Global Databases support fast promotion to primary status.
Omitting versioning on either bucket prevents CRR from being configured, and standard Aurora replica promotion requires manual intervention or complex custom scripting compared to Global Database promotion.
4
Identify the routing mechanism for failover.
Use Route 53 Application Recovery Controller (ARC) routing controls to systematically fail over traffic to the recovery region.
Latency-based active-active routing is not suitable for a pilot light disaster recovery failover.

Anahtar Kavram

Disaster Recovery Strategies (Pilot Light)
Tahmini Süre:3m 0s
Bu soruyu puanla