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?
Creating a managed node group that contains only Spot Instances is the most cost-effective solution for a dedicated EKS cluster used infrequently for development and resiliency testing. Spot Instances offer significant cost savings compared to On-Demand Instances because they allow you to take advantage of unused EC2 capacity. While Spot Instances can be terminated by AWS with little notice, this is not typically a problem for development and test environments. This solution ensures that costs are minimized while still leveraging Amazon EKS's ability to manage all the nodes.
I think the question is easy to misunderstand, whether you should create the whole setup or just the development cluster. But from the wording ("The [production] EKS cluster has (!) managed node groups ... The company needs a dedicated EKS cluster for development work"), I conclude that we should only create the development cluster. As this will be used "infrequently" for testing purposes only, and it must be "most cost-effective", I'd go with A - new cluster with "one managed node group that contains only Spot instances".
The wording of question and options is so confusing. The last line is a throw off also "The EKS cluster must manage all the nodes" Which EKS cluster? A new one or the existing one. Both A and B are correct depending on how you decipher the question. I really hope the exam question uses better language!
I hate this question.... I think I will go with B just because wording also. A company is developing an application that "WILL" run on a production Amazon Elastic Kubernetes Service
This question is convoluted and missing some details. We need: - control plane running on on-demand EC2s - worker nodes running on spot instances Read this to understand correct solution: https://aws.amazon.com/blogs/containers/amazon-eks-now-supports-provisioning-and-managing-ec2-spot-instances-in-managed-node-groups/
The keywords are infrequent and resiliency.. This solution allows you to have a mix of On-Demand Instances and Spot Instances within the same EKS cluster. You can use the On-Demand Instances for the development work where you need dedicated resources and then leverage Spot Instances for testing the resiliency of the application. Spot Instances are generally more cost-effective but can be terminated with short notice, so using a combination of On-Demand and Spot Instances provides a balance between cost savings and stability. Option A (Create a managed node group that contains only Spot Instances) might be cost-effective, but it could introduce potential challenges for tasks that require dedicated resources and might not be the best fit for all scenarios.
Based on the document [1], we can know that only self-managed node group can deploy the container on EC2 dedicated hosts . Which mean that customer need to manually create launch template, auto scaling group, and register it to the EKS cluster. The creation process should be same as general EC2 auto scaling creation. For now, EKS managed node group only supported on-demand and spot. MOST cost-effectively: *Spot Instances* https://repost.aws/questions/QUugoX4f1gRHW0MGHRTHFFFA/how-to-create-eks-cluster-with-dedicated-host-node-group
If we look closer to the last requirement "The EKS cluster must manage all the nodes." Option B is the only feasable and cost-effective one.
I think this requirment mean to use manage node group to manage all worker nodes, the nodes for control panel will be managed by AWS, so A is correct
Option B
Why do you think so?
The GBT vote A, I know the spot instance is the cheapest, but the question says "dedicated EKS cluster for development", so I vote B
A dedicated EKS cluster means a separate EKS cluster that is isolated from the production cluster. This ensures that development work does not interfere with the production environment
"The company will use the development cluster infrequently to test the resiliency of the application" = Spot instances = cost effective
B is the best ans.
Why do you think so?
Option A leverages the cost savings of Spot Instances, which is ideal for a development environment where the application is tested infrequently, and there is flexibility in when the nodes can be interrupted. This aligns with the goal of cost-efficiency and takes advantage of EKS's ability to manage the nodes directly.
Clearly prod and dev are two different envs and two separate EKS cluster. In order to do meaningful resilience test, dev must matches the prod, so D is the answer.
I'll go with B because no matter what production should not go in spot instances
This has nothing to do with production instances though. The question is referring to the development instance.
For a development Amazon Elastic Kubernetes Service (Amazon EKS) cluster that is used infrequently to test application resiliency, the most cost-effective solution is to create a managed node group consisting solely of Spot Instances (Option A). Spot Instances offer significant cost savings—up to 90% compared to On-Demand Instances—making them ideal for non-critical, intermittent workloads like development and testing.
infrequently + cost effective -> Spot
in the exam.... answer A is too easy... AWS want the candidate to apply the two workload... the PROD vs DEV...