Pay-Per-Use: Run Scheduled Reports with AWS Lambda
An internal team runs a report-generation job once per day. It typically finishes in a few minutes, and even on its slowest days it still completes in under 15 minutes. The team wants to reduce operational overhead and pay primarily for actual runtime instead of keeping servers running 24/7. Which AWS approach best matches these goals?
Quick Answer
AWS Lambda triggered on a schedule is the right fit because the job's profile, a short daily task that reliably finishes in minutes and never exceeds 15 minutes even on its slowest runs, sits comfortably within what Lambda is built for: functions that run in response to a trigger, execute for a bounded time, and then stop, with billing tied only to that execution time rather than to any idle period in between. Using EventBridge to invoke the function at the required time removes the need for a server that sits running around the clock just to be available once a day, which is precisely the operational overhead and wasted spend the team wants to eliminate. The detail that even the slowest run stays under Lambda's 15-minute execution timeout is what makes this a safe fit rather than a risky one, since a job that occasionally ran long enough to approach or exceed that limit would need a different compute option instead. This scenario is a clean match for serverless functions specifically because the workload is short, infrequent, and has a predictable upper bound on runtime, unlike longer or more variable jobs that call for a different service. When a scenario describes a brief, infrequent job with a runtime that comfortably fits within a short execution window, and the goal is to cut idle costs and operational overhead, that pattern points to a scheduled Lambda function rather than persistent compute.
⚠ Common exam trap
Many exam-takers assume EC2 or Auto Scaling is needed for any scheduled job, overlooking that Lambda's 15-minute timeout and serverless pricing perfectly suit short, infrequent tasks, while the 'pay primarily for actual runtime' requirement explicitly points away from always-on compute.
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 AWS Lambda triggered by a schedule (for example, EventBridge) to run the report at the required time.
AWS Lambda, triggered by Amazon EventBridge (CloudWatch Events), is ideal for short-lived, infrequent jobs like this daily report. It eliminates idle server costs by running only when invoked, and the 15-minute execution timeout comfortably covers the job's maximum runtime. This serverless approach directly reduces operational overhead and aligns with a pay-per-use cost model.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy the job on EC2 instances and keep them running continuously for the daily schedule.
Why it's wrong here
Always-on EC2 instances increase cost and do not minimize operational overhead for short-lived jobs.
When this WOULD be correct
If the job required a persistent, stateful environment (e.g., large local storage, specific OS configurations) or needed to run multiple times per day with unpredictable latency demands, EC2 instances running continuously would be appropriate.
- ✓
Use AWS Lambda triggered by a schedule (for example, EventBridge) to run the report at the required time.
Why this is correct
Lambda runs on demand and charges for execution time, aligning spend with actual job runtime and reducing ops.
- ✗
Run the job in an RDS database using stored procedures scheduled by the database engine.
Why it's wrong here
RDS is not designed for general scheduled compute workloads like daily report generation.
When this WOULD be correct
If the question required processing large datasets directly within a database (e.g., complex aggregations on terabytes of data) and the team already had a running RDS instance for other purposes, using stored procedures could be efficient without additional compute overhead.
- ✗
Use an Auto Scaling group with a fixed minimum size of one instance and disable scaling.
Why it's wrong here
A fixed-size Auto Scaling group still requires instance management and does not fully match runtime-based billing.
When this WOULD be correct
A question where a workload requires a single EC2 instance to always be available (e.g., a legacy application that cannot be containerized or serverless) and must automatically recover from failure, with the goal of high availability rather than cost optimization.
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 AWS Lambda triggered by a schedule (for example, EventBridge) to run the report at the required time.Correct answer▾
Why this is correct
Lambda runs on demand and charges for execution time, aligning spend with actual job runtime and reducing ops.
✗Deploy the job on EC2 instances and keep them running continuously for the daily schedule.Wrong answer — click to see why▾
Why this is wrong here
Keeping EC2 instances running 24/7 incurs costs for idle time, contradicting the goal of paying primarily for actual runtime when the job completes in under 15 minutes daily.
★ When this WOULD be the correct answer
If the job required a persistent, stateful environment (e.g., large local storage, specific OS configurations) or needed to run multiple times per day with unpredictable latency demands, EC2 instances running continuously would be appropriate.
Why candidates choose this
Candidates may default to EC2 for any compute workload without considering serverless alternatives, overlooking the cost and operational overhead of idle instances.
✗Run the job in an RDS database using stored procedures scheduled by the database engine.Wrong answer — click to see why▾
Why this is wrong here
Running the job as stored procedures in RDS would still require a running database instance 24/7, incurring costs for idle time, and does not align with the goal of paying primarily for actual runtime.
★ When this WOULD be the correct answer
If the question required processing large datasets directly within a database (e.g., complex aggregations on terabytes of data) and the team already had a running RDS instance for other purposes, using stored procedures could be efficient without additional compute overhead.
Why candidates choose this
Candidates might think that using RDS stored procedures eliminates the need for separate compute resources, overlooking that the database instance itself must remain running continuously, incurring costs regardless of job execution.
✗Use an Auto Scaling group with a fixed minimum size of one instance and disable scaling.Wrong answer — click to see why▾
Why this is wrong here
An Auto Scaling group with a fixed minimum size of one instance keeps an EC2 instance running 24/7, which incurs costs for idle time and does not reduce operational overhead or pay-per-use runtime.
★ When this WOULD be the correct answer
A question where a workload requires a single EC2 instance to always be available (e.g., a legacy application that cannot be containerized or serverless) and must automatically recover from failure, with the goal of high availability rather than cost optimization.
Why candidates choose this
Candidates may think Auto Scaling automatically reduces costs, but a fixed minimum of one instance means the instance never scales in, so it runs continuously, failing to meet the 'pay primarily for actual runtime' requirement.
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
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
One of 302 original SAA-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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. An internal team runs a report-generation job once per day. It typically finishes in a few minutes, and even on its slowest days it still completes in under 15 minutes. The team wants to reduce operational overhead and pay primarily for actual runtime instead of keeping servers running 24/7. Which AWS approach best matches these goals?
easy- A.Deploy the job on EC2 instances and keep them running continuously for the daily schedule.
- ✓ B.Use AWS Lambda triggered by a schedule (for example, EventBridge) to run the report at the required time.
- C.Run the job in an RDS database using stored procedures scheduled by the database engine.
- D.Use an Auto Scaling group with a fixed minimum size of one instance and disable scaling.
Why B: AWS Lambda is the ideal choice because it is a serverless compute service that runs code only when triggered, aligning with the requirement to pay primarily for actual runtime. By using Amazon EventBridge (CloudWatch Events) to invoke the Lambda function on a daily schedule, the team eliminates the need to provision or manage servers, and the job's typical runtime of a few minutes (under 15 minutes, Lambda's maximum execution timeout) fits perfectly within Lambda's constraints.
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.