Selected Answer: B B and D are both fine. Still, since it says LEAST operational overhead, keep it simple. B then.

Selected Answer: B B. AWS Lambda functions can be easily integrated with Amazon API Gateway to create RESTful APIs. This integration lets API Gateway directly invoke the Lambda function when the API endpoint is hit.

Selected Answer: B B - simple and clear

Selected Answer: D D. Create an AWS Lambda function. Make sure the function stays warm by scheduling an Amazon EventBridge rule to invoke the Lambda function every 5 minutes using mock events.

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

Selected Answer: B Although D seems like a good choice, the question asks for "LEAST operational overhead" so the answer is B

Selected Answer: B I would choose B

I AM THINKING B. Dont u think provisionning concurrency add extra cost even when the function is not in active use, which is unnecessary for an occasionally invoked function.

Selected Answer: D The option with the least operational overhead is D. Create an AWS Lambda function with an EventBridge rule to keep it warm. Lambda handles infrastructure management automatically, and the warm-up approach addresses possible cold start issues while keeping minimal operational requirements compared to container-based solutions.

The question says “occasionally”, so warming it up every 5 minutes goes against the Well-Architected Framework.