Examkin

Question

Difficulty: HardHigh Availability and Disaster Recovery Design

A digital health enterprise is designing a high-availability patient telemetry ingestion platform across two AWS Regions: us-east-1 (primary) and us-west-2 (secondary). The platform must ingest real-time data from medical IoT devices.

The requirements are:
- High availability for the public ingestion API endpoints. In the event of a primary region outage, traffic must automatically fail over to the secondary region. The public DNS routing policy must evaluate endpoint health before routing.
- The database layer requires a Recovery Time Objective (RTO) of less than 10 minutes and a Recovery Point Objective (RPO) of less than 1 minute.
- Outbound internet connectivity for ingestion servers running in private subnets of multiple Availability Zones in each region must be highly resilient against Availability Zone failures.
- Internal microservices in both regions must resolve the private domain internal-telemetry.local to regional VPC endpoints locally without routing traffic over the public internet.

Which two of the following configuration options should the solutions architect select to meet these requirements? (Select two.)

  1. Configure Amazon Route 53 with an Active-Passive Failover routing policy for the public domain using Application Load Balancer health checks. Associate the private hosted zone internal-telemetry.local with the VPCs in both us-east-1 and us-west-2.Answer
  2. Set up an Amazon Aurora Global Database with the primary database cluster in us-east-1 and a secondary database cluster in us-west-2. Deploy a NAT Gateway in each Availability Zone containing private subnets in both regions.Answer
  3. C
    Configure Amazon Route 53 with an Active-Passive Failover routing policy. To handle private DNS resolution, create the private hosted zone internal-telemetry.local in us-east-1 and associate it only with the us-east-1 VPC, allowing the us-west-2 VPC resources to resolve it via default public DNS recursion.
  4. D
    Deploy the application servers in private subnets across multiple Availability Zones in each region. In each region, deploy a single NAT Gateway in a single public subnet to handle all outbound egress traffic for all private subnets across all Availability Zones.
  5. E
    To achieve the database RPO and RTO requirements, deploy an RDS PostgreSQL DB instance in us-east-1 with a Multi-AZ standby deployment. Direct read-heavy analytics workloads in the secondary region to query the standby instance directly to offload the primary database.

Answer

The correct configurations are to set up Route 53 Active-Passive Failover for the public endpoint, associate the private hosted zone with the VPCs in both regions, deploy Aurora Global Database for database replication, and provision a NAT Gateway per Availability Zone in each region.
The configuration of Route 53 with an Active-Passive Failover routing policy utilizing Application Load Balancer health checks ensures automatic failover in the event of a regional outage. Associating the private hosted zone with the VPCs in both regions ensures that DNS queries for the private domain resolve locally in both environments. At the database layer, Amazon Aurora Global Database uses storage-level physical replication to replicate data to the secondary region with an RPO of less than 1 minute and allows promotion in less than 10 minutes. Deploying a NAT Gateway in each Availability Zone ensures that outbound egress traffic remains resilient to Availability Zone outages.

Step-by-Step Solution

1
Analyze the database HA/DR requirements (RTO < 10 mins, RPO < 1 min).
Determine that Amazon Aurora Global Database satisfies these requirements via storage-level physical replication.
It provides cross-region RPO of less than 1 minute and can be promoted to a primary cluster in less than 10 minutes.
2
Evaluate the DNS resolution requirement for the private hosted zone across multiple regions.
Identify that a Route 53 Private Hosted Zone must be associated with the VPCs of both regions.
This allows resources in both regions to resolve the private DNS names locally without routing over the public internet.
3
Analyze outbound connectivity resiliency constraints.
Identify that a NAT Gateway must be deployed in each Availability Zone containing private subnets.
This avoids a single point of failure at the Availability Zone level, ensuring outbound traffic is highly available.

Key Concept

Designing highly available, resilient, and multi-region disaster recovery systems using Route 53 failover, cross-region VPC DNS association, and Aurora Global Databases.
Rate this question

Topics

High Availability and Disaster Recovery Design

More questions from this topic