SOA-C03 · Question #48
A company needs to ensure that an AWS Lambda function can access resources in a VPC in the company's account. The Lambda function requires access to third-party APIs that can be accessed only over…
The correct answer is D. Connect the Lambda function to a private subnet that has a route to a NAT gateway deployed in a. Lambda functions configured to run in a VPC require network egress to reach the internet for external APIs. A private subnet with a default route to a NAT gateway provides outbound internet access for the Lambda without exposing the Lambda’s resources to inbound internet…
Question
A company needs to ensure that an AWS Lambda function can access resources in a VPC in the company's account. The Lambda function requires access to third-party APIs that can be accessed only over the internet. Which action should a SysOps administrator take to meet these requirements?
Options
- AAttach an Elastic IP address to the Lambda function and configure a route to the internet gateway
- BConnect the Lambda function to a private subnet that has a route to the virtual private gateway of
- CConnect the Lambda function to a public subnet that has a route to the internet gateway of the
- DConnect the Lambda function to a private subnet that has a route to a NAT gateway deployed in a
How the community answered
(18 responses)- A6% (1)
- C11% (2)
- D83% (15)
Explanation
Lambda functions configured to run in a VPC require network egress to reach the internet for external APIs. A private subnet with a default route to a NAT gateway provides outbound internet access for the Lambda without exposing the Lambda’s resources to inbound internet traffic. This setup preserves the security of the VPC while enabling internet access for external API calls. The NAT gateway handles outbound connections on behalf of resources in the private subnet, ensuring stable and scalable access.
Topics
Community Discussion
No community discussion yet for this question.