DVA-C02 · Question #391
A company launched an online portal to announce a new product that the company will release in 6 months. The portal requests that users enter an email address to receive communications about the produ
The correct answer is A. Expose the Lambda function by using function URLs. E. Expose the Lambda function by using Amazon API Gateway.. Lambda Function URLs (A) and Amazon API Gateway (E) are the correct choices because both are purpose-built, native ways to expose a Lambda function over HTTP with minimal configuration - Function URLs can be enabled directly on the Lambda function in seconds, and API Gateway inte
Question
A company launched an online portal to announce a new product that the company will release in 6 months. The portal requests that users enter an email address to receive communications about the product. The company needs to create a REST API that will store the email addresses in Amazon DynamoDB. A developer has created an AWS Lambda function that can store the email addresses. The developer will deploy the Lambda function by using the AWS Serverless Application Model (AWS SAM). The developer must provide access to the Lambda function over HTTP. Which solutions will meet these requirements with the LEAST additional configuration? (Choose two.)
Options
- AExpose the Lambda function by using function URLs.
- BExpose the Lambda function by using a Gateway Load Balancer.
- CExpose the Lambda function by using a Network Load Balancer.
- DExpose the Lambda function by using AWS Global Accelerator.
- EExpose the Lambda function by using Amazon API Gateway.
How the community answered
(25 responses)- A84% (21)
- B4% (1)
- C12% (3)
Explanation
Lambda Function URLs (A) and Amazon API Gateway (E) are the correct choices because both are purpose-built, native ways to expose a Lambda function over HTTP with minimal configuration - Function URLs can be enabled directly on the Lambda function in seconds, and API Gateway integrates seamlessly with AWS SAM via the AWS::Serverless::Api resource type (or implicitly via Events: Type: Api).
Why the distractors are wrong:
- B (Gateway Load Balancer): GLB is designed for routing traffic to third-party virtual appliances (firewalls, IDS/IPS) - it has no native Lambda integration and cannot expose Lambda over HTTP.
- C (Network Load Balancer): NLB operates at Layer 4 (TCP/UDP), not HTTP. While ALB (Application Load Balancer) can trigger Lambda, NLB cannot - and even ALB requires significantly more configuration than the two correct options.
- D (Global Accelerator): This is a network-layer performance service that improves latency by routing traffic through AWS's backbone - it's not an HTTP endpoint creator and doesn't integrate directly with Lambda.
Memory tip: Think "least configuration" = fewest AWS services involved. Function URLs require zero extra services (it's a Lambda feature), and API Gateway is the canonical SAM/serverless HTTP integration. Any answer involving a load balancer or accelerator should raise a red flag - those services solve different problems and add infrastructure complexity.
Topics
Community Discussion
No community discussion yet for this question.