An enterprise runs a high-volume payment processing application in a single AWS account in the us-east-1 Region. The system uses an Amazon Elastic Kubernetes Service (EKS) cluster for compute and an Amazon DynamoDB table for transaction states. The application has suffered outages due to regional service issues and internet routing degradation. To improve availability, the solutions architect must redesign the architecture to implement a multi-region Active-Passive disaster recovery (DR) strategy across us-east-1 and us-west-2. The solution must achieve a Recovery Time Objective (RTO) of less than 5 minutes and a Recovery Point Objective (RPO) of less than 1 minute. Which of the following actions should the solutions architect take to meet these reliability and disaster recovery requirements? (Select TWO.)
- Convert the existing DynamoDB table to a global table by adding a replica in the us-west-2 Region, and provision Route 53 Application Recovery Controller (ARC) routing controls linked to Route 53 failover routing records pointing to the Application Load Balancers in each region.Cevap
- Deploy a duplicate EKS cluster in the us-west-2 Region with pre-provisioned worker nodes matching the baseline capacity of the primary region, and ensure the application deployment pipeline deploys container images and configuration maps to both EKS clusters to maintain configuration alignment.Cevap
- CConfigure a pilot light DR strategy by maintaining a backup EKS cluster in the us-west-2 Region with an Auto Scaling Group size set to zero, and use an AWS Lambda function triggered by Route 53 DNS failover events to bootstrap the EKS nodes and pull the container images when an outage is detected in the us-east-1 Region.
- DSet up Route 53 active-passive failover using standard Route 53 HTTP/HTTPS health checks directly targeting the Application Load Balancers in both regions to automate DNS failover without manual intervention during a regional control plane event.
- EEstablish an AWS Transit Gateway in both regions to route all outbound egress payment traffic from the us-west-2 EKS cluster through a single NAT Gateway in the us-east-1 Region to preserve static IP addresses for external payment providers.