Least Operational Overhead for API Gateway Lambda

Answer Correct 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.

A company has a frontend ReactJS website that uses Amazon API Gateway to invoke REST APIs. The APIs perform the functionality of the website. A data engineer needs to write a Python script that can be occasionally invoked through API Gateway. The code must return results to API Gateway. Which solution will meet these requirements with the LEAST operational overhead?

  1. Deploy a custom Python script on an Amazon Elastic Container Service (Amazon ECS) cluster.
  2. Create an AWS Lambda Python function with provisioned concurrency.
  3. Deploy a custom Python script that can integrate with API Gateway on Amazon Elastic Kubernetes Service (Amazon EKS).
  4. 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. Correct Answer

Community Votes

B
83%
D
17%

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

Community Insight

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.

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.

Community Discussion (8 comments)

MephiboshethGumani 👍 2 Selected: D
D. 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.
royalrum 👍 1
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.
pypelyncar 👍 4 Selected: B
B and D are both ok. Still, since it says LEAST operational overhead, then keep it simple. B then.
HunkyBunky 👍 2 Selected: B
B - simple and clear
lucas_rfsb 👍 1 Selected: B
I would go in B
GiorgioGss 👍 1 Selected: B
Although D seems a good choice but the questions asks for "LEAST operational overhead" will result in B
damaldon 👍 1
Answ. 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
rralucard_ 👍 2 Selected: B
B. 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.

Comments & Corrections

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

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

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

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?

Provisioned Concurrency adds cost for idle capacity. For 'occasional' invocations, the cold start latency is acceptable, making standard Lambda (D) cheaper and less complex to manage.

Does EventBridge warming increase operational overhead?

No. It is a simple scheduled task. Managing ECS/EKS clusters or configuring Provisioned Concurrency involves significantly more ongoing operational maintenance.

More DEA-C01 FAQ →

Related Analysis

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide