SOA-C03 · Question #151
A SysOps administrator needs to give an existing AWS Lambda function access to an existing Amazon S3 bucket. Traffic between the Lambda function and the S3 bucket must not use public IP addresses…
The correct answer is D. Create an S3 interface endpoint. Change the Lambda function to use the new S3 DNS name. The requirement is that traffic from a VPC-connected Lambda to Amazon S3 must not use public IP addresses. The AWS-native way to keep traffic private is to use VPC endpoints, which provide private connectivity to supported AWS services without traversing the public internet…
Question
A SysOps administrator needs to give an existing AWS Lambda function access to an existing Amazon S3 bucket. Traffic between the Lambda function and the S3 bucket must not use public IP addresses. The Lambda function has been configured to run in a VPC. Which solution will meet these requirements?
Options
- AConfigure VPC sharing between the Lambda VPC and the S3 bucket.
- BAttach a transit gateway to the Lambda VPC to allow the Lambda function to connect to the S3
- CCreate a NAT gateway. Associate the NAT gateway with the subnet where the Lambda function
- DCreate an S3 interface endpoint. Change the Lambda function to use the new S3 DNS name.
How the community answered
(28 responses)- A7% (2)
- B14% (4)
- C4% (1)
- D75% (21)
Explanation
The requirement is that traffic from a VPC-connected Lambda to Amazon S3 must not use public IP addresses. The AWS-native way to keep traffic private is to use VPC endpoints, which provide private connectivity to supported AWS services without traversing the public internet. Among the options, creating an S3 VPC endpoint is the only approach that satisfies "no public IP addresses" while allowing access to the bucket. Option D is the best match because it explicitly configures an S3 endpoint and directs the Lambda function to use the endpoint-specific DNS name for private
Topics
Community Discussion
No community discussion yet for this question.