Examkin

Soru

Zorluk: OrtaHigh Availability and Disaster Recovery Design

A digital marketing agency is designing a disaster recovery (DR) architecture for its centralized digital asset management platform. The primary production environment runs in the us-east-1 Region, and the DR environment will be deployed in the us-west-2 Region. The architecture must support a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. The design must also minimize ongoing compute costs in the secondary Region during normal operations. The platform's database tier uses an Amazon Aurora PostgreSQL DB cluster.

Which combination of actions should the solutions architect take to meet these requirements? (Select TWO.)

  1. Configure Amazon Aurora Global Database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2. In us-west-2, provision a single Aurora Replica of the same instance class as the primary writer to serve as the failover target.Cevap
  2. Configure Route 53 with a Failover routing policy. Create a primary record pointing to the us-east-1 Application Load Balancer (ALB) and associate it with a Route 53 health check, and create a secondary record pointing to the us-west-2 ALB.Cevap
  3. C
    Configure Route 53 with a Latency routing policy. Associate health checks with the Application Load Balancers (ALBs) in both Regions to dynamically route users to the secondary Region if latency increases or an outage occurs.
  4. D
    Deploy a single NAT Gateway in us-east-1 within a single Availability Zone, and configure the route tables of private subnets in all Availability Zones to route outbound internet traffic through this NAT Gateway to reduce idle resource costs.
  5. E
    Configure Aurora Auto Scaling on the secondary DB cluster in us-west-2 with a target metric to dynamically upgrade the instance class of the standby database from a cost-optimized db.t3.medium to the primary instance class during a failover event.

Cevap

The combination of configuring Amazon Aurora Global Database with a standby replica of the same instance class in the secondary Region, and using Amazon Route 53 Failover routing policy with health checks to route traffic between the Regions.
Configuring Amazon Aurora Global Database provides cross-region replication with a typical replication lag of less than one second, which satisfies the 1-minute RPO. Provisioning a replica of the same instance class in the secondary Region ensures that when the cluster is promoted to primary, it can immediately handle the production load without performance degradation. For DNS routing, configuring a Route 53 Failover routing policy with health checks creates an active-passive setup. This directs all production traffic to the primary Region (us-east-1) under normal operations and automatically redirects users to the secondary Region (us-west-2) during an outage, meeting the 15-minute RTO while keeping the secondary Region's compute resources idle or scaled down.

Adım Adım Çözüm

1
Analyze the database replication mechanism and instance configuration for disaster recovery.
Amazon Aurora Global Database provides sub-second cross-region replication, meeting the 1-minute RPO. The secondary Region's instance must be the same size as the primary to handle the write workload immediately upon failover, satisfying the 15-minute RTO.
Choosing the correct replication technology and sizing ensures database integrity and performance standards are met during failover.
2
Select the appropriate Route 53 routing policy for an active-passive disaster recovery configuration.
A Route 53 Failover routing policy is chosen, directing all traffic to us-east-1 under normal operations and failing over to us-west-2 when health checks fail.
This policy ensures that the secondary Region's compute resources remain idle/scaled down during normal operations, minimizing running compute costs.
3
Verify high availability constraints in the primary Region and check for scaling limitations.
Avoid single points of failure like a single NAT Gateway in the primary Region, and avoid invalid configurations like using Aurora Auto Scaling for vertical instance class upgrades.
This guarantees that the primary infrastructure is highly available and that the disaster recovery failover mechanism is technically viable.

Anahtar Kavram

Designing active-passive multi-region architectures with low RTO/RPO using Route 53 Failover routing and Aurora Global Database.
Bu soruyu puanla

Konular

High Availability and Disaster Recovery Design

Bu konudan daha fazla soru