DOP-C02 · Question #130
A DevOps engineer is researching the least expensive way to implement an image batch processing cluster on AWS. The application cannot run in Docker containers and must run on Amazon EC2. The batch…
The correct answer is D. Use Amazon EFS for checkpoint data. Use EC2 Fleet to launch EC2 Spot Instances. Create a custom. The most cost-effective solution involves using Amazon EFS for shared checkpoint data and EC2 Fleet to provision highly discounted Spot Instances for the interruptible batch job. To further reduce costs, a custom AMI with the cluster software pre-installed should be used to…
Question
A DevOps engineer is researching the least expensive way to implement an image batch processing cluster on AWS. The application cannot run in Docker containers and must run on Amazon EC2. The batch job stores checkpoint data on an NFS volume and can tolerate interruptions. Configuring the cluster software from a generic EC2 Linux image takes 30 minutes. What is the MOST cost-effective solution?
Options
- AUse Amazon EFS for checkpoint data. To complete the job, use an EC2 Auto Scaling group and an
- BUse GlusterFS on EC2 instances for checkpoint data. To run the batch job, configure EC2 instances
- CUse Amazon EFS for checkpoint data. Use EC2 Fleet to launch EC2 Spot Instances, and utilize user
- DUse Amazon EFS for checkpoint data. Use EC2 Fleet to launch EC2 Spot Instances. Create a custom
How the community answered
(27 responses)- A26% (7)
- B15% (4)
- C7% (2)
- D52% (14)
Why each option
The most cost-effective solution involves using Amazon EFS for shared checkpoint data and EC2 Fleet to provision highly discounted Spot Instances for the interruptible batch job. To further reduce costs, a custom AMI with the cluster software pre-installed should be used to eliminate the 30-minute configuration time during instance launch.
While EFS is suitable, an EC2 Auto Scaling group might not exclusively use Spot Instances, and relying on user data for a 30-minute installation incurs costs for non-productive setup time, making it less cost-effective.
GlusterFS requires self-management on EC2, which increases operational overhead and may not be as cost-effective as managed EFS. Furthermore, this option doesn't specify using Spot Instances or custom AMIs for efficiency.
Although using EFS and EC2 Spot Instances via EC2 Fleet is cost-effective, employing user data for a 30-minute installation on every instance launch or replacement means paying for significant non-productive time, which is less optimal than using a pre-configured custom AMI.
This option combines Amazon EFS for managed NFS checkpoint data, EC2 Fleet to leverage highly cost-effective and interruptible Spot Instances, and a custom AMI with pre-installed cluster software. The custom AMI eliminates the 30-minute setup time, minimizing billing for non-productive instance time, making it the most cost-effective approach for frequent launches or interruptions.
Concept tested: Cost optimization for batch processing using Spot Instances, EFS, and custom AMIs
Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-instances.html
Topics
Community Discussion
No community discussion yet for this question.