Examkin

Soru

Zorluk: Çok zorMulti-AZ, Multi-Region Architectures and Disaster Recovery (DR)

A logistics company hosts a fleet tracking application on AWS. The application runs on Amazon ECS Fargate tasks behind an Application Load Balancer (ALB) in the primary Region (us-east-1). The database is an Amazon RDS for PostgreSQL Multi-AZ DB instance. The company requires a disaster recovery (DR) strategy in a secondary Region (us-west-2) with a Recovery Time Objective (RTO) of less than 1515 minutes and a Recovery Point Objective (RPO) of less than 55 minutes. The solution must minimize ongoing operational costs. Which two actions should a solutions architect take to meet these requirements?

  1. Create an Amazon RDS cross-region read replica in the secondary Region. During a failover, promote the read replica to a standalone DB instance.Cevap
  2. Deploy the ECS service in the secondary Region with a minimum desired task count of 11. Configure an Application Load Balancer in the secondary Region, and set up Amazon Route 53 active-passive failover routing with health checks.Cevap
  3. C
    Configure the RDS DB instance to replicate synchronously to the secondary Region using Multi-AZ deployment.
  4. D
    Configure automated DB snapshots and copy them to the secondary Region every 1212 hours. In a disaster, restore the database from the copied snapshot.
  5. E
    Use Route 53 Latency routing policy to route user traffic to both regions simultaneously, allowing clients to automatically direct requests to the secondary Region if the primary Region becomes unresponsive.

Cevap

The correct options are creating an Amazon RDS cross-region read replica in the secondary Region (promoting it during failover), and deploying the ECS service in the secondary Region with a minimum task count of one along with an Application Load Balancer and Route 53 active-passive failover routing with health checks.
The correct actions combine an Amazon RDS cross-region read replica in the secondary Region with a Warm Standby ECS deployment and Route 53 active-passive failover. Creating a cross-region read replica satisfies the RPO of less than 55 minutes since replication is continuous and asynchronous, and promoting the replica to a standalone database takes only a few minutes. Running a single Fargate task in the secondary Region keeps compute costs minimal while ensuring that the infrastructure is ready to receive traffic immediately upon a DNS failover, satisfying the RTO of less than 1515 minutes.

Adım Adım Çözüm

1
Analyze the RPO requirement of less than 55 minutes.
Identify that data replication to the secondary Region must be near real-time. Since the primary database is Amazon RDS for PostgreSQL, an asynchronous cross-region read replica is the most appropriate option to keep replication lag within seconds/minutes while keeping costs low compared to active-active architectures.
Ensures that data loss is minimized to meet the RPO threshold.
2
Analyze the RTO requirement of less than 1515 minutes.
Determine that compute capacity must be pre-provisioned or quickly deployable, and failover routing must be automated. Running a scaled-down ECS Fargate task (desired count of 11) represents a Warm Standby strategy that allows traffic to be served immediately upon DNS failover, avoiding the startup delays of deploying infrastructure from scratch.
Allows the application to recover and start serving traffic within the RTO budget.
3
Evaluate the database replication options.
Rule out RDS Multi-AZ for cross-region replication since Multi-AZ is strictly single-region. Rule out periodic snapshots since 1212-hour snapshot copying does not meet the 55-minute RPO and restoration takes too long for the 1515-minute RTO.
Eliminates database options that violate either the synchronous cross-region technical limitation or RPO/RTO constraints.
4
Evaluate routing and failover options.
Rule out latency-based routing without active health checks, as it does not perform automated failover during a regional outage.
Eliminates incorrect DNS configurations that fail to provide high availability.

Anahtar Kavram

Disaster recovery (DR) strategies (specifically Warm Standby vs. Pilot Light) require aligning AWS database replication (like RDS cross-region replicas) and routing mechanisms (like Route 53 failover routing) to meet specific RTO and RPO objectives at the lowest cost.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Multi-AZ, Multi-Region Architectures and Disaster Recovery (DR)

Bu konudan daha fazla soru