Cost-Effective Serverless Reporting with AWS Lambda
Short answer
B Run the program in AWS Lambda triggered by EventBridge to minimize cost and management overhead for infrequent, short tasks.
Question
Key Takeaways
Tests the ability to identify serverless options for infrequent workloads while avoiding infrastructure management overhead and interruption risks.
This question evaluates designing cost-optimized compute solutions for sporadic, short-duration tasks using AWS Lambda versus EC2 or ECS.
Common mistake: Choosing EC2 Spot Instances (D) due to lower hourly costs, ignoring that spot interruptions can delay critical monthly reports, or choosing ECS (C) which adds unnecessary complexity and cost for simple scripts.
Expert Analysis
Why the Answer Is Correct
The correct answer is B because AWS Lambda is designed for event-driven, short-running code execution without managing servers. Since the report generation takes less than 10 minutes and occurs only during a specific week each month, Lambda’s pay-per-use pricing model is significantly more cost-effective than keeping any infrastructure running continuously. It also provides the fastest startup time among the options, meeting the requirement for immediate report generation.
Why the Other Options Are Wrong
Option A (EC2 On-Demand) and Option D (EC2 Spot) are incorrect because they involve managing instances. While Spot is cheaper, it can be interrupted, risking delayed reports. Running them "continuously" during the last week of the month is wasteful and complex compared to Lambda. Option C (ECS) is valid but over-engineered; it requires setting up clusters, task definitions, and potentially paying for Fargate or EC2 capacity providers, which is more costly and complex than a simple Lambda function for this workload.
Community Comment Notes
Most learners correctly identified Lambda as the best fit. One user noted, "No infrastructure to manage. Love it," highlighting the operational simplicity. Another argued against ECS, stating it is "more cost more than B and is more complex." A dissenting view suggested Lambda might be too slow for multiple reports totaling over 10 minutes, but this overlooks Lambda's concurrency limits and typical cold start improvements, making it still the most efficient choice for this scale.
Exam Strategy
Always look for 'infrequent' or 'sporadic' triggers combined with short execution times (< 15 mins). These are prime indicators for AWS Lambda. Avoid managed services like ECS unless the workload requires long-running processes or specific container dependencies.
Frequently Asked Questions
Why not use EC2 Spot Instances for lower cost?
Is Lambda too expensive if reports take 10+ minutes total?
Community Votes
82% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 7 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 7
-
Scheldon 👍 2 Answered CAnswerC Option A and D are saying abount Running the EC2 instances countinously during the last week of each month which is not necessery from my understanding and will be not so cheap. Option B - 10min per report and we have couple of reports. So it looks like program is running for at least 20 min so in theory Lambda is not useful here Option C - ECS is allowing us to run Fargate which will allow to run program for more then 15 min, hence all reports which program is preparing should be created. I'm not sure but I think ECS API is allowing to run task on demand/request.
-
EdricHoang 👍 2 Answered B"The program takes less than 10 minutes to produce each report. The company rarely uses the program to generate reports outside of the last week of each month The company wants to generate reports in the least amount of time when the reports are requested." I go for B because of this
-
LeonSauveterre 👍 1 Answered BA - The task only runs for 10 minutes per report. Why would you need an EC2 instance? B - No infrastructure to manage. Love it. C - Works, but cost more than B and is more complex to set up than B. D - More cost-effective than A, but spot instances can be interrupted, probably causing delays in report generation.
-
Andy_09 👍 6Option B
-
asdfcdsxdfc 👍 2 Answered BB is corre ct
Show 2 more comments
-
agbor_tambe 👍 2 Answered BB is correct
-
NayeraB 👍 2 Answered BB..maybe?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →