Question 1
At a Junos EVPN-VXLAN leaf-spine fabric, a Junos specialist investigates this scenario: A tenant's EVPN route appears in another tenant's MAC table despite separate VLAN names. The tenant traffic must remain isolated across the overlay. For which use case is this feature the best match?
Explanation
Correct Answer
For a Junos EVPN-VXLAN leaf-spine fabric, this mechanism fits the requirement: Use EVPN route-target policy to control overlay route membership between tenants. The design is appropriate because: EVPN route targets determine which routes are imported into the relevant EVPN instances and tenant contexts. In this scenario, the observed issue is: A tenant's EVPN route appears in another tenant's MAC table despite separate VLAN names. The corresponding implementation is: Set approved export and import route targets for each isolated tenant EVPN service.
Incorrect Answers
VXLAN adds outer Ethernet, IP, UDP and VXLAN encapsulation overhead to tenant frames. The appropriate correction for the reported case is: Set approved export and import route targets for each isolated tenant EVPN service.
EVPN route type 3 carries inclusive multicast Ethernet tag information used to establish BUM replication membership. Fixing that different mechanism would not address the current root cause: EVPN route targets determine which routes are imported into the relevant EVPN instances and tenant contexts.
EVPN route type 2 advertises MAC reachability and can include associated IP information for hosts. Its verification is distinct from the reported condition: A tenant's EVPN route appears in another tenant's MAC table despite separate VLAN names. The tenant traffic must remain isolated across the overlay.