AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company needs to integrate with a third-party data feed. The data feed sends a webhook to notify an external service when new data is ready for consumption. A developer wrote an AWS Lambda function to retrieve data when the company receives a webhook callback. The developer must make the Lambda function available for the third party to call.
Which solution will meet these requirements with the MOST operational efficiency?
Other
Community
UAnonymous
A
Create a function URL for the Lambda function. Provide the Lambda function URL to the third party for the webhook.
B
Deploy an Application Load Balancer (ALB) in front of the Lambda function. Provide the ALB URL to the third party for the webhook.
C
Create an Amazon Simple Notification Service (Amazon SNS) topic. Attach the topic to the Lambda function. Provide the public hostname of the SNS topic to the third party for the webhook.
D
Create an Amazon Simple Queue Service (Amazon SQS) queue. Attach the queue to the Lambda function. Provide the public hostname of the SQS queue to the third party for the webhook.
Explanation:
Explanation
Correct Answer: A
Why Option A is correct:
- Function URLs provide a dedicated HTTP(S) endpoint for Lambda functions without requiring any additional AWS services.
- Operational efficiency is maximized because:
- No additional infrastructure to manage (no ALB, SNS, or SQS)
- Direct integration with Lambda
- Built-in authentication options (AWS_IAM or NONE)
- Simple setup and maintenance
- Cost-effective (no additional service charges)
Why other options are less efficient:
Option B (ALB):
- Requires deploying and managing an ALB
- Additional cost for ALB usage
- More complex setup with target groups
- Overkill for a simple webhook scenario
Option C (SNS):
- SNS topics don't have public hostnames for direct webhook calls
- Third party would need to use AWS SDK to publish to SNS
- Additional service to manage
- Not designed for direct HTTP webhook calls from external parties
Option D (SQS):
- SQS queues don't have public HTTP endpoints for direct posting
- Third party would need AWS credentials to send messages
- Designed for internal AWS service communication, not external webhooks
- Additional service to manage
Key Considerations:
- Lambda Function URLs were specifically designed for this use case
- Provide a simple, secure, and scalable way to expose Lambda functions via HTTP
- Support CORS configuration for cross-origin requests
- Can be configured with authentication (AWS_IAM) or open access
- Most operationally efficient solution with minimal management overhead
Comments
Loading comments...