Question 230
While checking a production data center change, the team finds: An external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route. What observation best confirms the configuration now behaves correctly?
Explanation
Correct Answer
This observation validates evpn ip prefix type five advertisement: The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The corresponding corrective action is: Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF. Evidence about a different component does not establish the requested service outcome.
Incorrect Answers
The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics” would address that alternative cause, not the condition in this question: the routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.
“Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” responds to this separate finding: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. This question instead needs “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF”, so the alternative does not meet the stated condition.
The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” applies to that separate problem. The observed case is an external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route; choosing this alternative would address the wrong failure mode.