SOA-C02 · Question #544
A SysOps administrator is re-architecting an application. The SysOps administrator has moved the database from a public subnet, where the database used a public endpoint, into a private subnet to rest
The correct answer is A. Create an AWS PrivateLink interface endpoint for the Lambda function. Connect to the database. AWS Lambda now supports AWS PrivateLink which lets you create, manage, and invoke Lambda functions securely from inside your virtual private cloud (VPC) or on-premises data centers without exposing traffic to the public Internet. https://aws.amazon.com/blogs/aws/new-use-aws-priva
Question
A SysOps administrator is re-architecting an application. The SysOps administrator has moved the database from a public subnet, where the database used a public endpoint, into a private subnet to restrict access from the public network. After this change, an AWS Lambda function that requires read access to the database cannot connect to the database. The SysOps administrator must resolve this issue without compromising security. Which solution meets these requirements?
Options
- ACreate an AWS PrivateLink interface endpoint for the Lambda function. Connect to the database
- BConnect the Lambda function to the database VPC. Connect to the database using its private
- CAttach an IAM role to the Lambda function with read permissions to the database.
- DMove the database to a public subnet. Use security groups for secure access.
How the community answered
(20 responses)- A80% (16)
- B5% (1)
- C10% (2)
- D5% (1)
Explanation
AWS Lambda now supports AWS PrivateLink which lets you create, manage, and invoke Lambda functions securely from inside your virtual private cloud (VPC) or on-premises data centers without exposing traffic to the public Internet. https://aws.amazon.com/blogs/aws/new-use-aws-privatelink-to-access-aws-lambda-over-private-
Topics
Community Discussion
No community discussion yet for this question.