Practice Test 3 | AWS Certified Solutions Architect Associate | SAA-C03 | Dumps | Mock Test
A company has an on-premises infrastructure which they want to extend to the AWS Cloud. There is a need to ensure that communication across both environments is possible over the Internet when initiated from on-premises. What should be set up on the on-premise side?
A. Create a VPC peering connection between the on-premises and the AWS Environment.
B. Create an AWS Direct connection between the on-premises and the AWS Environment.
C. Create a VPN connection between the on-premises and the AWS Environment.
D. Create a Virtual private gateway connection between the on-premises and the AWS Environment.
Explanation:
Answer – C
AWS Documentation mentions the following:
One can create a Virtual private connection to establish communication across both environments over the Internet.
For more information on Virtual private connection, please visit the following URL:
Option A is invalid because A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between them using private IPv4 addresses or IPv6 addresses. It is not used for connection between on-premise environment and AWS.
Option D is invalid because A virtual private gateway is the Amazon VPC side of a VPN connection. For the communication to take place between the on-premise servers to AWS EC2 instances with in the VPC, we need to set up the customer gateway at the on-premise location.
Note: The question says that “There is a need to ensure that communication across both environments is possible over the Internet.” AWS Direct Connect does not involve the Internet.
A VPC VPN Connection utilizes IPSec to establish encrypted network connectivity between your intranet and Amazon VPC over the Internet. VPN Connections can be configured in minutes and are a good solution if you have an immediate need, have low to modest bandwidth requirements, and can tolerate the inherent variability in Internet-based connectivity. AWS Direct Connect does not involve the Internet; instead, it uses dedicated, private network connections between your intranet and Amazon VPC.
Comments are closed, but trackbacks and pingbacks are open.