A company connects several VPCs to an on-premises datacenter (CIDR ) using an AWS Transit Gateway. The Transit Gateway has two attachments: an AWS Direct Connect Gateway (associated with a Transit VIF) and an AWS Site-to-Site VPN. Both attachments are configured to dynamically propagate routes to the Transit Gateway route table using BGP. During an operational review, a SysOps Administrator discovers that all outbound traffic from the VPCs to the on-premises network is traversing the Site-to-Site VPN connection instead of the Direct Connect path, despite the Direct Connect connection being fully operational and active. Which of the following is the most likely cause of this routing behavior?
- AThe dynamic BGP routes advertised over the Site-to-Site VPN have a shorter AS-Path length than those advertised over the Direct Connect Gateway, causing the Transit Gateway to prefer the VPN path.
- BThe VPC subnet route tables do not contain a route pointing to the Transit Gateway for the prefix, which defaults the outbound traffic to the VPN path.
- A static route for pointing to the Site-to-Site VPN attachment is configured in the Transit Gateway route table.Cevap
- DThe Transit Gateway route table is using a route evaluation order where dynamically propagated routes from VPN attachments take precedence over propagated routes from Direct Connect Gateway attachments.
Cevap
A static route for pointing to the Site-to-Site VPN attachment is configured in the Transit Gateway route table.
The correct answer identifies that a static route configured in a Transit Gateway route table always takes precedence over dynamically propagated routes. Since the static route targets the VPN attachment, it overrides the dynamic BGP route propagated by the Direct Connect Gateway, forcing all traffic to use the VPN connection.
Adım Adım Çözüm
Anahtar Kavram
Transit Gateway Route Evaluation Priority
Tahmini Süre:3m 0s