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 wants to run applications in containers in the AWS Cloud. These applications are stateless and can tolerate disruptions within the underlying infrastructure. The company needs a solution that minimizes cost and operational overhead.
What should a solutions architect do to meet these requirements?
Other
Community
UAnonymous
A
Use Spot Instances in an Amazon EC2 Auto Scaling group to run the application containers.
B
Use Spot Instances in an Amazon Elastic Kubernetes Service (Amazon EKS) managed node group.
C
Use On-Demand Instances in an Amazon EC2 Auto Scaling group to run the application containers.
D
Use On-Demand Instances in an Amazon Elastic Kubernetes Service (Amazon EKS) managed node group.
Explanation:
Explanation
Correct Answer: B - Use Spot Instances in an Amazon Elastic Kubernetes Service (Amazon EKS) managed node group.
Key Analysis:
-
Cost Minimization Requirement: The company needs to minimize cost. Spot Instances provide up to 90% discount compared to On-Demand Instances, making them the most cost-effective option.
-
Stateless & Disruption-Tolerant Applications: The applications are stateless and can tolerate disruptions. This is a perfect use case for Spot Instances, which can be interrupted with a 2-minute warning when AWS needs the capacity back.
-
Operational Overhead Minimization: The company wants to minimize operational overhead. Amazon EKS managed node groups handle:
- Node provisioning and lifecycle management
- Automatic node replacement if Spot Instances are interrupted
- Automatic patching and updates
- Integration with AWS services
-
Why not Option A (Spot Instances in EC2 Auto Scaling group):
- While Spot Instances are cost-effective, managing container orchestration on EC2 instances requires more operational overhead
- You would need to manage container scheduling, scaling, and orchestration yourself
- No built-in handling of Spot interruptions for containers
-
Why not Options C & D (On-Demand Instances):
- On-Demand Instances are significantly more expensive than Spot Instances
- They don't align with the cost minimization requirement
-
EKS Managed Node Groups with Spot Instances Benefits:
- Cost Optimization: Spot Instances provide maximum cost savings
- Reduced Operational Overhead: EKS manages the Kubernetes control plane, and managed node groups handle node lifecycle
- Automatic Recovery: When Spot Instances are interrupted, EKS managed node groups automatically replace them
- Container Orchestration: Built-in support for container deployment and management
Best Practice: For stateless, disruption-tolerant containerized applications where cost is a primary concern, using Spot Instances with EKS managed node groups provides the optimal balance of cost savings and reduced operational overhead.
Comments
Loading comments...