A company must migrate a three-tier .NET web application (which depends on MySQL) from on-premises to AWS to handle 200,000 daily users and provide scalability and high availability. Which design steps should the solutions architect take to meet these requirements?

The correct option provides a robust, scalable, and highly available architecture. An Application Load Balancer (ALB) is ideal for HTTP/HTTPS traffic from web applications, distributing requests across an EC2 Auto Scaling group in multiple Availability Zones (AZs) for high availability and scalability. Amazon Aurora MySQL is a high-performance, highly available, and scalable database solution, and a Multi-AZ cluster ensures fault tolerance. CloudFormation enables infrastructure as code, making deployments repeatable and manageable. A Route 53 alias provides a reliable way to map the domain to the ALB. The first incorrect option uses Elastic Beanstalk, which is suitable, but a Network Load Balancer (NLB) is typically for TCP/UDP traffic, not HTTP/HTTPS web applications, where an ALB is more appropriate. The third incorrect option suggests a multi-Region deployment, which is overkill for the given requirements and adds complexity and cost. The fourth incorrect option uses Amazon ECS with Spot Instances, which are not suitable for a production web application requiring consistent availability, and an Amazon RDS MySQL single instance lacks the high availability of Aurora Multi-AZ.