Examkin

Question

Difficulty: MediumHigh Availability and Disaster Recovery Design

A software-as-a-service (SaaS) company is designing a highly available, multi-region web application on AWS with a primary deployment in us-east-1 and a disaster recovery (DR) site in us-west-2. The application relies on an Amazon Aurora MySQL database and must communicate with external payment APIs. The business requirements specify a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 22 minutes. The design must ensure high availability within each Region and minimize single points of failure. Which two actions should a solutions architect take to meet these requirements?

  1. Create an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, utilizing storage-based physical replication.Answer
  2. Deploy a NAT Gateway in each Availability Zone's public subnet within both Regions, and configure the route tables of the private subnets in each Availability Zone to route outbound traffic through their respective local NAT Gateway.Answer
  3. C
    Deploy a single NAT Gateway in a single Availability Zone for each Region, and configure the route tables of all private subnets in that Region to point to this common gateway.
  4. D
    Configure AWS Backup to perform daily database backups in us-east-1 and copy them to us-west-2, restoring the database from the copied snapshot during a failover event.
  5. E
    Deploy the database using Amazon RDS for MySQL Multi-AZ with the primary in us-east-1 and the standby instance in us-west-2, and configure the standby instance to serve read traffic during normal operations.

Answer

Create an Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2, and deploy a NAT Gateway in each Availability Zone's public subnet within both Regions, configuring the private route tables accordingly.
Implementing an Amazon Aurora Global Database meets the RPO of 22 minutes because its storage-based cross-region replication lag is typically under a second, and a failover can be completed quickly to meet the RTO. Deploying a NAT Gateway in each public subnet per Availability Zone ensures outbound high availability, preventing a single Availability Zone outage from dropping all outbound connections.

Step-by-Step Solution

1
Evaluate the database tier against the RTO of 1515 minutes and RPO of 22 minutes.
Identify that cross-region storage replication via Amazon Aurora Global Database is required to keep replication lag under a second, meeting the RPO, and allowing rapid failover within the RTO.
Traditional snapshot copies or standard backup restorations take too long and result in too much data loss to satisfy the RTO and RPO requirements.
2
Design the outbound connectivity architecture for external API access.
Deploy a NAT Gateway in each Availability Zone's public subnet and point local private subnets to their respective zone's gateway.
A single NAT Gateway per Region creates a single point of failure. Redundant NAT Gateways ensure high availability in the event of an Availability Zone outage.

Key Concept

Designing multi-region disaster recovery using Amazon Aurora Global Database while ensuring local Availability Zone redundancy for network address translation.
Rate this question

Topics

High Availability and Disaster Recovery Design

More questions from this topic