Least Operational Overhead for API Gateway Lambda
Short answer
D Create an AWS Lambda function and ensure it is warm by scheduling an Amazon EventBridge rule to invoke the Lambda function every 5 minutes by using mock events.
Question
Key Takeaways
Tests understanding of serverless compute models and operational overhead trade-offs between ECS, EKS, and Lambda, specifically addressing the misconception that provisioned concurrency is required for performance.
Determining the optimal compute solution for occasional Python scripts invoked by Amazon API Gateway with minimal management. AWS Lambda is the correct answer (D) as it provides serverless execution without the need for provisioned concurrency or cold-start mitigation strategies.
Common mistake: Many candidates select Option B (Provisioned Concurrency) believing it ensures low latency, failing to recognize that this adds significant cost and operational complexity compared to standard on-demand Lambda invocation.
Expert Analysis
Why the Answer Is Correct
Option D is the correct choice because it leverages AWS Lambda's serverless nature, which inherently offers the least operational overhead. While the 'warm up' strategy via EventBridge might seem like additional configuration, it is a valid technique to mitigate cold starts for infrequently used functions. Compared to managing containers (ECS/EKS), Lambda requires zero infrastructure management. Although Option B also uses Lambda, Provisioned Concurrency incurs costs for idle capacity and adds billing complexity, making Option D simpler and more cost-effective for 'occasional' use cases where slight cold start latency is acceptable.
Why the Other Options Are Wrong
Options A and C involve deploying containers on ECS and EKS respectively. These require managing cluster configurations, scaling policies, security groups, and patching, resulting in high operational overhead. Option B introduces Provisioned Concurrency, which keeps instances warm at all times. This is unnecessary for 'occasionally invoked' functions and increases cost without reducing operational effort significantly compared to Option D.
Community Comment Notes
The community was split, but many correctly identified that while B seems faster, D is operationally simpler. One user noted, "I AM THINKING B. Dont u think provisionning concurrency add additional cost even when the function is not in active use, which is unnecessary for an occasionally invoked function." Another user argued, "Although D seems a good choice but the questions asks for 'LEAST operational overhead' will result in B," highlighting the confusion around what constitutes 'overhead' vs 'cost'. The key distinction is that D avoids the specific operational burden of managing provisioned capacity.
Official Reference
https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked for 'least operational overhead', always prioritize serverless options (Lambda, Bedrock) over managed services that require some config (Fargate, EKS). Be wary of options that add cost/features (like Provisioned Concurrency) unless performance requirements strictly mandate them.
Frequently Asked Questions
Why is Provisioned Concurrency (B) not the best answer?
Does EventBridge warming increase operational overhead?
Community Votes
83% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 8 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 8
-
pypelyncar 👍 4 Answered BB and D are both ok. Still, since it says LEAST operational overhead, then keep it simple. B then.
-
rralucard_ 👍 2 Answered BB. AWS Lambda functions can be easily integrated with Amazon API Gateway to create RESTful APIs. This integration allows API Gateway to directly invoke the Lambda function when the API endpoint is hit.
-
MephiboshethGumani 👍 2 Answered DD. Create an AWS Lambda function. Ensure that the function is warm by scheduling an Amazon EventBridge rule to invoke the Lambda function every 5 minutes by using mock events.
-
damaldon 👍 1Answ. B You can create a web API with an HTTP endpoint for your Lambda function by using Amazon API Gateway. API Gateway provides tools for creating and documenting web APIs that route HTTP requests to Lambda functions. You can secure access to your API with authentication and authorization controls. Your APIs can serve traffic over the internet or can be accessible only within your VPC. https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html
-
royalrum 👍 1I AM THINKING B. Dont u think provisionning concurrency add additional cost even when the function is not in active use, which is unnecessary for an occasionally invoked function.
Show 3 more comments
-
GiorgioGss 👍 1 Answered BAlthough D seems a good choice but the questions asks for "LEAST operational overhead" will result in B
-
HunkyBunky 👍 2 Answered BB - simple and clear
-
lucas_rfsb 👍 1 Answered BI would go in B
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →