SOA-C03 · Question #132
A company deploys AWS infrastructure in a VPC that has an internet gateway. The VPC has public subnets and private subnets. An Amazon RDS for MySQL DB instance is deployed in a private subnet. An…
The correct answer is C. Deploy a NAT gateway. Update the private subnet's route table to route all traffic to the NAT D. Create an interface endpoint for Amazon SQS in the VPC. The Lambda function now runs inside a private subnet. To reach public AWS service endpoints like SQS over the internet, resources in private subnets need an egress path, typically via a NAT gateway. Adding a NAT gateway and updating the route table lets the Lambda function call…
Question
A company deploys AWS infrastructure in a VPC that has an internet gateway. The VPC has public subnets and private subnets. An Amazon RDS for MySQL DB instance is deployed in a private subnet. An AWS Lambda function uses the same private subnet and connects to the DB instance to query data. A developer modifies the Lambda function to require the function to publish messages to an Amazon Simple Queue Service (Amazon SQS) queue. After these changes, the Lambda function times out when it tries to publish messages to the SQS queue. Which solutions will resolve this issue? (Choose two.)
Options
- AReconfigure the Lambda function so that the function is not connected to the VPC.
- BDeploy an RDS proxy. Configure the Lambda function to connect to the DB instance through the
- CDeploy a NAT gateway. Update the private subnet's route table to route all traffic to the NAT
- DCreate an interface endpoint for Amazon SQS in the VPC.
- ECreate a gateway endpoint for Amazon SQS in the VPC.
How the community answered
(35 responses)- A3% (1)
- B6% (2)
- C80% (28)
- E11% (4)
Explanation
The Lambda function now runs inside a private subnet. To reach public AWS service endpoints like SQS over the internet, resources in private subnets need an egress path, typically via a NAT gateway. Adding a NAT gateway and updating the route table lets the Lambda function call the SQS public endpoint while still accessing the RDS instance in the private subnet. Alternatively, you can keep the subnet private and create an interface VPC endpoint for SQS. This gives the Lambda function a private, VPC-internal path to SQS without requiring internet
Topics
Community Discussion
No community discussion yet for this question.