SAA-C03 · Question #223
A company hosts its applications in multiple private and public subnets in a VPC. The applications in the private subnets need to access an API. The API is available on the internet and is hosted in…
The correct answer is D. Implement an AWS Site-to-Site VPN connection between the VPC and the on-premises data. AWS Site-to-Site VPN is a cost-effective way to securely connect your on-premises data center with AWS resources. In this scenario: Applications in private subnetsrequire access to the API hosted in the on-premises data center. A Site-to-Site VPN connectionis a secure and…
Question
A company hosts its applications in multiple private and public subnets in a VPC. The applications in the private subnets need to access an API. The API is available on the internet and is hosted in the company's on-premises data center. A solutions architect needs to establish connectivity for applications in the private subnets. Which solution will meet these requirements MOST cost-effectively?
Options
- ACreate a transit gateway to connect the VPC to the on-premises network. Use the transit gateway
- BCreate a NAT gateway in the public subnet of the VPC. Use the NAT gateway to allow the private
- CEstablish an AWS PrivateLink connection to connect the VPC to the on-premises network. Use
- DImplement an AWS Site-to-Site VPN connection between the VPC and the on-premises data
How the community answered
(31 responses)- A16% (5)
- B6% (2)
- C6% (2)
- D71% (22)
Explanation
AWS Site-to-Site VPN is a cost-effective way to securely connect your on-premises data center with AWS resources. In this scenario: Applications in private subnetsrequire access to the API hosted in the on-premises data center. A Site-to-Site VPN connectionis a secure and cost-efficient option to route traffic between the VPC and on-premises resources. Transit GatewayandPrivateLinkare not cost-effective for this use case. NAT Gatewayonly provides internet access for private subnets, which is not suitable for reaching an on-premises resource.
Community Discussion
No community discussion yet for this question.