Question 430
At Cedarview Rail Logistics, while checking a remote VTEP path, the data center fabric team observes: An EVPN route import policy permits the expected tenant prefix but blocks a new legitimate subnet. Which evidence directly validates the intended repair?
Explanation
Correct Answer
At Cedarview Rail Logistics, while checking a remote VTEP path, this result is the relevant closure evidence: The new prefix appears only in the intended tenant IP-VRF. It checks the effect of: Update the narrowly scoped import policy for the authorized subnet without broad route leakage. The underlying issue was: The route-target or prefix filter was not updated with the approved tenant expansion.
Incorrect Answers
At Cedarview Rail Logistics, while checking a remote VTEP path, this option proposes: Small and correctly sized large test frames cross VXLAN without fragmentation issues. This is a valid category of fabric maintenance for another scenario (An overlay forwarding issue affects only jumbo-sized packets), not the targeted action for Cedarview Rail Logistics. The distinction is the actual cause: The route-target or prefix filter was not updated with the approved tenant expansion.
At Cedarview Rail Logistics, while checking a remote VTEP path, this option proposes: The route selection and endpoint location converge on the intended VTEP. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: An unintended overlay attachment or duplicated MAC advertisement exists in the fabric. The evidence in the current case requires a different result: The new prefix appears only in the intended tenant IP-VRF.
At Cedarview Rail Logistics, while checking a remote VTEP path, this option proposes: A tenant test packet reaches its remote leaf using the intended VXLAN path. Using that approach would investigate BGP EVPN peers come up over the underlay but a remote VTEP remains unable to carry data traffic instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The route-target or prefix filter was not updated with the approved tenant expansion.