Q59 — AWS SAA-C03 Ch.10

Question 59 of 100 | ← Chapter 10

Q659. A company collects and processes data from a vendor. The vendor stores its data in an Amazon RDS for MySQL database in the vendor's own AWS account. The company's VPC does not have an internet gateway, an AWS Direct Connect connection, or an AWS Site-to-Site VPN connection. The company needs to access the data that is in the vendor database.Which solution will meet this requirement?

Correct Answer: C. Instruct the vendor to create a Network Load Balancer (NLB). Place the NLB in front of the Amazon RDS for MySQL database.Use AWS PrivateLink to integrate the company's VPC and the vendor's VPC

Explanation

To enable the company to access the data stored in the vendor's Amazon RDS for MySQL database, without requiring an internet gateway, AWS Direct Connect, or an AWS Site-to-Site VPN connection, the solution that will meet this requirement is:C. Instruct the vendor to create a Network Load Balancer (NLB). Place the NLB in front of the Amazon RDS for MySQL database. Use AWS PrivateLink to integrate the company's VPC and the vendor's VPC.Here's the rationale behind this solution:\1. Network Load Balancer (NLB): Instructing the vendor to create an NLB and placing it in front of the Amazon RDS for MySQL database allows for load balancing and routing of incoming traffic to the database. The NLB acts as an entry point for accessing the database securely.\2. AWS PrivateLink: AWS PrivateLink enables private connectivity between VPCs and services without traversing the public internet. By using AWS PrivateLink, the company's VPC and the vendor's VPC can be securely connected, allowing access to the vendor's RDS database. Option A suggests instructing the vendor to sign up for the AWS Hosted Connection Direct Connect Program and using VPC peering. While VPC peering can establish connectivity between the VPCs, it does not address the need for access to the vendor's RDS database. The AWS Hosted Connection Direct Connect Program is not relevant to this scenario.Option B suggests configuring a client VPN connection between the company's VPC and the vendor's VPC. While VPN connections can provide secure connectivity, it requires additional configuration and management overhead, which is not desired in this scenario.Option D suggests using AWS Transit Gateway to integrate the VPCs and using VPC peering. While Transit Gateway can provide connectivity between multiple VPCs, it introduces additional complexity and might be an overcomplication for this scenario.Therefore, option C is the most appropriate solution as it leverages Network Load Balancer and AWS PrivateLink to securely access the vendor's RDS database without the need for an internet gateway, AWS Direct Connect, or a Site-to-Site VPN connection.