A company has hired you to assist with the migration of an interactive website that allows registered users to rate local restaurants. Updates to the ratings are displayed on the home page, and ratings are updated in real-time. Although the website is not very popular today, the company anticipates that it will grow over the next few weeks. They also want to ensure that the website remains highly available. The current architecture consists of a single Windows server 2016 web server and a MySQL database on Linux. Both reside inside on an on-premises hypervisor. What would be the most efficient and optimal way to point the application to AWS, ensuring high performance and availability?

Answer options:

A.Configure Auto Scaling to launch one Windows Server 2016 instance each in us-west-1a and us-west-1b. Copy the web files from an on-premises web server to each Amazon EC2 web server, using Amazon S3 as the repository. Launch a Multi-AZ MySQL Amazon RDS Instance in us-west-1a and us-west-1b. Import the data into Amazon RDS from the latest MySQL backup. Create an elastic load balancer (ELB) to front your web servers. Use Amazon Route53 and create an alias ( Type: A-IP4 Address ) record pointing to the ELB.B.Export web files to an Amazon S3 bucket in us-west-1. Run the website directly out of Amazon S3. Launch a Multi-AZ MySQL Amazon RDS instance in us-west-1a. Import the data into Amazon RDS from the latest MySQL backup. Use Route 53 and create an alias record pointing to the elastic load balancer.
C.Use AWS VM Import/Export to create an Amazon EC2 AMI of the webserver. Configure Auto Scaling to launch one web server in us-west-1a and one in us-west-1b. Create an Elastic Load Balancer to distribute the traffic. Launch a Multi-AZ MySQL Amazon RDS instance in us-west-1. Import the data Into Amazon RDS from the latest MySQL backup. Use Amazon Route 53 and create an Alias record pointing to the Elastic Load Balancer.
D.Use AWS VM Import/Export to create an Amazon EC2 AMI of the webserver. Configure Auto Scaling to launch one webserver in us-west-1a and one in us-west-1b. Launch a Multi-AZ MySQL Amazon RDS instance in us-west-1. Import the data into Amazon RDS from the latest MySQL backup. Use Amazon Route 53 to create a hosted zone and point an A record to the EC2 IP addresses.

Answer – C
The main consideration in the question is that the architecture should be highly available with high performance.
Option A is incorrect because (a) EC2 servers can communicate with S3 for the web files, and (b) Auto Scaling of webservers and the setup of Multi-AZ RDS instance, as well as the Route 53 alias record with ELB provides high availability. However, this option does not mention the use of VM Import/Export that would provide an "optimal" solution to the given requirement.
Option B is incorrect because this is an interactive website and S3 is suitable for static websites.
Option C is CORRECT because Route 53 is used to create an Alias record to point to an ELB DNS. Using a VM Import/Export would be the most "optimal" solution as given in the requirement.
Option D is incorrect because, in Route 53, you should create an Alias record pointing to the ELB rather than the EC2 IP addresses. When the EC2 instance in the Auto Scaling group is recreated, the IP will be changed, and the A record will not work in Route 53.
For more information, please refer to the below URL-
http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html