Not Required Configuration for Public VIF in AWS Direct Connect
Question
When configuring a Public VIF for AWS Direct Connect, which of the following is not required in the configuration?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Answer-D.
Options A, B and C are incorrect since all of these are required when creating a Public VIF.The Virtual Private Gateway is only required when you are creating a Private VIF.Below is the screenshot of what is required when creating a Public VIF.For more information on creating a public VIF, one can visit the below URL.
https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html![, Create a Virtual Interface
‘You may choose to create a private or public virtua interface, Select the appropriate option below.
Private - A private virtual interface should be used to access an Amazon VPC using private IP addresses.
‘© Public - A public vtual interface can access all AWS public services (Including EC2, $3, and DynamoDB) using public IP addresses.
Define Your New Public Virtual Interface
This virtual interface will have access to AWS public services in all US regions. For more information, see the user guide.
Enter the name of your virtual interface. If youre creating a virtua interface for another account, youll need to provide the other AWS account ID. For more information about virtual interface ownership, see "Hosted.
Virtual interfaces’ in the AWS Direct Connect Getting Started Guide.
Connection: | dxcon-fava'fy7 (USWest!) #) I
Virtual Interface Name: ja
[e.My Vital interface]
Virtual Interface Owner: @My AWS Account Another AWS Account (i
Enter the VLAN ID, if not already supplied by your AWS Direct Connect partner, and the IP Addresses for your router interface and the AWS Direct Connect interface.
VLAN: O
Address family: IPV4 OIE
Your router peer IP: jo
‘Amazon router peer IP: ie
Before you can use your virtual interface, we must establish a BGP session. You must provide an ASN for your router and any prefixes you would lke to announce to AWS. You will also need an MDS key to
authenticate the BGP session. We can generate one for you, or you can supply your own.
BGP ASN: O
‘Auto-generate BGP key: © i
Prefixes you want to advertise: Jo
It may take up to 72 hours to verify that your IP prefixes are valid for use with Direct Connect.](https://eaeastus2.blob.core.windows.net/optimizedimages/static/images/AWS-Certified-Advanced-Networking-Specialty/answer/imgquestions_efzmic.png)
When configuring a Public VIF (Virtual Interface) for AWS Direct Connect, the following components are required:
A. VLAN ID: A VLAN ID is required for identifying the traffic flow between the customer's network and the AWS network. This VLAN ID must be unique for each Public VIF.
B. Router Peer IP: A router peer IP address is required to establish a BGP session between the customer's router and AWS. This IP address is typically provided by the Direct Connect service provider.
C. BGP ASN: A BGP ASN (Autonomous System Number) is required for exchanging routing information between the customer's router and the AWS network. The customer must use a unique ASN for their network, and AWS will provide a unique ASN for their network as well.
D. Virtual Private Gateway: A Virtual Private Gateway is a component in AWS that is required for establishing a VPN connection to the customer's on-premises network. However, it is not required for configuring a Public VIF.
Therefore, the correct answer to the question is D. Virtual Private Gateway.