Question 200
A validation test observes a broadcast traversing both multihomed access peers and then looping back into its origin segment due to missing split-horizon treatment. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Add split-horizon validation to multihomed rack commissioning and peer replacement checklists. Multihoming loop prevention depends on segment provenance rather than treating every flood path as independent.
Incorrect Answers
The alternative applies to another Juniper security situation: Two VTEPs advertise otherwise identical tenant prefixes, and an engineer reuses route identity assumptions that obscure how BGP can distinguish different originating advertisements. That situation concerns an EVPN route distinguisher makes BGP VPN NLRI unique across originating contexts; its purpose is distinct from policy-based route import membership. Its key condition is eVPN multihoming uses loop-prevention procedures to avoid forwarding eligible frames back into the Ethernet segment from which they originated.
Include endpoint move tests and MAC route convergence monitoring during host virtualization migrations. That concerns EVPN MAC mobility after virtual machine relocation, while the issue here is EVPN multihoming split-horizon behavior. Verify the supported ESI split-horizon and multihoming forwarding state, and correct mismatched peer membership before adding broader flood permissions.
Route targets mark EVPN VPN route membership and VRF import/export decisions; an established BGP session alone does not authorize all tenant routes. For this issue, verify the supported ESI split-horizon and multihoming forwarding state, and correct mismatched peer membership before adding broader flood permissions.