SAA-C03 Question 153
Single answerA company is running a microservices application using containers. The application currently uses Amazon ECS with the Fargate launch type to manage the containers. The company wants to migrate to Amazon EKS to take advantage of Kubernetes features, but without managing the underlying compute infrastructure. Which solution will allow the company to achieve this goal?
- A
Use Amazon EKS with Managed Node Groups to deploy and manage the Kubernetes nodes.
- B
Use Amazon EKS with the Fargate profile to run Kubernetes pods without managing the compute infrastructure.
- C
Migrate the application to Amazon EC2 instances and use Amazon EKS to orchestrate the containers.
- D
Run Amazon ECS with EC2 launch type and integrate it with a Kubernetes cluster for orchestration.
Show answer and explanation
Correct answer: B
Explanation
Amazon EKS provides multiple options for running Kubernetes workloads. By using EKS with Fargate profiles, you can deploy Kubernetes pods without managing any EC2 instances, as Fargate provides a serverless compute environment. This meets the company's goal of leveraging Kubernetes features while avoiding the operational overhead of managing compute infrastructure.
- A. Incorrect.
Amazon EKS Managed Node Groups are used to manage EC2-based Kubernetes nodes, which still require you to manage the underlying compute infrastructure. This does not meet the requirement of avoiding compute management.
- B. Correct.
Amazon EKS with the Fargate profile allows you to run Kubernetes pods on serverless compute infrastructure, meeting the requirement of not managing the underlying compute layer.
- C. Incorrect.
Migrating to Amazon EC2 instances and using Amazon EKS would require managing the EC2 instances, which contradicts the requirement to avoid managing the underlying infrastructure.
- D. Incorrect.
Amazon ECS with EC2 launch type is unrelated to Kubernetes and requires management of EC2 instances, so it does not satisfy the requirement.