A company has two data centers that are interconnected with multiple redundant links from different suppliers. The company Uses IP addresses that are within the 172.16,0.0/16 CIDR block. The company is running iBGP between the two data centers by using a private Autonomous System Number (ASN) and IGP. The company is moving toward a hybrid setup in which the company will initially use one VPC in the AWS Cloud. An AWS Direct Connect connection runs from the first data center to a Direct Connect gateway by using a private VIF. On the connection, the company advertises a summarized route for the 172.16.0.0/16 network. The company is planning to set up a second summarized route from the second data center to a different Direct Connect location. The company needs to implement a solution to route traffic to and from AWS through the first Direct Connect connection. The solution must use the second Direct Connect connection for failover purposes only. Which solution will meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Prepend the private ASN on the BGP announcements to AWS from the second data center. Add a second VIF in the first Direct Connect connection. Advertise the same network without any prepends from the first data center. Implement the same setup for the BGP announcement from AWS to the two data centers.
Most accepted answer: A. Prepend the private ASN on the BGP announcements to AWS from the second data center. Add a second VIF in the first Direct Connect connection. Advertise the same network without any prepends from the first data center. Implement the same setup for the BGP announcement from AWS to the two data centers.
Community votes: A=4, B=4, D=2
Selected Answer: A What does A do: DC2 (backup): ➕ Add AS_PATH prepend → Least preferred path DC1 (primary): 🚫 No prepend → Shortest preferred path upvoted 1 times
Selected Answer: A Prepend incoming and outgoing advertisements will do it. Local preference only affects outbound traffic not inbound upvoted 1 times
Selected Answer: B It's B https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#:~:text=Local%20preference%20BGP%20community%20tags%20are%20evaluated%20before%20any%20AS_PATH%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20attribute%2C%20and%20are%20evaluated%20in%20order%20from%20lowest%20to%20highest%20preference%20(where%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20highest%20preference%20is%20preferred) upvoted 2 times
Selected Answer: B B is the only one taking into consideration out (aws-dtc with prepend from the DTC) and in traffic (dtc-aws with local pref in the second DTC pointing to the primary). A: prepend is only be user from DTC to AWS, but not from AWS to DTC C: can't configure preference in a DXG D: talks about regions but there no region in the question, plus they are used for diferent purposes. Filtering/manupulation at the DTC, propagation at AWS upvoted 3 times
B is correct! To support failover across multiple AWS Direct Connect connections (active/passive), apply a community tag with a higher preference to the prefixes for the primary or active virtual interface and a lower preference to the prefixes for the backup or passive virtual interface. For example, set the BGP community tags for your primary or active virtual interfaces to 7224:7300 (high preference) and 7224:7100 (low preference) for your passive virtual interfaces. Local preference BGP community tags are evaluated before any AS_PATH attribute, and are evaluated in order from lowest to highest preference (where highest preference is preferred). upvoted 2 times