Q35 — AWS SAA-C03 Ch.5

Question 35 of 65 | ← Chapter 5

Q335. A company hosts its application in the AWS Cloud. The application runs on Amazon EC2 instances behind an Elastic Load Balancer in an Auto Scaling group and with an Amazon DynamoDB table. The company wants to ensure the application can be made available in another AWS Region with minimal downtime. What should a solutions architect do to meet these requirements with the L EAST amount of downtime?

Correct Answer: A. Create an Auto Scaling group and a load balancer in the disaster recovery Region. Configure the DynamoDB table as a global tablc. Configure DNS failover to point to the now disaster recovery Region's load balancer.

Explanation

To ensure the application can be made available in another AWS Region with minimal downtime, the solutions architect should create a disaster recovery environment in the new region and configure DNS failover to point to the disaster recovery load balancer. Option A is the correct choice as it suggests creating an Auto Scaling group and load balancer in the disaster recovery Region and configuring the DynamoDB table as a global table. Global tables enable automatic multi-region replication, making it easier to provide low-latency data access to users globally. By configuring DNS failover to point to the new disaster recovery region's load balancer, traffic can be redirected to the disaster recovery environment with minimal downtime. Therefore, option A is the most appropriate answer. Option B is not suitable because it suggests creating a CloudFormation template to create EC2 instances, load balancers, and DynamoDB tables to be executed when needed instead of having a pre-configured environment to minimize downtime.Option C creates EC2 instances and a load balancer but does not include a disaster recovery strategy, which is the primary requirement.Option D suggests creating an Amazon CloudWatch alarm to trigger an AWS Lambda function that updates Amazon Route 53 pointing to the disaster recovery load balancer, which will take time to update DNS records. This option may cause some downtime, which violates the requirement of minimal downtime.Let's think, using CloudFormation nothing is created until necessary so how to configure route 53 to point to something that doesn't still exist? Then how much time CloudFormation take time to create and fullfill the DynamoDB (especially if the db is big)?. This point to rule out B & C.D is clearly wrong.A-- make sense because infrastructure is already ready, only to switch dns. You will not need to make any effort if some disaster happens. The system will automatically handle everything without launching CF templates (manually or automatically). Just curious, you as an architect, how are you going without any downtime to understand that CF template should be run? Sitting in front of the monitor and refreshing the web page with AWS console? Even in your case you will have to wait for failing health checks (or other triggers). But with option "A" if health checks are failed system will switch to failover configuration and that's it. No need to wait for resources being deployed