How Should Containers Run to Minimize Cost and Overhead?
Answer
Correct answer: B — run the stateless containers on Spot Instances in an Amazon EKS managed node group for maximum savings with managed orchestration.
A company wants to run applications in containers in the AWS Cloud. These applications are stateless and can tolerate disruptions within the underlying infrastructure. The company needs a solution that minimizes cost and operational overhead. What should a solutions architect do to meet these requirements?
Community Insight
The question tests the intersection of Spot pricing and managed container orchestration; the trap is assuming a raw EC2 Auto Scaling group running containers is 'low overhead' when it leaves all scheduling, self-healing, and interruption handling to the customer.
For stateless container applications that tolerate infrastructure disruptions, the cheapest and least operationally demanding pattern on AWS is Spot Instances inside an Amazon EKS managed node group. This page explains why option B beats a plain EC2 Auto Scaling group and On-Demand alternatives.
Option A is the most tempting wrong pick: Spot Instances in an EC2 Auto Scaling group do cut compute cost, but with no managed orchestrator the company must install runtimes, place containers, handle Spot interruption notices, and manage rollouts itself — which directly violates the 'minimizes operational overhead' requirement.
Community Discussion (56 comments)
Sushmita42
👍 1
Selected: A
The key clues in the question are: Containers Stateless applications Can tolerate infrastructure disruptions Minimize cost Minimize operational overhead The strongest clue is: "can tolerate disruptions" That makes EC2 Spot Instances a strong choice because Spot Instances provide significant cost savings compared with On-Demand Instances and are designed for interruption-tolerant workloads
46e1a46
👍 1
Selected: D
3 Storage needs 3 different solutions - Max I/O performance -> EC2 Instance Store. This is physically attached NVMe SSD on the host server, fasters possible I/O on AWS - Durable Storage for media content -> S3. S3 has 11 nines of durability - Archival storage -> S3 Glacier. Cheapest option for data that's "not in use anymore" D
Maco
👍 1
Selected: A
Spot Instances Up to 90% cheaper Perfect for: Stateless workloads Interruptible workloads
Bhuvan_D
👍 1
Selected: A
Why Option A is best: Amazon EC2 Auto Scaling Group + Spot Instances: Spot Instances are highly cost-effective (up to 90% cheaper than On-Demand). Auto Scaling ensures automatic replacement of interrupted instances. Stateless nature of apps makes Spot a perfect fit. Operational overhead is low compared to running a full Kubernetes cluster (like EKS).
MortisG
👍 1
Selected: B
Answer is B since it’s less operational overhead to run containers on EKS (managed service) than running on EC2 instances which implies installing dockers to orchestrate containers)
zdi561
👍 1
Selected: A
ai response "Generally, an ECS EC2 Auto Scaling Group is considered cheaper than an EKS Managed Node Group because with ECS, you only pay for the EC2 instances used to run your containers, while EKS adds an additional cost per cluster hour on top of the compute costs for the managed nodes"
Dharmarajan
👍 2
Selected: B
Definitely B. running containers on spot EC2 instances means there has to be additional configuration requirements every time an instance comes up. That means making a custom AMI with prepping the spot instance to launch the container = additional operational overhead in maintaining the AMI - with EKS, that overhead is eliminated.
satyaammm
👍 2
Selected: B
Spot Instances are the cheapest and most suitable here along with EKS for automation and thereby reducing operational overhead.
19d92c7
👍 1
When you use EKS is add operational over head, if ECS was in option then it could have justified here
PaulGa
👍 1
Selected: A
Ans A - hint: "stateless" and 'don't care' infrastructure - so Spot and containerisation
huaze_lei
👍 1
Spot instance is definitely the answer for interruptible process. It's between A and B now. I would reckon Option B requires lesser operational overheads than to maintain own fleet of EC2 servers with containers.
SaurabhTiwari1
👍 2
Selected: B
B is correct
ChymKuBoy
👍 2
Selected: B
B for sure
Anthony_Rodrigues
👍 4
IMHO, the option B is the right one. Breaking down the reasons for it: 1 - Spot is much cheaper than on-demand, which already eliminates C&D for cost related. 2 - Even though we can create a bootstrap script to install docker, managing this can be complicated, especially if any of the applications require more than one instance running.
lofzee
👍 3
Container in ec2 or container on a container platform? B
EMPERBACH
👍 3
Selected: B
run applications in containers -> Container service not EC2 (no operational overhead to config container workload on EC2) Spot instance < On-demand cost
vip2
👍 2
Selected: A
Does A implicitly means run spot Instance on ECS?
awsgeek75
👍 2
Selected: B
Spot instances for disruption friendly containers which are also cheaper. EKS allows using spot instances from a managed node group that takes away the EC2 operational overhead. Link: https://aws.amazon.com/blogs/containers/amazon-eks-now-supports-provisioning-and-managing-ec2-spot-instances-in-managed-node-groups/ "Previously, customers had to run Spot Instances as self-managed worker nodes in their EKS clusters. This meant doing some heavy lifting such as building and maintaining configuration for Spot Instances in EC2 Auto Scaling groups, deploying a tool for handling Spot interruptions gracefully, deploying AMI updates, and updating the kubelet version running on their worker nodes. Now, all you need to do is supply a single parameter to indicate that a managed node group should launch Spot Instances, and provide multiple instance types that would be used by the underlying EC2 Auto Scaling group."
pipici
👍 2
Selected: A
A has less operational overhead
xdkonorek2
👍 4
Selected: B
running containers without container service like EKS introduce huge operational effort
David_Ang
👍 7
Selected: B
dude always if you have a service that is meant to be used for a job there is the correct answer, is logic.
tom_cruise
👍 3
Selected: B
It is a lot of work to manage docker environment on ec2 instance by yourself.
poponpo
👍 1
Selected: A
k8s is not easy solution. there are too many to study about it. You have to know about ingress, storageclass, cni, namesapce, etc... they make burdened to operate.
Modulopi
👍 1
Selected: A
reponse A
TariqKipkemei
👍 5
Selected: B
Minimize costs = Spot instances Minimize operational overhead = Amazon EKS is a managed Kubernetes service that makes it easy for you to run Kubernetes on AWS and on-premises. https://aws.amazon.com/pm/eks/?trk=c69c708c-c423-4c07-9fc8-513781540cc7&sc_channel=ps&ef_id=Cj0KCQjw9MCnBhCYARIsAB1WQVWD7pSyGgjzsk6QHMNAIZrHvuAzZd4cy9b4QAaCcB5QTn6MR_czhWkaAm6UEALw_wcB:G:s&s_kwcid=AL!4422!3!669047416746!e!!g!!eks!20433874212!155230227787#:~:text=is%20Amazon%20EKS%3F-,Amazon%20EKS,-is%20a%20managed I would not try to overthink this.
Guru4Cloud
👍 4
Selected: B
The key reasons are: Using Spot Instances reduces EC2 costs significantly compared to On-Demand. EKS managed node groups simplify running and scaling containerized applications vs self-managed Kubernetes. Since the applications are stateless and fault-tolerant, intermittent Spot interruptions are acceptable. The combination of Spot + EKS provides the most cost-efficient infrastructure with minimal operational overhead. Options A, C and D either use On-Demand instances or self-managed infrastructure, which increases costs and overhead.
aadityaravi8
👍 2
to run application with minimum cost, use spot instances and to reduce operational overhead, run it on EKS. Hence B should be right answer.
cookieMr
👍 6
Selected: B
Option B is the recommended solution. Using Spot Instances within an Amazon EKS managed node group allows you to run containers in a managed Kubernetes environment while taking advantage of the cost savings offered by Spot Instances. Spot Instances provide access to spare EC2 capacity at significantly lower prices than On-Demand Instances. By utilizing Spot Instances in an EKS managed node group, you can reduce costs while maintaining high availability for your stateless applications. Option A suggests using Spot Instances in an EC2 Auto Scaling group, which is a valid approach. However, utilizing Amazon EKS provides a more streamlined and managed environment for running containers. Options C and D suggest using On-Demand Instances, which would provide stable capacity but may not be the most cost-effective solution for minimizing costs, as On-Demand Instances typically have higher prices compared to Spot Instances.
Abrar2022
👍 4
There are no additional costs to use Amazon EKS managed node groups. You only pay for the AWS resources that you provision.
MutiverseAgent
👍 1
you do not necessary need to install K8S, in terms of plain containers you can run them using docker just as you do on your own machine.
bgsanata
👍 18
Selected: A
Requirement is "minimizes cost and operational overhead" A is better option than B as EKS add additional cost and operational overhead.
Tsige
👍 5
Using Amazon EKS with managed node groups simplifies container orchestration by reducing the operational overhead of managing the underlying infrastructure and Kubernetes control plane. EKS automatically handles tasks like patching, scaling, and deploying containers across multiple nodes, further reducing operational effort. While Spot Instances in an EC2 Auto Scaling group can reduce costs, it requires more manual management of container orchestration (e.g., deploying, scaling, and managing containers across instances), increasing operational overhead compared to EKS. In the exam its highly recommended to select Managed services Like EKS in this case. My choice is B.
EMPERBACH
👍 9
Really ??? You want more configuration efforts for container workload on EC2, instead of using EKS ::))
MutiverseAgent
👍 6
In my opinion option A) seems to be a reasonable at first because setting up AWS EKS might be seem as an operation overhead comparing to the option of running the containers inside the EC2 using docker just as you we do on your own machines. However, consider installing docker on multiple EC2 instances and manually manage docker instances and images will end up in chaos, so, as a conclusion, the operational cost of setting up AWS EKS will worth the effort.
Lalo
👍 1
USING SPOT INSTANCES WITH EKS https://ec2spotworkshops.com/using_ec2_spot_instances_with_eks.html
ruqui
👍 6
option A is the worst option in terms of operational overhead ... you have to install your own kubernetes cluster!!! B is a more suitable option
TheAbsoluteTruth
👍 4
Selected: B
La opción B es la mejor para cumplir con los requisitos de minimización de costos y gastos generales operativos mientras se ejecutan contenedores en la nube de AWS. Amazon EKS es un servicio de orquestación de contenedores altamente escalable y de alta disponibilidad que se encarga de administrar y escalar automáticamente los nodos de contenedor subyacentes. El uso de instancias de spot en un grupo de nodos administrados de Amazon EKS ayudará a reducir los costos en comparación con las instancias bajo demanda, ya que las instancias de spot son instancias de EC2 disponibles a precios significativamente más bajos, pero pueden ser interrumpidas con poco aviso. Al aprovechar la capacidad no utilizada de EC2 a un precio reducido, la empresa puede ahorrar dinero en costos de infraestructura sin comprometer la tolerancia a fallos o la escalabilidad de sus aplicaciones en contenedores.
alexiscloud
👍 1
B: Sport instance save cost
bgsanata
👍 1
Selected: D
The answer should be D. Spot instance is not good option at all. The question say "...can tolerate disruptions" this doesn't mean it can run at random time intervals.
Robrobtutu
👍 1
Spot instances are the correct option for this case.
GalileoEC2
👍 10
Answer is A: Amazon ECS: ECS itself is free, you pay only for Amazon EC2 resources you use. Amazon EKS: The EKS management layer incurs an additional cost of $144 per month per cluster. Advantages of Amazon ECS include: Spot instances: Because containers are immutable, you can run many workloads using Amazon EC2 Spot Instances (which can be shut down with no advance notice) and save 90% on on-demand instance costs.
Sdraju
👍 2
Selected: B
Spot instances for cost optimisation and Kubernetes for container management
Zerotn3
👍 5
Selected: B
A and B are working. but requirements have "operational overhead". EKS would allow the company to use Amazon EKS to manage the containerized applications.
Buruguduystunstugudunstuy
👍 6
Selected: B
The correct answer is B. To minimize cost and operational overhead, the solutions architect should use Spot Instances in an Amazon Elastic Kubernetes Service (Amazon EKS) managed node group to run the application containers. Amazon EKS is a fully managed service that makes it easy to run Kubernetes on AWS. By using a managed node group, the company can take advantage of the operational benefits of Amazon EKS while minimizing the operational overhead of managing the Kubernetes infrastructure. Spot Instances provide a cost-effective way to run stateless, fault-tolerant applications in containers, making them a good fit for the company's requirements.
JayBee65
👍 6
Running your Kubernetes and containerized workloads on Amazon EC2 Spot Instances is a great way to save costs. ... AWS makes it easy to run Kubernetes with Amazon Elastic Kubernetes Service (EKS) a managed Kubernetes service to run production-grade workloads on AWS. To cost optimize these workloads, run them on Spot Instances. https://aws.amazon.com/blogs/compute/cost-optimization-and-resilience-eks-with-spot-instances/
career360guru
👍 1
Selected: B
Option B
Qjb8m9h
👍 2
B. Use Spot Instances - Supports Disruption ( stop and start at anytime) Elastic Kubernetes Service (Amazon EKS) managed node group - Supports containerized application.
jiemin
👍 3
why not A, EC2 can run container with lower cost than EKS...
JayBee65
👍 3
There are no additional costs to use Amazon EKS managed node groups, you only pay for the AWS resources you provision, so I disagree
Wpcorgan
👍 1
B is correct
study_aws1
👍 5
Selected: B
This should explain https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html
mabotega
👍 1
Selected: B
Answer B
Six_Fingered_Jose
👍 2
Selected: B
agreed with B cause container
tubtab
👍 1
Selected: B
bbbbbb
Lilibell
👍 1
The answer is B
brushek
👍 7
Selected: B
it should be B: https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-eks-support-ec2-spot-instances-managed-node-groups/
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option B pairs the deepest discount with the least customer-managed work. Spot Instances typically save 70–90% versus On-Demand, and because these applications are stateless and disruption-tolerant, they can safely absorb Spot interruptions through rescheduling onto other nodes. An Amazon EKS managed node group handles node provisioning, AMI and health management, automatic replacement of unhealthy nodes, and scaling on the customer's behalf, while the EKS control plane provides managed scheduling, service discovery, and self-healing for the containers themselves. AWS explicitly supports Spot Instances in EKS managed node groups, including built-in responses to Spot interruption notices, so no custom interruption tooling is required.Why the Other Options Are Wrong
Options C and D use On-Demand Instances, which forfeit the Spot savings that the requirement to minimize cost makes mandatory, so both fail on the cost dimension regardless of their orchestration model. Option A does use Spot Instances, but a plain EC2 Auto Scaling group offers no container orchestration layer: the company would have to install and operate the container runtime, decide container placement, build its own health-check and replacement logic, and react to Spot interruptions manually — the opposite of minimized operational overhead. Option D, while managed, is both more expensive than B (On-Demand pricing) and adds no advantage that the Spot-based managed node group does not already provide.Community Comment Notes
Commenters split between A and B, and the disagreement is mostly about how operational overhead is measured. bgsanata argued A because "EKS add additional cost and operational overhead," and GalileoEC2 noted that "Amazon ECS: ECS itself is free, you pay only for Amazon EC2 resources you use" versus an EKS control-plane charge — but ECS is not one of the offered options, so that trade-off does not apply here. On the other side, ruqui countered that "option A is the worst option in terms of operational overhead" since it implies assembling your own Kubernetes cluster, and MutiverseAgent warned that manually managing Docker on multiple EC2 instances "will end up in chaos." brushek pointed to AWS's announcement that Amazon EKS supports Spot Instances in managed node groups, Buruguduystunstugudunstu stated flatly "The correct answer is B," and EMPERBACH pushed back only on the assumption that EKS requires more configuration effort than raw EC2.Official Reference
Exam Strategy
On SAA-C03 cost questions, eliminate any option that uses On-Demand Instances when the prompt says the workload tolerates interruptions — Spot is almost always the intended lever. Then compare the survivors on management: choose the fully managed service (EKS managed node group) over self-assembled infrastructure whenever operational overhead is named as a requirement.
Frequently Asked Questions
Why is Spot in an EC2 Auto Scaling group (A) not the lowest-overhead choice?
A raw EC2 Auto Scaling group has no orchestrator, so you must place containers, handle Spot interruptions, and manage rollouts yourself. EKS managed node groups automate all of that.
Doesn't EKS cost extra and undermine the cost-minimization goal?
The EKS control-plane fee is small compared with running On-Demand Instances, and Spot savings of 70–90% far outweigh it. Since no ECS option is offered, EKS plus Spot is the cheapest managed path.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →