Amazon EKS with Fargate for Least Operational Overhead

SAA-C03 By islever Editorial Last updated

Design secure workloads and applications.

Short answer

C Use AWS Fargate to supply compute capacity by creating a Fargate profile and deploying the application to avoid managing underlying EC2 infrastructure.

Question

A company runs an on-premises application on a Kubernetes cluster. The company recently added millions of new customers. The company's existing on-premises infrastructure is unable to handle the large number of new customers. The company needs to migrate the on-premises application to the AWS Cloud. The company will migrate to an Amazon Elastic Kubernetes Service (Amazon EKS) cluster. The company does not want to manage the underlying compute infrastructure for the new architecture on AWS. Which solution will meet these requirements with the LEAST operational overhead?
  1. Use a self-managed node to supply compute capacity. Deploy the application to the new EKS cluster.
  2. Use managed node groups to supply compute capacity. Deploy the application to the new EKS cluster.
  3. Use AWS Fargate to supply compute capacity. Create a Fargate profile. Use the Fargate profile to deploy the application. Correct Answer
  4. Use managed node groups with Karpenter to supply compute capacity. Deploy the application to the new EKS cluster.

Key Takeaways

The exam traps candidates into choosing managed node groups; however, the requirement for 'least operational overhead' and no management of underlying compute points strictly to the serverless Fargate option.

This question tests the selection of serverless container compute options in Amazon EKS to minimize management overhead. The correct solution utilizes AWS Fargate, which abstracts the underlying infrastructure completely.

Common mistake: Candidates often select Managed Node Groups (Option B) because they are the standard way to run EKS workloads. They overlook that managing nodes, even when automated, still constitutes operational overhead compared to the fully serverless Fargate model.

Expert Analysis

Why the Answer Is Correct

AWS Fargate is a technology that allows you to focus on building your applications without managing servers. When using Amazon EKS with Fargate, you do not provision or manage EC2 instances; AWS handles the scaling, patching, and maintenance of the underlying infrastructure. This directly satisfies the requirement for the 'LEAST operational overhead' and the explicit constraint that the company does not want to manage underlying compute.

Why the Other Options Are Wrong

Options A, B, and D all rely on EC2 instances as the underlying compute resource. Option A uses self-managed nodes, requiring significant manual intervention for OS updates, security patches, and capacity planning. Options B and D use managed node groups, which automate instance lifecycle management but still require the user to manage the node group configuration, scaling policies, and cluster capacity. While Karpenter (Option D) improves efficiency, it still operates on top of EC2 instances, violating the 'no management of underlying compute' constraint.

Community Comment Notes

Community consensus strongly supports Fargate due to the serverless nature. As Razvan_C noted, "The company does not want to manage the underlying compute infrastructure... Serverless => Fargate." Another commenter emphasized that with Fargate, you don't have to "provision, configure, or scale groups of virtual machines," highlighting the reduction in operational tasks compared to node-based approaches.

Official Reference

https://docs.aws.amazon.com/eks/latest/userguide/fargate.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

Always look for keywords like 'serverless', 'no underlying infrastructure management', or 'least operational overhead' when comparing EKS compute options. If 'managed node groups' are an option alongside 'Fargate' and the goal is minimizing ops, choose Fargate unless specific requirements (like GPU access or custom AMIs) force the use of EC2.

Frequently Asked Questions

Why not use Managed Node Groups for least overhead?

Managed Node Groups still require you to manage the node group itself, including scaling configurations and ensuring capacity. Fargate removes the node abstraction entirely.

Does Fargate support all Kubernetes features?

Fargate supports most standard Kubernetes features but may have limitations regarding certain daemonsets or host-networking pods compared to EC2-backed nodes.

More SAA-C03 FAQ →

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 5 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 5

  1. Razvan_C 👍 5 Answered C
    "The company does not want to manage the underlying compute infrastructure for the new architecture on AWS" => Serverless => Fargate
  2. viejito 👍 2
    Respuesta correcta C = AWS Fargate = menor sobrecarga operativa . A , B y C tienen gestión de infraestructura .
  3. viejito 👍 2
    Respuesta correcta C = AWS Fargate = menor sobrecarga operativa. A, B y D tienen gestión de infraestructura.
  4. FlyingHawk 👍 1 Answered C
    With Fargate, you don’t have to provision, configure, or scale groups of virtual machines on your own to run containers. You also don’t need to choose server types, decide when to scale your node groups, or optimize cluster packing. A Fargate profile is used to specify which Kubernetes pods should run on Fargate. By creating a Fargate profile, you can ensure that your application runs on Fargate without needing to manage node groups or EC2 instances.
  5. elmyth 👍 3 Answered C
    Fargate

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide