Free AWS SAP-C02 Actual Exam Questions - Question 10 Discussion
website that runs on two Amazon EC2 instances behind an Application Load Balancer (ALB). The
application backend is a Python application that runs on three EC2 instances behind another ALB.
The EC2 instances are large, general purpose On-Demand Instances that were sized to meet the on-
premises specifications for peak usage of the application.
The application averages hundreds of thousands of requests each month. However, the application is
used mainly during lunchtime and receives minimal traffic during the rest of the day.
A solutions architect needs to optimize the infrastructure cost of the application without negatively
affecting the application availability.
Which combination of steps will meet these requirements? (Choose two.)
B imo for sure, moving the frontend to S3 cuts costs a lot since it’s just static content and no need for EC2 there. For the backend, E makes sense because burstable instances can handle the peaks but save money during low-traffic times. Spot instances (D) are risky here since interruptions might cause downtime, which they want to avoid. Also, switching instance families (A) won’t necessarily save money if the usage pattern is uneven like this. So yeah, B and E feels like the best combo to optimize cost without losing availability.
Makes sense to offload the static frontend to S3 for cost savings, so B fits. For the backend, switching to burstable instances (E) helps with low off-peak demand without risking interruptions like Spot instances would.
It’s B and E since S3 reduces frontend cost and burstable instances handle variable backend load well.
B/D? Moving the frontend to S3 eliminates EC2 costs there, and Spot Instances for backend can drastically cut expenses if the app can handle interruptions. Burstable instances might risk throttling during peak use.
B, D – S3 for frontend cuts cost, and Spot Instances for backend save money if workload tolerates interruption.
B tbh, moving the frontend to S3 for static hosting makes sense and should save costs. E also sounds right since burstable instances could handle low traffic periods cheaper without losing availability.