How to Run Hourly Batch Containers on ECS with Least Management?

DVA-C02 By islever Editorial Last updated Aug 27, 2026

Short answer

C Define a task definition with an AWS Fargate launch type.

Question

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?

Add a capacity provider to manage instances.
Add an Amazon EC2 instance that runs the application.
Define a task definition with an AWS Fargate launch type. Correct Answer
Create an Amazon ECS cluster and add the managed node groups feature to run the application.

Key Takeaways

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.

Common mistake: 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.

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

These links open the official vendor documentation in a new tab.

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.

Community Votes

100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 6 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 6

tgv 👍 10 Answered C

Always ECS with Fargate for the least management.
ANDRES715 👍 4 Answered C

El desarrollador debe definir una definición de tarea con un tipo de lanzamiento de AWS Fargate. Al utilizar AWS Fargate, el desarrollador puede ejecutar la aplicación en un clúster de Amazon ECS sin tener que administrar la infraestructura subyacente. Fargate se encarga de aprovisionar y escalar automáticamente los recursos necesarios para ejecutar la tarea de la aplicación, lo que reduce la carga operativa y los gastos generales de administración. Al ejecutar la aplicación en AWS Fargate, el desarrollador puede aprovechar los recursos mínimos de CPU y RAM necesarios para la aplicación, lo que garantiza un uso eficiente de los recursos y minimiza los costos.
KarBiswa 👍 3 Answered C

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html
preachr 👍 1 Answered C

Fargate is suitable for the following workloads: - Large workloads that require low operational overhead - Small workloads that have an occasional burst - Tiny workloads - Batch workloads
Saudis 👍 1 Answered C

AWS Fargate Serverless Container management

Show 1 more comment

65703c1 👍 1 Answered C

C is the correct answer.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide