Which solution will meet these requirements?
Deploy the application on Amazon EC2 instances. Use Amazon Route 53 to forward requests to the EC2 instances. Use Amazon DynamoDB to save the authenticated connection details.
Deploy the application on Amazon EC2 instances in an Auto Scaling group. Use an internet-facing Application Load Balancer to handle requests. Use Amazon DynamoDB to save the authenticated connection details.
Deploy the application on Amazon EC2 instances in an Auto Scaling group. Use an internet-facing Application Load Balancer on the front end. Use EC2 instances to save the authenticated connection details.
Deploy the application on Amazon EC2 instances in an Auto Scaling group. Use an internet-facing Application Load Balancer on the front end. Use EC2 instances hosting a MySQL database to save the authenticated connection details.
Explanations:
While using Amazon Route 53 can distribute requests, it does not ensure high availability or fault tolerance by itself. Also, saving authenticated connection details in DynamoDB without a load balancer may lead to connection issues during instance failures.
This option includes an Auto Scaling group, which provides redundancy and fault tolerance by automatically replacing unhealthy instances. An Application Load Balancer can distribute traffic and maintain connectivity for users, while DynamoDB provides a reliable, highly available storage solution for connection details.
This option lacks an external load balancer; using EC2 instances to save authenticated connection details directly is not optimal for high availability and can lead to single points of failure.
While this option does have an Auto Scaling group and a load balancer, using EC2 instances with a MySQL database for saving authenticated connection details creates a single point of failure. MySQL does not inherently provide high availability unless configured with additional components, such as replication or clustering.