300-415 · Question #430
Refer to the exhibit. Which configuration establishes connectivity between the 172.16.102.0/24 and the 192.168.0.0/24 subnet?
The correct answer is A. vrf definition 200 address-family ipv4 route-replicate from vrf global unicast bgp 100. The correct VRF route-replication syntax imports BGP routes from the global routing table into VRF 200, enabling connectivity between the two subnets.
Question
Exhibit
Options
- Avrf definition 200 address-family ipv4 route-replicate from vrf global unicast bgp 100
- Bvrf definition 200 address-family ipv4 route-replicate from vrf global unicast ospf 200
- Cvrf definition 200 global-address-family ipv4 route-replicate from vrf global unicast ospf 200
- Dvrf definition 200 global-address-family ipv4 route-replicate from vrf 200 unicast bgp 100
How the community answered
(26 responses)- A77% (20)
- B4% (1)
- C12% (3)
- D8% (2)
Why each option
The correct VRF route-replication syntax imports BGP routes from the global routing table into VRF 200, enabling connectivity between the two subnets.
The 'route-replicate from vrf global unicast bgp 100' command uses the correct IOS syntax under 'address-family ipv4' inside 'vrf definition 200', copying BGP 100 routes from the global VRF into VRF 200 and bridging the two subnets.
This option specifies 'ospf 200' as the source protocol, but the exhibit shows the global routing table uses BGP 100, so OSPF routes would not produce the needed connectivity.
'global-address-family ipv4' is not a valid IOS configuration keyword under 'vrf definition'; the correct keyword is 'address-family ipv4', making this command rejected by the parser.
Both the invalid 'global-address-family' keyword and the self-referential 'from vrf 200' source (replicating from VRF 200 into VRF 200) make this configuration syntactically and logically incorrect.
Concept tested: VRF route replication for inter-VRF connectivity
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-16/irg-xe-16-book/bgp-vrf-route-leaking.html
Topics
Community Discussion
No community discussion yet for this question.