Run Long-Running Scheduled Reports on AWS Fargate Without Idle Costs
A marketing team runs a report-generation process that must execute once per day at 02:00 UTC. It usually completes in 10315 minutes, but sometimes takes up to 45 minutes due to varying data volumes. They currently run the workload on an EC2 instance that is always on, which wastes money during off-hours. The team wants to minimize operational overhead and pay mainly for actual execution time.
What is the best architecture choice?
Quick Answer
The reasoning here centers on matching the compute model to how the workload actually behaves: a job that runs once a day for a variable amount of time, sometimes far longer than its typical case, is a poor fit for infrastructure that has to stay provisioned around the clock just to be ready for it. Running it as a containerized ECS task on Fargate means the compute only exists for the duration of that day's run, and billing is based on the vCPU and memory actually consumed during execution rather than on keeping an instance alive through the rest of the day when it's idle. EventBridge supplies the piece that makes this hands-off: it triggers the task at the required time without anyone needing to start or stop anything manually, and writing results to S3 gives the output a durable, cost-effective destination once the task finishes. This combination directly targets the two things called out in the scenario, minimizing operational overhead and paying mainly for actual execution time, without requiring the team to manage servers, patch an EC2 instance, or babysit its uptime. When you see a workload described as periodic, short relative to a full day, and currently running on an always-on instance purely out of convenience, that's the pattern that usually points to a scheduled, serverless container task rather than persistent compute.
⚠ Common exam trap
Test-takers frequently choose AWS Lambda without considering its 15-minute execution timeout, which cannot handle the 45-minute maximum runtime of this report-generation process.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use an EventBridge schedule to run the report as an Amazon ECS task on AWS Fargate and write results to S3.
Amazon ECS on AWS Fargate is the best choice because it eliminates the need to manage servers, scales automatically, and charges only for the vCPU and memory resources consumed during task execution. The EventBridge schedule triggers the Fargate task at 02:00 UTC, and the report is written to S3, which provides durable, cost-effective storage. This architecture minimizes operational overhead and cost by avoiding an always-on EC2 instance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a scheduled Amazon EC2 Auto Scaling group that keeps a minimum of one instance running at all times.
Why it's wrong here
Keeping a minimum instance reduces savings and still requires EC2 operational management.
When this WOULD be correct
A scheduled Auto Scaling group with a minimum of one instance is correct when the workload requires a persistent server (e.g., for real-time processing or stateful applications) and cost optimization is not the primary concern.
- ✓
Use an EventBridge schedule to run the report as an Amazon ECS task on AWS Fargate and write results to S3.
Why this is correct
Fargate allows the containerized job to run only when scheduled, so the team pays for task runtime instead of keeping an EC2 instance always on.
- ✗
Use AWS Lambda triggered by an EventBridge schedule at 02:00 UTC and write results to S3.
Why it's wrong here
Lambda has a 15-minute maximum runtime, so it cannot reliably handle a workload that may take up to 45 minutes.
When this WOULD be correct
A question where the task completes in under 15 minutes, requires no containerization, and benefits from Lambda's serverless, pay-per-execution model with minimal operational overhead.
- ✗
Use an EMR cluster provisioned daily with manual teardown to ensure the instance is always available before 02:00.
Why it's wrong here
EMR provisioning overhead and operational complexity are typically unnecessary for a daily report process.
When this WOULD be correct
This option would be correct if the workload involved large-scale data processing (e.g., running Spark or Hive jobs on terabytes of data) that requires a distributed cluster, and the team already has operational processes in place to manage cluster lifecycle automatically (e.g., using AWS Step Functions or Lambda for teardown). The question would emphasize cost savings by running only when needed, but not prioritize minimizing overhead.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Use an EventBridge schedule to run the report as an Amazon ECS task on AWS Fargate and write results to S3.Correct answer▾
Why this is correct
Fargate allows the containerized job to run only when scheduled, so the team pays for task runtime instead of keeping an EC2 instance always on.
✗Use a scheduled Amazon EC2 Auto Scaling group that keeps a minimum of one instance running at all times.Wrong answer — click to see why▾
Why this is wrong here
This option keeps an instance running at all times, which wastes money during off-hours and does not minimize operational overhead or pay mainly for actual execution time.
★ When this WOULD be the correct answer
A scheduled Auto Scaling group with a minimum of one instance is correct when the workload requires a persistent server (e.g., for real-time processing or stateful applications) and cost optimization is not the primary concern.
Why candidates choose this
Candidates may think Auto Scaling is cost-effective, but the 'minimum one instance' requirement contradicts the goal of paying only for execution time.
✗Use AWS Lambda triggered by an EventBridge schedule at 02:00 UTC and write results to S3.Wrong answer — click to see why▾
Why this is wrong here
AWS Lambda has a maximum execution timeout of 15 minutes, but the report-generation process can take up to 45 minutes, so Lambda cannot handle the entire workload.
★ When this WOULD be the correct answer
A question where the task completes in under 15 minutes, requires no containerization, and benefits from Lambda's serverless, pay-per-execution model with minimal operational overhead.
Why candidates choose this
Candidates see 'EventBridge schedule' and 'serverless' and assume Lambda is the simplest choice, overlooking the 15-minute timeout limit.
✗Use an EMR cluster provisioned daily with manual teardown to ensure the instance is always available before 02:00.Wrong answer — click to see why▾
Why this is wrong here
Provisioning an EMR cluster daily with manual teardown introduces significant operational overhead, which contradicts the requirement to minimize operational overhead. Additionally, EMR is designed for big data processing (e.g., Spark, Hive) and is overkill for a simple report-generation task, leading to higher costs and complexity.
★ When this WOULD be the correct answer
This option would be correct if the workload involved large-scale data processing (e.g., running Spark or Hive jobs on terabytes of data) that requires a distributed cluster, and the team already has operational processes in place to manage cluster lifecycle automatically (e.g., using AWS Step Functions or Lambda for teardown). The question would emphasize cost savings by running only when needed, but not prioritize minimizing overhead.
Why candidates choose this
Candidates may think EMR is suitable for any 'report generation' task, especially if they associate it with data processing. The manual teardown might seem like a simple way to save costs, but they overlook the operational burden and the fact that simpler services (like ECS Fargate) can handle the workload more efficiently.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A marketing team runs a report-generation process that must execute once per day at 02:00 UTC. It usually completes in 10315 minutes, but sometimes takes up to 45 minutes due to varying data volumes. They currently run the workload on an EC2 instance that is always on, which wastes money during off-hours. The team wants to minimize operational overhead and pay mainly for actual execution time. What is the best architecture choice?
medium- A.Use a scheduled Amazon EC2 Auto Scaling group that keeps a minimum of one instance running at all times.
- ✓ B.Use an EventBridge schedule to run the report as an Amazon ECS task on AWS Fargate and write results to S3.
- C.Use AWS Lambda triggered by an EventBridge schedule at 02:00 UTC and write results to S3.
- D.Use an EMR cluster provisioned daily with manual teardown to ensure the instance is always available before 02:00.
Why B: AWS Fargate allows the report-generation task to run as an Amazon ECS task triggered by an EventBridge schedule, eliminating the need for an always-on EC2 instance. Fargate charges only for the vCPU and memory resources consumed during the task's execution (typically 10–45 minutes), which aligns with the team's goal of minimizing operational overhead and paying mainly for actual execution time. Writing results to S3 provides durable, cost-effective storage without managing infrastructure.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.