AWS Direct Connect Connection Setup: Requirements for On-Premises Data Center to AWS Partner Location

AWS Direct Connect Connection Setup

Prev Question Next Question

Question

You are in charge of setting up the AWS Direct Connect connection between your on-premises data center and an AWS Partner location.

You need to ensure that your network can support the connection.

What needs to be in check for this? Choose 3 answers from the options given below.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer - A, B and D.

Following are the requirements given in the AWS Documentation for AWS Direct Connect.

· Your network must use single mode fiber with a 1000BASE-LX (1310nm) transceiver for 1 gigabit Ethernet, or a 10GBASE-LR (1310nm) transceiver for 10 gigabit Ethernet.

· Auto-negotiation for the port must be disabled.

Port speed and full-duplex mode must be configured manually.

· 802.1Q VLAN encapsulation must be supported across the entire connection, including intermediate devices.

· Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication.

· (Optional) You can configure Bidirectional Forwarding Detection (BFD) on your network.

Asynchronous BFD is automatically enabled for AWS Direct Connect virtual interfaces, but will not take effect until you configure it on your router.

Option C is invalid because the network device must support BGP routing.

For more information on AWS Direct Connect, please refer to the below URL:

https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html

AWS Direct Connect is a service that allows you to establish a dedicated network connection between your on-premises infrastructure and AWS cloud. To ensure that your network can support this connection, there are certain prerequisites that need to be met.

The following three options are the prerequisites that must be in check to support AWS Direct Connect:

A. The network must have support for 802.1Q VLAN: AWS Direct Connect requires support for 802.1Q VLAN tagging, which is a protocol that allows multiple VLANs to coexist on a single physical switch interface. This enables the segregation of traffic between multiple virtual private clouds (VPCs) over a single physical interface. Hence, the network must have support for 802.1Q VLAN to configure VLAN tagging on the Direct Connect interface.

B. The network device must support BGP: AWS Direct Connect uses Border Gateway Protocol (BGP) as a routing protocol to exchange routing information between your on-premises data center and the AWS Partner location. Therefore, the network device connecting your on-premises infrastructure to the Direct Connect location must support BGP.

C. The network device must support Static Routing: In addition to BGP, AWS Direct Connect also supports static routing. If you prefer to use static routing, the network device connecting your on-premises infrastructure to the Direct Connect location must support it.

Option D, "Auto-negotiation for the port must be disabled for the network device" is incorrect. Auto-negotiation for the port should be enabled and it is not a prerequisite for AWS Direct Connect.

In summary, to ensure that your network can support the AWS Direct Connect connection, your network must have support for 802.1Q VLAN, the network device connecting your on-premises infrastructure to the Direct Connect location must support BGP and static routing.