Amazon DVA-C02 Exam - Topic 4 Question 41 Discussion

Actual exam question for Amazon's DVA-C02 exam

Question #: 41
Topic #: 4

A developer is creating an AWS Lambda function that needs network access to private resources in a VPC.

AAttach the Lambda function to the VPC through private subnets. Create a security group that allows network access to the private resources. Associate the security group with the Lambda function.

BConfigure the Lambda function to route traffic through a VPN connection. Create a security group that allows network access to the private resources. Associate the security group with the Lambda function.

CConfigure a VPC endpoint connection for the Lambda function. Set up the VPC endpoint to route traffic through a NAT gateway.

DConfigure an AWS PrivateLink endpoint for the private resources. Configure the Lambda function to reference the PrivateLink endpoint.

Show Suggested Answer

Suggested Answer: A

Comprehensive Detailed Step by Step Explanation with All AWS Developer Reference:

When you need to provide an AWS Lambda function access to private resources in a VPC, the most common and straightforward approach is to attach the Lambda function to a VPC via private subnets. Once the Lambda function is associated with the VPC, you need to configure appropriate security groups to control the access to the private resources.

Lambda with VPC Access: Lambda functions can be attached to private subnets in a VPC, allowing them to access resources like RDS, EC2, or internal services within that VPC.

Security Groups: A security group acts as a virtual firewall for the Lambda function, ensuring that it can access only the necessary resources and ports in the VPC.

Alternatives:

Option B involves routing traffic through a VPN, which adds unnecessary complexity and operational overhead compared to simply attaching the Lambda to the VPC.

Option C requires configuring a VPC endpoint and a NAT gateway, which can be complex and costly.

Option D refers to AWS PrivateLink, which is used to access services over private connections, but it's unnecessary in this scenario unless you need a cross-VPC connection.

Lambda functions in a VPC

by Jacinta at Oct 22, 2024, 11:09 PM

Limited Time Offer

25%

Off

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Alex

3 months ago

D is overkill for this scenario, just stick with A!

upvoted 0 times

...

Polly

3 months ago

C is interesting, but I prefer A for simplicity.

upvoted 0 times

...

Odette

3 months ago

Wait, can Lambda really connect to a VPC like that? Sounds tricky!

upvoted 0 times

...

Tu

4 months ago

I think B could work too, but it seems more complicated.

upvoted 0 times

...

Marcos

4 months ago

A is definitely the way to go for VPC access!

upvoted 0 times

...

Lonna

4 months ago

I think option D could be a good choice since PrivateLink is for accessing services privately. But I’m not confident if it’s the best approach for Lambda functions.

upvoted 0 times

...

Brynn

4 months ago

I vaguely recall something about VPC endpoints, but I'm not clear if they apply here. Option C might be relevant, but I need to double-check how NAT gateways work with Lambda.

upvoted 0 times

...

Nada

4 months ago

I feel like option B is a bit off because using a VPN for Lambda seems unnecessary. I think we just need to connect it directly to the VPC.

upvoted 0 times

...

Genevive

5 months ago

I remember we discussed how to attach Lambda functions to VPCs, so I think option A sounds right. But I'm not entirely sure about the security group details.

upvoted 0 times

...

Felicidad

5 months ago

Aha, option D with the PrivateLink endpoint is an interesting approach. I haven't used that before, but it could be a neat way to connect the Lambda function to the private resources. I'll need to research PrivateLink a bit more to see if that's the best fit.

upvoted 0 times

...

Dortha

5 months ago

Okay, I've got this. Option C with the VPC endpoint and NAT gateway seems like a good way to provide the Lambda function with secure network access to the private resources. I'll make sure to understand how the VPC endpoint works.

upvoted 0 times

...

Catalina

5 months ago

Hmm, I'm a bit unsure about this one. The VPN connection in option B seems like it could work, but I'm not sure if that's the most efficient solution. I'll need to review the VPC networking concepts to decide.

upvoted 0 times

...

Twanna

5 months ago

This looks like a straightforward VPC networking question. I think option A is the best approach - attaching the Lambda function to the VPC through private subnets and using a security group to control access.

upvoted 0 times

...

Jannette

1 year ago

I'm going with Option A. Anything that involves 'PrivateLink' just sounds like it's going to be a pain to set up. Keep it simple, folks!

upvoted 0 times

...

Alex

1 year ago

I'm leaning towards Option A as well. Gotta love it when the simple solution is also the right one. Plus, it's just more fun to say 'private subnets' than 'PrivateLink'.

upvoted 0 times

Latricia

1 year ago

Definitely, private subnets are the way to go for network access to private resources.

upvoted 0 times

...

Maurine

1 year ago

I agree, keeping it simple with private subnets is the way to go.

upvoted 0 times

...

Janessa

1 year ago

Option A sounds like the way to go. Private subnets for the win!

upvoted 0 times

...

Anabel

1 year ago

I agree with Stacey. Option A seems like the most straightforward solution for network access to private resources.

upvoted 0 times

...

Pamella

1 year ago

Option C is an interesting idea, but I'm not sure if the VPC endpoint and NAT gateway setup is necessary for this scenario. A seems like the most direct solution.

upvoted 0 times

Jaleesa

1 year ago

I agree, option A is the most straightforward approach.

upvoted 0 times

...

Marica

1 year ago

A seems like the most direct solution.

upvoted 0 times

...

Glendora

1 year ago

C) Configure a VPC endpoint connection for the Lambda function. Set up the VPC endpoint to route traffic through a NAT gateway.

upvoted 0 times

...

Dominque

1 year ago

A) Attach the Lambda function to the VPC through private subnets. Create a security group that allows network access to the private resources. Associate the security group with the Lambda function.

upvoted 0 times

...

Curtis

1 year ago

I agree with Yun. Option A is the clear winner here. Keeping everything within the VPC just makes sense for a use case like this.

upvoted 0 times

...

Yun

1 year ago

Option A seems like the way to go. Attaching the Lambda function to the VPC through private subnets and setting up a security group sounds like a straightforward approach.

upvoted 0 times

Galen

1 year ago

D) Option A provides a clear path for the Lambda function to access private resources securely.

upvoted 0 times

...

Hui

1 year ago

C) Definitely, setting up the Lambda function in the VPC with the right security group is key for network access.

upvoted 0 times

...

Na

1 year ago

B) I think option A is the best choice too. It's a simple and effective way to ensure network access.

upvoted 0 times

...

Kenneth

1 year ago

A) Attach the Lambda function to the VPC through private subnets. Create a security group that allows network access to the private resources. Associate the security group with the Lambda function.

upvoted 0 times

...

Stacey

1 year ago

I think option A is the best choice because it directly attaches the Lambda function to the VPC.

upvoted 0 times

...