Answer-first summary for fast verification
Answer: Configure a single private VIF on each Direct Connect connection. Add both IPv4 and IPv6 peering to each private VIF. Configure the on- premises equipment with the AWS provided BGP neighbors to advertise IPv4 routes on the IPv4 peering and IPv6 routes on the IPv6 peering. Enable Bidirectional Forwarding Detection (BFD) on all peering sessions., Configure two private VIFs on each Direct Connect connection: one private VIF with the IPv4 address family and one private VIF with the IPv6 address family. Configure the on-premises equipment with the AWS provided BGP neighbors to advertise IPv4 routes on the IPv4 peering and IPv6 routes on the IPv6 peering. Enable Bidirectional Forwarding Detection (BFD) on all peering sessions.
To meet the requirements of providing highly available and reliable dual-stack connectivity between the company's office location and an AWS account, the solution must ensure that both IPv4 and IPv6 traffic can be routed efficiently and with minimal latency. This involves configuring separate Virtual Interfaces (VIFs) for IPv4 and IPv6 traffic on each Direct Connect connection to ensure that traffic is segregated and can be managed independently. Additionally, enabling Bidirectional Forwarding Detection (BFD) on all peering sessions enhances the reliability and speed of failover in case of a link failure. Option A suggests configuring a single private VIF on each Direct Connect connection with both IPv4 and IPv6 peering, which does not provide the necessary segregation of traffic types for optimal performance and reliability. Option C incorrectly suggests advertising IPv6 routes over an IPv4 peering, which is not a standard or efficient practice. Option D suggests advertising all routes on all peering sessions, which could lead to inefficiencies and potential routing issues. Option E suggests reducing the BGP hello timer, which is not directly related to ensuring dual-stack connectivity and could introduce unnecessary complexity. Therefore, the correct solutions are provided in Option B, which correctly segregates IPv4 and IPv6 traffic on separate VIFs and enables BFD for enhanced reliability, and Option A, despite its initial appearance, is also correct because it allows for dual-stack connectivity on a single VIF, which is a valid configuration supported by AWS for scenarios where traffic segregation is not a concern.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Which two solutions will ensure highly available and reliable dual-stack connectivity with low latency between the company's on-premises office and the AWS account, given that the on-premises router and VPC support dual-stack, and two AWS Direct Connect connections are already established?
A
Configure a single private VIF on each Direct Connect connection. Add both IPv4 and IPv6 peering to each private VIF. Configure the on- premises equipment with the AWS provided BGP neighbors to advertise IPv4 routes on the IPv4 peering and IPv6 routes on the IPv6 peering. Enable Bidirectional Forwarding Detection (BFD) on all peering sessions.
B
Configure two private VIFs on each Direct Connect connection: one private VIF with the IPv4 address family and one private VIF with the IPv6 address family. Configure the on-premises equipment with the AWS provided BGP neighbors to advertise IPv4 routes on the IPv4 peering and IPv6 routes on the IPv6 peering. Enable Bidirectional Forwarding Detection (BFD) on all peering sessions.
C
Configure a single private VIF and IPv4 peering on each Direct Connect connection. Configure the on-premises equipment with this peering to advertise the IPv6 routes in the same BGP neighbor configuration. Enable Bidirectional Forwarding Detection (BFD) on all peering sessions.
D
Configure two private VIFs on each Direct Connect connection: one private VIF with the IPv4 address family and one private VIF with the IPv6 address family. Configure the on-premises equipment with the AWS provided BGP neighbors to advertise all IPv4 routes and IPv6 routes on all peering sessions. Keep the Bidirectional Forwarding Detection (BFD) configuration unchanged.
E
Configure two private VIFs on each Direct Connect connection: one private VIF with the IPv4 address family and one private VIF with the IPv6 address family. Configure the on-premises equipment with the AWS provided BGP neighbors to advertise IPv4 routes on the IPv4 peering and IPv6 routes on the IPv6 peering. Reduce the BGP hello timer to 5 seconds on both the on-premises equipment and the Direct Connect configuration.