Which solution should a solutions architect recommend that has the LEAST amount of downtime?
Configure an Amazon Route 53 failover record. Run application servers on Amazon EC2 instances behind an Application Load Balancer in an Auto Scaling group. Set up AWS Storage Gateway with stored volumes to back up data to Amazon S3.
Configure an Amazon Route 53 failover record. Execute an AWS CloudFormation template from a script to create Amazon EC2 instances behind an Application Load Balancer. Set up AWS Storage Gateway with stored volumes to back up data to Amazon S3.
Configure an Amazon Route 53 failover record. Set up an AWS Direct Connect connection between a VPC and the data center. Run application servers on Amazon EC2 in an Auto Scaling group. Run an AWS Lambda function to execute an AWS CloudFormation template to create an Application Load Balancer.
Configure an Amazon Route 53 failover record. Run an AWS Lambda function to execute an AWS CloudFormation template to launch two Amazon EC2 instances. Set up AWS Storage Gateway with stored volumes to back up data to Amazon S3. Set up an AWS Direct Connect connection between a VPC and the data center.
Explanations:
This option provides the best solution with minimal downtime. Amazon Route 53 failover helps direct traffic to AWS during on-premises failures. The use of EC2 instances in an Auto Scaling group behind an ALB ensures high availability. AWS Storage Gateway with stored volumes synchronizes data between AWS and on-premises, maintaining data uniformity.
This option requires executing a CloudFormation template each time the failover occurs, causing delays and downtime. Although AWS Storage Gateway is included, it doesn’t match the real-time readiness provided by Auto Scaling and Route 53 failover as in Option A.
The setup is complex and adds unnecessary components. AWS Direct Connect is not needed for this use case, as failover can be achieved without a persistent, private connection. AWS Lambda to execute CloudFormation adds delay in launching resources.
This option includes AWS Direct Connect, which is not required here and increases costs. Using Lambda to execute CloudFormation for EC2 instances adds downtime during failover, reducing the solution’s effectiveness for quick recovery.
I structure that the answer is:
Configure an Amazon Route 53 failover record. Run application servers on Amazon EC2 instances behind an Application Load Balancer in an Auto Scaling group. Set up AWS Storage Gateway with stored volumes to back up data to Amazon S3.