Examkin

Question

Difficulty: MediumHigh Availability and Disaster Recovery Design

A software-as-a-service (SaaS) company is designing a multi-region disaster recovery (DR) architecture for a telemetry ingestion application. The workload runs in the primary Region (us-west-2) and uses a secondary Region (us-east-1) for disaster recovery. The business requires a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 15 minutes. The architecture uses Amazon Aurora PostgreSQL for data storage, and external client agents send data to Application Load Balancers (ALBs) in both Regions. The configuration must automate failover while maintaining high availability. Which TWO options should the Solutions Architect implement to meet these requirements?

  1. Deploy an Amazon Aurora Global Database with the primary DB cluster in us-west-2 and a secondary DB cluster in us-east-1.Answer
  2. Configure Route 53 with Failover routing records, using an active health check on the primary Application Load Balancer in us-west-2 and a standby record pointing to the Application Load Balancer in us-east-1.Answer
  3. C
    Use Route 53 Latency-based routing to distribute writes across both regions, and rely on Aurora Replica Auto Scaling to scale write capacity dynamically on the secondary DB cluster.
  4. D
    Configure a Route 53 Private Hosted Zone for the telemetry domain name, and associate it with the VPCs in both regions so the external agents can resolve the endpoints.
  5. E
    Configure the private subnets in us-east-1 to route all outbound internet traffic through a single NAT Gateway located in us-west-2 to optimize cross-region data transfer costs.
  6. F
    Create a backup strategy using AWS Backup to take hourly snapshots of the database in us-west-2 and copy them to us-east-1, restoring the database in the secondary region during a failover event.

Answer

Deploy an Amazon Aurora Global Database across the primary and secondary regions, and configure Route 53 Failover routing records with active health checks to redirect telemetry traffic.
To satisfy the RPO of 5 minutes and RTO of 15 minutes, the solution must utilize continuous data replication and automated DNS failover. Amazon Aurora Global Database provides sub-second replication lag, meeting the RPO, and can be promoted rapidly. Route 53 Failover routing records detect primary endpoint issues via health checks and redirect telemetry traffic to the secondary Region dynamically to satisfy the RTO.

Step-by-Step Solution

1
Address the database RPO by deploying Amazon Aurora Global Database.
Establishes sub-second cross-region replication from the primary cluster in us-west-2 to the secondary cluster in us-east-1, satisfying the 5-minute RPO requirement.
Traditional backup and restore methods fail to meet the RPO, requiring continuous asynchronous database replication.
2
Address the routing RTO by implementing Route 53 Failover routing.
Directs client traffic to the primary ALB in us-west-2 during normal operations, and automatically shifts traffic to the secondary ALB in us-east-1 if health checks fail.
This automates traffic redirection without manual DNS intervention, completing the failover within the 15-minute RTO.

Key Concept

Disaster recovery planning using Aurora Global Database for sub-minute RPO and Route 53 Failover routing for automated traffic redirection.
Rate this question

Topics

High Availability and Disaster Recovery Design

More questions from this topic