AWS Certified Solutions Architect Associate SAA-C03 Practice Question
A company is containerizing an internal API that normally runs at low traffic but occasionally experiences unpredictable, short-lived traffic spikes. The operations team does not want to manage or patch any Amazon EC2 instances and seeks the most cost-efficient compute option.
Which solution meets these requirements?
Deploy the application on Amazon ECS using the AWS Fargate launch type.
Run the containers on an Amazon EC2 Auto Scaling group using On-Demand Instances.
Deploy the application on Amazon Elastic Kubernetes Service (EKS) with self-managed EC2 worker nodes purchased as Reserved Instances.
Deploy the application on Amazon Elastic Container Service (ECS) using EC2 Spot Instances.
With AWS Fargate you specify only the vCPU and memory each task needs and are billed per-second for those resources. There are no EC2 instances to manage, so you avoid paying for idle cluster capacity. This makes AWS Fargate the most cost-effective choice for highly variable, bursty container workloads. EC2-based options (whether On-Demand, Spot, or Reserved) require running EC2 instances that may sit idle between spikes, while EKS on self-managed nodes has similar instance costs and management overhead.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is AWS Fargate?
Open an interactive chat with Bash
How does Fargate pricing work?
Open an interactive chat with Bash
What are the differences between AWS Fargate and Amazon EC2?