Q40 — AWS SAA-C03 Ch.13
Question 40 of 100 | ← Chapter 13
Q940. A company runs its customer-facing web application on containers. The workload uses Amazon Elastic Container Service (Amazon ECS) on AWS Fargate. The web application is resource intensive.The web application needs to be available 24 hours a day,7 days a week for customers.The company expects the application to experience short bursts of high traffic.The workload must be highly available.Which solution will meet these requirements MOST cost-effectively?
- A. Configure an ECS capacity provider with Fargate. Conduct load testing by using a third-party tool.Rightsize the Fargate tasks in Amazon CloudWatch.
- B. Configure an ECS capacity provider with Fargate for steady state and Fargate Spot for burst traffic. ✓
- C. Configure an ECS capacity provider with Fargate Spot for steady state and Fargate for burst traffic
- D. Configure an ECS capacity provider with Fargate. Use AWS Compute Optimizer to rightsize the Fargate task
Correct Answer: B. Configure an ECS capacity provider with Fargate for steady state and Fargate Spot for burst traffic.
Explanation
The solution that meets the requirements most cost-effectively is:B. Configure an ECS capacity provider with Fargate for steady state and Fargate Spot for burst traffic.Here's why:Cost Optimization: Fargate Spot instances offer significant cost savings compared to on-demand Fargate tasks, making them ideal for handling burst traffic.High Availability: Fargate provides inherent high availability, ensuring that the web application remains available even during traffic spikes.Capacity Management: By using Fargate for steady-state traffic and Fargate Spot for bursts, you can optimize resource utilization and minimize costs.Flexibility: This approach allows you to dynamically adjust capacity based on real-time traffic patterns, ensuring optimal performance and cost efficiency.Why other options are less efficient or cost-effective:A. Configure an ECS capacity provider with Fargate. Conduct load testing by using a third-party tool. Rightsize the Fargate tasks in Amazon CloudWatch. While load testing and rightsizing are important, they don't address the need for cost optimization during burst traffic.C. Configure an ECS capacity provider with Fargate Spot for steady state and Fargate for burst traffic. This approach is less cost-effective because Fargate is more expensive than Fargate Spot. It's better to use Fargate Spot for steady-state traffic and Fargate for bursts when necessary.D. Configure an ECS capacity provider with Fargate. Use AWS Compute Optimizer to rightsize the Fargate task. AWS Compute Optimizer can help with rightsizing, but it doesn't address the need for cost optimization during burst traffic.In summary:Option B provides the most cost-effective solution for a resource-intensive web application with short bursts of high traffic. By leveraging Fargate Spot for steady-state traffic and Fargate for bursts, you can optimize resource utilization and minimize costs while maintaining high availability.