AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
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?
Other
Community
UAnonymous
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.
Explanation:
Explanation
Correct Answer: A - Create a managed node group that contains only Spot Instances.
Why this is the most cost-effective solution:
-
Development cluster requirements: The company needs a dedicated EKS cluster for development work that will be used infrequently to test application resiliency.
-
Cost optimization with Spot Instances: Spot Instances are ideal for development/test workloads because:
- They offer up to 90% discount compared to On-Demand Instances
- They are perfect for fault-tolerant, stateless, and interruptible workloads
- Development/testing environments can tolerate interruptions
- The infrequent usage pattern aligns perfectly with Spot Instance characteristics
-
Managed node group requirement: The question states "The EKS cluster must manage all the nodes." Managed node groups with Spot Instances satisfy this requirement while providing cost savings.
Why other options are not optimal:
-
Option B: Creating two managed node groups (one On-Demand, one Spot) adds unnecessary complexity and cost. For a development cluster used infrequently, having On-Demand Instances defeats the purpose of cost optimization.
-
Option C: Creating an Auto Scaling group with launch configuration and user data to add nodes to EKS violates the requirement that "The EKS cluster must manage all the nodes." This approach uses self-managed nodes instead of managed node groups.
-
Option D: Creating a managed node group with only On-Demand Instances is the most expensive option and doesn't leverage cost optimization opportunities for a development environment.
Key AWS Concepts:
- Spot Instances: Best for workloads that are fault-tolerant, flexible in when they run, and can handle interruptions
- Managed Node Groups: Automatically manage the lifecycle of nodes (EC2 instances) in an EKS cluster
- Cost Optimization: Development/test environments should use Spot Instances or Savings Plans to reduce costs
Best Practice: For development/test EKS clusters, use managed node groups with Spot Instances to achieve the best balance of cost-effectiveness and management simplicity.
Comments
Loading comments...