Question 580
At Skyline Energy Services, while verifying tenant isolation, the data center fabric team observes: An EVPN overlay tunnel forms but frames arrive under the wrong tenant identifier. What repeatable acceptance check would reduce recurrence?
Explanation
Correct Answer
At Skyline Energy Services, while verifying tenant isolation, for Skyline Energy Services, include the safeguard: Audit overlay encapsulation metadata during new tenant provisioning. It reduces repeat risk from the original mechanism and complements a validation of: Sample frames remain in the correct tenant across the remote leaves.
Incorrect Answers
At Skyline Energy Services, while verifying tenant isolation, this option proposes: Monitor unusual tenant MAC growth and audit service attachments. Using that approach would investigate A tenant's bridge MAC table grows with unexpected external endpoint addresses instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The VXLAN network identifier does not match the intended tenant service.
At Skyline Energy Services, while verifying tenant isolation, this option proposes: Use cross-tenant route leak checks in L3 overlay regression suites. The alternative focuses on The EVPN route-target import policy is too broad for the isolated IP-VRF, not on the stated defect. For this scenario the expected acceptance result would be: Sample frames remain in the correct tenant across the remote leaves.
At Skyline Energy Services, while verifying tenant isolation, this option proposes: Test ARP resolution and subsequent unicast after overlay configuration changes. It tests a different symptom: Two virtual machines share a subnet across leaves but ARP requests fail to discover their peers. For the observed case, the relevant distinction is The VXLAN network identifier does not match the intended tenant service, with verification: Sample frames remain in the correct tenant across the remote leaves.