Q65 — AWS SAA-C03 Ch.11

Question 65 of 100 | ← Chapter 11

Q765. A company is developing an application that will run on a production Amazon Elastic Kubernetes Service (Amazon EKS) cluster. The EKS cluster has managed node groups that are provisioned with On-Demand Instances.The company needs a dedicated EKS cluster for development work. The company will use the development cluster infrequently to test the resiliency of the application. The EKS cluster must manage all the nodes.Which solution will meet these requirements MOST cost-effectively?

• A. Create a managed node group that contains only Spot Instances. ✓
• B. Create two managed node groups. Provision one node group with On-Demand Instances. Provision the second node group with Spot Instances.
• C. Create an Auto Scaling group that has a launch configuration that uses Spot Instances. Configure the user data to add the nodes to the EKS cluster.
• D. Create a managed node group that contains only On-Demand Instances.

Correct Answer: A. Create a managed node group that contains only Spot Instances.

Explanation

To meet the requirements of having a dedicated EKS cluster for development work, infrequent usage, and testing the resiliency of the application in the most cost-effective manner, the most suitable solution is:A. Create a managed node group that contains only Spot Instances.Option A provides the desired solution:Create a managed node group that contains only Spot Instances:\1. Managed Node Group: By creating a managed node group, you can have a specific set of EC2 instances dedicated to your EKS cluster. This allows you to separate the development work from the production cluster and manage the nodes independently.\2. Spot Instances: Provision the managed node group with Spot Instances. Spot Instances are spare EC2 instances with significantly lower costs compared to On-Demand Instances. Since the development cluster will be used infrequently, leveraging Spot Instances can help reduce costs significantly.Here's why the other options are not the most suitable choices:Option B suggests creating two managed node groups - one provisioned with On-Demand Instances and the other with Spot Instances. While this approach provides flexibility, it increases complexity and potentially incurs higher costs compared to using only Spot Instances for the development cluster.Option C suggests creating an Auto Scaling group with a launch configuration using Spot Instances and configuring user data to add the nodes to the EKS cluster. While this approach can work, using a managed node group simplifies the management of EC2 instances in the EKS cluster.Option D suggests creating a managed node group with only On-Demand Instances. While this option ensures stability and reliability, it does not meet the requirement of being cost-effective, as On-Demand Instances have higher costs compared to Spot Instances.Therefore, the most cost-effective solution to have a dedicated EKS cluster for development work, infrequent usage, and testing the resiliency of the application is A: Create a managed node group that contains only Spot Instances.