Multiple AWS DX Connections for Government Organization - Configuring Primary and Secondary Links

Configuring Primary and Secondary AWS DX Connections for Government Organization

Prev Question Next Question

Question

Multiple AWS DX Connections from 2 different locations are commissioned by a government organization to access web applications deployed in AWS cloud infrastructure.

Users are complaining of session interruption while accessing a legacy software deployed on EC2 instance in AWS VPC.

Further analysis shows an asymmetric traffic flow between users in the government offices & servers over both AWS DX links.

To avoid varied latency from both AWS DX links, the client wants a primary AWS DX connection as a preferred path to AWS & a secondary AWS DX connection should be a backup in case of primary link failure.

Which of the following additional configuration changes will meet this requirement?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Correct Answer - C.

Local Preference BGP Community Tag can be used to set route preferences for incoming traffic to the customer network.

Supported Local Preference BGP Community Tag are as follows.

1)7224:7100-Low preference.

2)7224:7200-Medium preference.

3)7224:7300-High preference.

In the above case, to prefer incoming traffic over the primary link, the client can add high preference Tag 7224:7300 for the primary link& tag 7224:7100 for the secondary link.

Option A is incorrect as having the same tag on both primary & secondary links will load balance the traffic.

Option B is incorrect as having medium preference 7224:7200 tag on the secondary link will prefer it over the primary link.

Option D is incorrect as since the high preference tag 7224:7300 is added to the secondary link, the secondary link will be preferred.

For more information on using BGP Community Tags with AWS Direct Connect, refer to the following URL.

https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html

To meet the client's requirement of a primary and secondary AWS Direct Connect (DX) connection for accessing web applications deployed in AWS cloud infrastructure, a configuration change is required. The configuration change is related to Border Gateway Protocol (BGP), which is used for routing traffic between the customer's on-premises network and the AWS cloud.

The BGP protocol can use Local Preference Community Tags to influence the selection of the path for outbound traffic. The Local Preference value is a non-transitive optional attribute that can be attached to BGP prefixes. It is used to select the best path among multiple paths to reach a destination. The path with the highest Local Preference value is preferred.

Based on the given scenario, there are two AWS DX connections from two different locations commissioned by a government organization to access web applications deployed in AWS cloud infrastructure. Users are complaining of session interruption while accessing a legacy software deployed on EC2 instance in AWS VPC. Further analysis shows an asymmetric traffic flow between users in the government offices and servers over both AWS DX links. The client wants a primary AWS DX connection as a preferred path to AWS, and a secondary AWS DX connection should be a backup in case of primary link failure.

To meet this requirement, we need to add Local Preference BGP Community Tags to the primary and secondary links. The value of the Local Preference Community Tags should be selected in such a way that the primary link has a higher Local Preference value than the secondary link. This will ensure that outbound traffic flows through the primary link by default, and if the primary link fails, traffic will be rerouted through the secondary link.

Option A: Add Local Preference BGP Community Tag 7224:7200 on the primary Link & Local Preference BGP Community Tag 7224:7200 on the secondary link. This option sets the same Local Preference value for both the primary and secondary links. Therefore, it does not meet the requirement of having a primary and a secondary link with different Local Preference values.

Option B: Add Local Preference BGP Community Tag 7224:7100 on the primary Link & Local Preference BGP Community Tag 7224:7200 on the secondary link. This option sets a lower Local Preference value for the primary link than the secondary link. Therefore, it does not meet the requirement of having a primary link with a higher Local Preference value than the secondary link.

Option C: Add Local Preference BGP Community Tag 7224:7300 on the primary Link & Local Preference BGP Community Tag 7224:7100 on the secondary link. This option sets a higher Local Preference value for the primary link and a lower Local Preference value for the secondary link. Therefore, it meets the requirement of having a primary link with a higher Local Preference value than the secondary link. This is the correct answer.

Option D: Add Local Preference BGP Community Tag 7224:7200 on the primary Link & Local Preference BGP Community Tag 7224:7300 on the secondary link. This option sets a higher Local Preference value for the secondary link than the primary link. Therefore, it does not meet the requirement of having a primary link with a higher Local Preference value than the secondary link.

In conclusion, the correct answer is option C: Add Local Preference BGP Community Tag 7224:7300 on the primary Link & Local Preference BGP Community Tag 7224:7100 on the secondary link.