Question 35

Question

A company migrated an application to the AWS Cloud. The application runs on two Amazon EC2
instances behind an Application Load Balancer (ALB). Application data is stored in a MySQL database
that runs on an additional EC2 instance. The application's use of the database is read-heavy.
The loads static content from Amazon Elastic Block Store (Amazon EBS) volumes that are attached to
each EC2 instance. The static content is updated frequently and must be copied to each EBS volume.
The load on the application changes throughout the day. During peak hours, the application cannot
handle all the incoming requests. Trace data shows that the database cannot handle the read load
during peak hours.
Which solution will improve the reliability of the application?

Accepted Answer

Containerize the application. Migrate the application to an Amazon Elastic Container Service
(Amazon ECS) cluster. Use the AWS Fargate launch type for the tasks that host the application. Create
an Amazon Elastic File System (Amazon EFS) file system for the static content. Mount the EFS file
system to each container. Configure AWS Application Auto Scaling on the ECS cluster Set the ECS
service as a target for the ALB. Migrate the database to Amazon Aurora MySQL Serverless v2 with a
reader DB instance.

Chris L. · Answer

D or maybe B, but D fits better because EFS is ideal for sharing frequently updated static content across containers and the Aurora Serverless v2 with reader deals with the read-heavy DB problem (autoscaling and read scaling). ECS Fargate + Application Auto Scaling covers handling variable load. Only concern: if writes were far heavier, solution might shift. Thoughts?

Casey R. · Answer

Probably C, since mounting a single EBS volume might look like the right way for shared data, but that's a trap. EFS would be better for that, but I think C is what most would pick if not careful.

AWS SAP-C02 Real Exam Questions [2026 Update] Quiz

Premium Access Includes