Explanation:
Lambda functions in a VPC need private subnets with a NAT gateway in a public subnet for outbound internet access to third-party APIs, while keeping the function's resources secure within the VPC.
Ultimate access to all questions.
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?
A
Attach an Elastic IP address to the Lambda function and configure a route to the internet gateway of the VPC.
B
Connect the Lambda function to a private subnet that has a route to the virtual private gateway of the VPC.
C
Connect the Lambda function to a public subnet that has a route to the internet gateway of the VPC.
D
Connect the Lambda function to a private subnet that has a route to a NAT gateway deployed in a public subnet of the VPC.
No comments yet.