Soru

Zorluk: OrtaHigh Availability and Disaster Recovery Design

A global digital publishing company is designing a high-availability and disaster recovery architecture for its core content management application on AWS. The application runs on Amazon EC2 instances in private subnets across multiple Availability Zones in the `us-east-1` Region. The application requires outbound internet access to synchronize syndication feeds with external partners. The database layer uses Amazon Aurora PostgreSQL. The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes, with a disaster recovery target in the `us-west-2` Region. The solutions architect must also ensure that the architecture has no single points of failure within a Region. Which two options should the Solutions Architect implement to meet these requirements?

  1. Set up an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2` for database replication. Use Amazon Route 53 with active-passive failover routing and associated health checks to manage DNS resolution for the application's public endpoint.Cevap
  2. Deploy a NAT Gateway in each public Availability Zone in both Regions, and configure the route tables of the private subnets to route internet-bound traffic through the local NAT Gateway in their respective Availability Zone.Cevap
  3. C
    Implement a Backup and Restore strategy by scheduling daily Aurora snapshots, copying them to `us-west-2`, and restoring the database cluster in `us-west-2` upon disaster declaration to minimize active database running costs.
  4. D
    Deploy a single NAT Gateway in one public Availability Zone in each Region, and point the route tables of all private subnets across all Availability Zones to this single NAT Gateway to reduce deployment costs.
  5. E
    Configure a Route 53 Private Hosted Zone for database endpoint resolution in the primary VPC, and establish a cross-region VPC peering connection to allow the secondary VPC to resolve the endpoint without associating the Private Hosted Zone with the secondary VPC.
  6. F
    Use an Amazon RDS for PostgreSQL Multi-AZ deployment in the primary Region, and configure the application to route read-intensive syndication queries to the standby instance in the secondary Availability Zone to scale read capacity.

Cevap

Setting up Amazon Aurora Global Database with Route 53 active-passive failover, and deploying a NAT Gateway in each public Availability Zone in both Regions.
To satisfy the RTO of 15 minutes and RPO of 5 minutes, database replication must be low-latency and failover must be rapid. Amazon Aurora Global Database uses asynchronous replication with latency of less than one second, satisfying the RPO. Promoting the secondary cluster in the recovery region takes less than a minute, satisfying the RTO. Redirection of public traffic is managed dynamically by Amazon Route 53 active-passive failover routing policies using health checks. Furthermore, to avoid single points of failure within a Region for outbound content syndication, NAT Gateways must be deployed in each Availability Zone where the application operates.

Adım Adım Çözüm

1
Evaluate the disaster recovery requirements (RTO of 15 minutes and RPO of 5 minutes) against the database replication strategies.
Identify that Aurora Global Database is required due to sub-second replication latency and sub-minute recovery time, whereas backup-and-restore strategies fail these requirements.
Ensures the database layer architecture aligns with recovery objectives.
2
Determine the routing mechanism to handle regional failover for the public application endpoint.
Select Amazon Route 53 active-passive failover routing policy combined with health checks.
Enables automatic routing of user traffic to the backup region when the primary region is determined to be unhealthy.
3
Address internal high availability requirements for outbound internet access across multiple Availability Zones.
Deploy a NAT Gateway in each public Availability Zone and configure subnet routing accordingly.
Eliminates the single point of failure that a single NAT Gateway would introduce across zones.

Anahtar Kavram

High Availability and Disaster Recovery Design
Bu soruyu puanla