You need to create a Private VIF for an existing AWS Direct Connect connection.
Which of the following is required during the configuration process? Please select the 2 correct options from below.
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - B and C.
If you look at the screen for creating a private VIF, this is how it looks like.
Here you can see that VLAN ID and the Virtual Private Gateway are part of the creation process.
Options A and D are incorrect since this is required when creating a public VIF.For more information on the creation of Virtual Interfaces, please refer to the below URL.
https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.htmlWhen configuring a Private VIF (Virtual Interface) for an existing AWS Direct Connect connection, the following two options are required:
VLAN ID: A VLAN (Virtual Local Area Network) ID is a numerical identifier that helps in creating a logical network segmentation within a physical network. VLAN tagging is used to separate different types of traffic over the same physical network. In the context of Direct Connect, a VLAN ID is required to create a dedicated logical connection between your network and AWS. You can choose any VLAN ID between 1 and 4094, with the exception of a few reserved VLAN IDs.
Prefixes to advertise: To advertise routes to the AWS network, you need to specify the prefixes you want to advertise over the Private VIF. Prefixes are IP address ranges that belong to your network. AWS uses Border Gateway Protocol (BGP) to exchange routing information between your network and AWS. You need to configure BGP on your router and advertise the prefixes you want to be reachable over the Private VIF. Once the prefixes are advertised, AWS updates its routing tables to direct traffic destined for those prefixes to your network.
Option A (The Peer Public IP) and Option C (Virtual Private Gateway) are not required during the configuration process of a Private VIF.