SAA-C03 · Question #598
A company is migrating its data processing application to the AWS Cloud. The application processes several short-lived batch jobs that cannot be disrupted. Data is generated after each batch job is…
The correct answer is D. Deploy Amazon EC2 On-Demand Instances to run the batch jobs. Store the data in Amazon S3. To run non-disruptible, short-lived batch jobs at low cost and manage data accessed for 30 days then retained for 2 years, On-Demand instances combined with Amazon S3 Intelligent-Tiering provide a cost-effective and operationally efficient solution.
Question
A company is migrating its data processing application to the AWS Cloud. The application processes several short-lived batch jobs that cannot be disrupted. Data is generated after each batch job is completed. The data is accessed for 30 days and retained for 2 years. The company wants to keep the cost of running the application in the AWS Cloud as low as possible. Which solution will meet these requirements?
Options
- AMigrate the data processing application to Amazon EC2 Spot Instances. Store the data in
- BMigrate the data processing application to Amazon EC2 On-Demand Instances. Store the data in
- CDeploy Amazon EC2 Spot Instances to run the batch jobs. Store the data in Amazon S3
- DDeploy Amazon EC2 On-Demand Instances to run the batch jobs. Store the data in Amazon S3
How the community answered
(65 responses)- A3% (2)
- B9% (6)
- C6% (4)
- D82% (53)
Why each option
To run non-disruptible, short-lived batch jobs at low cost and manage data accessed for 30 days then retained for 2 years, On-Demand instances combined with Amazon S3 Intelligent-Tiering provide a cost-effective and operationally efficient solution.
Amazon EC2 Spot Instances can be interrupted, which violates the requirement that the batch jobs 'cannot be disrupted.'
While Amazon EC2 On-Demand Instances are suitable for non-disruptible jobs and S3 Glacier Deep Archive is cost-effective for long-term retention, manually transitioning data to S3 Glacier Deep Archive via lifecycle policies has more operational overhead than S3 Intelligent-Tiering, and Deep Archive has longer retrieval times if data unexpectedly needs to be accessed after 30 days.
Amazon EC2 Spot Instances can be interrupted, which violates the requirement that the batch jobs 'cannot be disrupted.'
Deploying Amazon EC2 On-Demand Instances ensures that the short-lived batch jobs run without interruption, fulfilling the core requirement for reliability. Storing the generated data in Amazon S3 Intelligent-Tiering automatically optimizes storage costs by moving objects between frequent access, infrequent access, and archive access tiers (including Deep Archive Access for objects not accessed for 180+ days) based on actual access patterns. This aligns perfectly with the requirement for data accessed for 30 days and retained for 2 years at the lowest possible cost with minimal operational overhead for managing lifecycle policies.
Concept tested: EC2 instance types and S3 storage classes for cost optimization
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering.html
Community Discussion
No community discussion yet for this question.