How to Run Hourly Batch Containers on ECS with Least Management?
A developer built an application that calls an external API to obtain data, processes the data, and saves the result to Amazon S3. The developer built a container image with all of the necessary dependencies to run the application as a container. The application runs locally and requires minimal CPU and RAM resources. The developer has created an Amazon ECS cluster. The developer needs to run the application hourly in Amazon Elastic Container Service (Amazon ECS). Which solution will meet these requirements with the LEAST amount of infrastructure management overhead?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests knowledge of ECS launch types, with the common trap being overcomplicating the architecture with EC2 or capacity providers when a fully managed, serverless option perfectly fits sporadic workloads.
This question evaluates your ability to select the appropriate Amazon ECS launch type for infrequent, low-resource containerized workloads. The community unanimously agrees that AWS Fargate eliminates underlying infrastructure management, making it the optimal choice for minimizing operational overhead.
Option A or D is frequently selected by candidates unfamiliar with Fargate, who mistakenly believe capacity providers or managed node groups eliminate infrastructure duties, but both still require OS-level patching and instance management.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
AWS Fargate is a serverless compute engine for containers that integrates natively with Amazon ECS. By removing the need to provision, configure, or scale virtual machines, it directly satisfies the requirement for the least amount of infrastructure management overhead. Since the application runs hourly with minimal resource demands, Fargate’s pay-per-second billing and automatic scaling align perfectly with these constraints.Why the Other Options Are Wrong
Options A, B, and D all depend on underlying EC2 infrastructure, which introduces ongoing responsibilities like operating system updates, security patching, capacity planning, and instance scaling. While capacity providers and managed node groups streamline cluster operations, they do not eliminate the administrative burden of managing the host layer. Option B explicitly requires manual EC2 management, which directly contradicts the goal of minimizing operational overhead.Community Comment Notes
Candidates consistently highlight Fargate’s serverless architecture as the definitive differentiator for this scenario. Comment [1] and [4] reinforce the rule of thumb to always default to Fargate for any ECS workload seeking minimal management. Comment [2] provides a clear breakdown confirming that Fargate automatically handles provisioning and scaling. Comment [3] correctly references the official AWS documentation detailing launch type comparisons.Official Reference
Exam Strategy
When exam questions emphasize "least management overhead," "serverless," or "intermittent/batch execution" for containerized apps, immediately prioritize AWS Fargate over EC2-backed alternatives. Match the workload frequency and resource profile to the service’s pricing model to avoid selecting unnecessarily complex infrastructure solutions.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →