SAA-C03 · Question #739
A company is building a data processing application that uses AWS Lambda functions. The application's Lambda functions need to communicate with an Amazon RDS DB instance that is deployed within a…
The correct answer is C. Deploy the Lambda functions inside the VPC. Attach a security group to the Lambda functions. Deploying Lambda functions inside the VPC and using security groups ensures that traffic between Lambda and the RDS instance stays within the VPC, providing secure, private communication. Allowing access on the RDS security group only from the Lambda security group enforces…
Question
A company is building a data processing application that uses AWS Lambda functions. The application’s Lambda functions need to communicate with an Amazon RDS DB instance that is deployed within a VPC in the same AWS account. Which solution meets these requirements in the MOST secure way?
Options
- AConfigure the DB instance to allow public access. Update the DB instance security group to allow
- BDeploy the Lambda functions inside the VPC. Attach a network ACL to the Lambda subnet.
- CDeploy the Lambda functions inside the VPC. Attach a security group to the Lambda functions.
- DPeer the Lambda default VPC with the VPC that hosts the DB instance to allow direct network
How the community answered
(23 responses)- A9% (2)
- B13% (3)
- C74% (17)
- D4% (1)
Explanation
Deploying Lambda functions inside the VPC and using security groups ensures that traffic between Lambda and the RDS instance stays within the VPC, providing secure, private communication. Allowing access on the RDS security group only from the Lambda security group enforces least-privilege network access.
Community Discussion
No community discussion yet for this question.