Q45 — AWS SAA-C03 Ch.14

Question 45 of 100 | ← Chapter 14

Q1045. 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?

Correct Answer: C. Use AWS Fargate to supply compute capacity. Create a Fargate profile. Use the Fargate profile to deploy the application.

Explanation

To migrate the on-premises application to an Amazon Elastic Kubernetes Service (Amazon EKS) cluster while minimizing operational overhead and avoiding management of the underlying compute infrastructure, the best solution is:C. Use AWS Fargate to supply compute capacity. Create a Fargate profile. Use the Fargate profile to deploy the application.Explanation:\1. AWS Fargate: - Fargate is a serverless compute engine for containers that allows you to run Kubernetes applications without managing the underlying EC2 instances. This means that you don't have to worry about provisioning, scaling, or managing servers, which significantly reduces operational overhead.\2. Fargate Profiles: - By creating a Fargate profile, you can specify which pods should run on Fargate. This allows you to seamlessly deploy your application to the EKS cluster without needing to manually handle the compute resources.\3. Operational Efficiency: - Fargate automatically scales the resources based on the application needs and only charges you for the resources that your containers use, making it a cost-effective solution for handling unpredictable workloads.Evaluation of Other Options:A. Use a self-managed node to supply compute capacity: - This option requires managing the EC2 instances yourself, which introduces significant operational overhead. It does not align with the requirement of minimizing management tasks for the underlying infrastructure.B. Use managed node groups to supply compute capacity: - While managed node groups simplify some aspects of managing EC2 instances in EKS, you still need to handle scaling, updates, and maintenance of the underlying nodes, which is not as low-maintenance as using Fargate.D. Use managed node groups with Karpenter to supply compute capacity: - Although Karpenter automates the provisioning of nodes based on demand, it still involves managing EC2 instances to some extent. This option does not provide the same level of operational simplicity as Fargate.Conclusion:Option C is the most suitable solution for migrating the application to AWS EKS with the least operational overhead, allowing the company to focus on application development rather than infrastructure management.