Question 530
At Southridge Health Systems, while verifying tenant isolation, the data center fabric team observes: A leaf receives an EVPN route but traffic goes to a tenant's wrong MAC-VRF. What test result proves the affected fabric function now works?
Explanation
Correct Answer
At Southridge Health Systems, while verifying tenant isolation, this result is the relevant closure evidence: The intended MAC-VRF learns only its approved remote MAC and IP routes. It checks the effect of: Review EVPN import and export route targets and correct the tenant assignment. The underlying issue was: The received overlay route target is imported into an unintended service context.
Incorrect Answers
At Southridge Health Systems, while verifying tenant isolation, this option proposes: The route selection and endpoint location converge on the intended VTEP. It tests a different symptom: A remote server's MAC is learned through two unexpected VTEPs. For the observed case, the relevant distinction is The received overlay route target is imported into an unintended service context, with verification: The intended MAC-VRF learns only its approved remote MAC and IP routes.
At Southridge Health Systems, while verifying tenant isolation, this option proposes: A test endpoint on each leaf exchanges tenant frames in the intended L2 service. The option describes a different failure mode: Two remote leaves use different VNI values for the same intended tenant broadcast domain. It would address The L2 EVPN service-to-VNI mapping is inconsistent across participants, but here the case reports A leaf receives an EVPN route but traffic goes to a tenant's wrong MAC-VRF. The current required evidence is: The intended MAC-VRF learns only its approved remote MAC and IP routes.
At Southridge Health Systems, while verifying tenant isolation, this option proposes: A controlled ARP request resolves the remote endpoint and unicast traffic succeeds. That choice would be more relevant when this different symptom occurs: Two virtual machines share a subnet across leaves but ARP requests fail to discover their peers. The present scenario instead points to: The received overlay route target is imported into an unintended service context. The correct resolution has its own verification outcome: The intended MAC-VRF learns only its approved remote MAC and IP routes.