Q40 — AWS SAP-C02 Ch.2

Question 40 of 75 | ← Chapter 2

Q190. A company is hosting a three-tier web application in an on-premises environment. Due to a recent surge in traffic that resulted in downtime and a significant financial impact, company management has ordered that the application be moved to AWS. The application is written in .NET and has a dependency on a MySQL database. A solutions architect must design a scalable and highly available solution to meet the demand of 200,000 daily users. Which steps should the solutions architect take to design an appropriate solution?

Correct Answer: B. Use AWS CloudFormation to launch a stack containing an Application Load Balancer (ALB) in front of an Amazon EC2 Auto Scaling group spanning three Availability Zones. The stack should launch a Multi- AZ deployment of an Amazon Aurora MySQL DB cluster with a Retain deletion policy. Use an Amazon Route 53 alias record to route traffic from the company's domain to the ALB

Explanation

Option B is the best solution to meet the requirement of designing a scalable and highly available solution for the three-tier web application with a dependency on a MySQL database. Using AWS CloudFormation to launch a stack containing an Application Load Balancer (ALB) in front of an Amazon EC2 Auto Scaling group spanning three Availability Zones provides high availability and scalability for the web server tier. Launching a Multi-AZ deployment of an Amazon Aurora MySQL DB cluster with a Retain deletion policy provides high availability and durability for the database tier. Using an Amazon Route 53 alias record to route traffic from the company's domain to the ALB allows for efficient routing of traffic to the web servers. Option A does not include a durable database solution, which is critical to ensure data is protected and always available. Elastic Beanstalk can be used but should be paired with a more robust database solution like RDS Multi-AZ or Aurora. Option C includes two Regions, which may add unexpected complexity to the design, especially when considering at-scale operations. Additionally, using a cross-Region read replica adds additional latency that may have a performance impact. Option D uses ECS and Spot Instances for the web server layer, which may not be the most appropriate solution for a .NET application, and may introduce additional complexity. Additionally, using an RDS instance with a Snapshot deletion policy does not provide the same level of durability and availability as a Multi-AZ deployment. Overall, Option B provides the most robust and appropriate solution by leveraging a highly available and durable database solution with Aurora Multi-AZ and providing high availability and scalability for the web server layer through an ALB with an EC2 Auto Scaling group.