Examkin

Soru

Zorluk: OrtaEnhancing Reliability and Disaster Recovery

An enterprise operates a citizen portal application using a multi-tier microservices architecture in the us-east-1 Region. The web tier consists of Amazon ECS tasks running on AWS Fargate behind an Application Load Balancer (ALB). The application logic runs on AWS Lambda behind Amazon API Gateway. The data tier utilizes Amazon DynamoDB. The entire environment is provisioned using AWS CloudFormation. To enhance the disaster recovery (DR) posture, the enterprise wants to establish a warm standby architecture in the us-west-2 Region with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. Which combination of actions should the Solutions Architect take to meet these requirements? (Select TWO.)

  1. Convert the Amazon DynamoDB tables into DynamoDB global tables to enable continuous replication between the primary and secondary regions.Cevap
  2. Pre-deploy the web and application infrastructure in the secondary region with the ECS service scaled to minimum capacity, and configure Amazon Route 53 active-passive failover routing linked to health checks.Cevap
  3. C
    Set up a daily backup schedule for DynamoDB tables using AWS Backup, copy the backups to the secondary region, and implement an automated AWS Lambda function to restore the tables during failover.
  4. D
    Configure Route 53 failover records pointing to the ALBs in both regions without health checks to prevent false positive failovers, and plan to manually update the routing weights during a regional outage.
  5. E
    Deploy the ECS Fargate tasks in private subnets in the secondary region, and route all outbound internet traffic through a single NAT Gateway in one Availability Zone to minimize standby operational costs.

Cevap

Convert the DynamoDB tables to DynamoDB global tables for replication, and pre-deploy the application tier in the secondary region at minimum capacity while configuring Route 53 active-passive failover with health checks.
To meet the RPO of 5 minutes, DynamoDB global tables are required as they provide sub-second replication latency across AWS regions. To meet the RTO of 15 minutes, a warm standby strategy must have the infrastructure pre-deployed and running at minimal scale in the secondary region, combined with automated Route 53 active-passive failover routing. The failover routing must be linked to health checks to enable automated diversion of traffic to the standby region in the event of an outage.

Adım Adım Çözüm

1
Address the Recovery Point Objective (RPO) constraint of 5 minutes by choosing an appropriate replication mechanism for the database layer.
Identify that DynamoDB global tables replicate data across regions with sub-second replication latency, satisfying the 5-minute RPO.
Standard backup and restore methods or manual synchronization cannot guarantee data freshness under 5 minutes during a disaster.
2
Address the Recovery Time Objective (RTO) constraint of 15 minutes by choosing a deployment pattern and routing mechanism.
Select a warm standby pattern where critical infrastructure is already running at minimal scale in the secondary region, and configure automated DNS failover using Route 53 active-passive failover routing policies associated with application health checks.
Cold standby or manual failover steps cannot consistently recover containerized services and update DNS records within 15 minutes.
3
Evaluate and eliminate options that violate the reliability design principles or the specified RTO/RPO thresholds.
Eliminate the options proposing daily backups (violates RPO/RTO), manual Route 53 failover without health checks (violates RTO), and a single NAT Gateway configuration (violates multi-AZ redundancy principles).
Each of these distractors introduces architectural defects or fails the service level agreements required by the business.

Anahtar Kavram

Designing multi-region disaster recovery architectures with tight RPO and RTO constraints requires automated database replication (such as DynamoDB global tables) and pre-deployed compute tiers with automated DNS routing failover (such as Route 53 health-checked active-passive failover) while maintaining high availability best practices.
Bu soruyu puanla

Konular

Enhancing Reliability and Disaster Recovery