A team runs workloads on Amazon EKS and wants AWS to handle node provisioning, AMI patching and scaling, but the workloads must still run on EC2 instances. Which option should they choose?
Show answer and explanation
Answer: A
Managed node groups are created and tracked by EKS, which provisions the instances through an Auto Scaling group, applies AMI updates and integrates them with the cluster. The team still gets EC2 instances to schedule pods on, but AWS owns the node lifecycle tasks.
Self-managed groups leave all of that to the operator.
Why the other options are wrong
- B. Self-managed node groups require you to build AMIs, patch hosts and manage scaling yourself.
- C. Fargate profiles remove EC2 nodes entirely, which does not satisfy the EC2 requirement.
- D. Changing orchestrators does not address the EKS node management requirement.