Question 910
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A network team expects dynamic site discovery from a manually provisioned LDP VPLS service and cannot explain why new PEs are not automatically participating. Which operational control would best prevent a recurrence of this exact failure mode?
- Maintain a per-VPN site-ID allocation register.
- Keep service signaling type and required peers in the provisioning contract.
- Perform negative remote-site membership checks before accepting a VPLS service.
- Use positive and negative RT import tests for each new Layer 2 VPN tenant.
Explanation
Correct Answer
B:Keep service signaling type and required peers in the provisioning contract. The control limits repetition of the described root condition: VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. During audits, confirm: The new PE participates after the correct signaling and neighbor configuration is completed.
Incorrect Answers
A:Maintain a per-VPN site-ID allocation register. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is VPLS BGP versus LDP signaling and the confirming observation is: The new PE participates after the correct signaling and neighbor configuration is completed.
C:Perform negative remote-site membership checks before accepting a VPLS service. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS route target site leakage. BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused. In this scenario, however, the distinguishing issue is VPLS BGP versus LDP signaling and the confirming observation is: The new PE participates after the correct signaling and neighbor configuration is completed.
D:Use positive and negative RT import tests for each new Layer 2 VPN tenant. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP L2VPN route target mismatch. Route targets control membership and distribution of BGP-based L2VPN service advertisements. In this scenario, however, the distinguishing issue is VPLS BGP versus LDP signaling and the confirming observation is: The new PE participates after the correct signaling and neighbor configuration is completed.
Question 911
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A newly provisioned VPLS customer receives MAC floods from another customer's network after both instances import the same unintended route target. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect Ethernet segment identifier, DF election result and per-VLAN forwarder eligibility.
- Inspect whether VPLS uses BGP autodiscovery/signaling or explicit LDP neighbor configuration.
- Inspect VPLS route targets and the set of learned remote participants.
- Inspect BGP L2VPN route distinguishers and the relevant service NLRI.
Explanation
Correct Answer
C:Inspect VPLS route targets and the set of learned remote participants. This check examines the decisive condition for VPLS route target site leakage before any unrelated changes are made. The underlying mechanism is: BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused. The confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Incorrect Answers
A:Inspect Ethernet segment identifier, DF election result and per-VLAN forwarder eligibility. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
B:Inspect whether VPLS uses BGP autodiscovery/signaling or explicit LDP neighbor configuration. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS BGP versus LDP signaling. VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
D:Inspect BGP L2VPN route distinguishers and the relevant service NLRI. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Question 912
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A newly provisioned VPLS customer receives MAC floods from another customer's network after both instances import the same unintended route target. Which routing or service mechanism best explains the reported behavior?
- EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment.
- VPLS signaling design determines how remote sites are discovered and how service labels are exchanged.
- BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide.
- BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused.
Explanation
Correct Answer
D:BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned. The targeted correction is: Correct per-tenant route target assignment and BGP import policy.
Incorrect Answers
A:EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
B:VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS BGP versus LDP signaling. VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
C:BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Question 913
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A newly provisioned VPLS customer receives MAC floods from another customer's network after both instances import the same unintended route target. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
- Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site.
- The new PE participates after the correct signaling and neighbor configuration is completed.
- Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Explanation
Correct Answer
A:Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused.
Incorrect Answers
B:Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
C:The new PE participates after the correct signaling and neighbor configuration is completed. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS BGP versus LDP signaling. VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
D:Distinct RDs preserve separate advertisements and only correct tenant membership is imported. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Question 914
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A newly provisioned VPLS customer receives MAC floods from another customer's network after both instances import the same unintended route target. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Align multihoming and DF-election configuration for the shared Ethernet segment.
- Correct per-tenant route target assignment and BGP import policy.
- Assign unique appropriate service RDs and verify per-tenant RT imports.
- Use the chosen BGP or LDP signaling model consistently rather than mixing assumptions.
Explanation
Correct Answer
B:Correct per-tenant route target assignment and BGP import policy. The change addresses the root behavior described here: BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused. Verify success with: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Incorrect Answers
A:Align multihoming and DF-election configuration for the shared Ethernet segment. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
C:Assign unique appropriate service RDs and verify per-tenant RT imports. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
D:Use the chosen BGP or LDP signaling model consistently rather than mixing assumptions. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS BGP versus LDP signaling. VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Question 915
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A newly provisioned VPLS customer receives MAC floods from another customer's network after both instances import the same unintended route target. Which operational control would best prevent a recurrence of this exact failure mode?
- Fail over the DF during testing and check for duplicate frames or blackholes.
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
- Perform negative remote-site membership checks before accepting a VPLS service.
- Keep service signaling type and required peers in the provisioning contract.
Explanation
Correct Answer
C:Perform negative remote-site membership checks before accepting a VPLS service. The control limits repetition of the described root condition: BGP VPLS RT import membership can join unrelated sites into one Layer 2 broadcast domain if values are reused. During audits, confirm: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Incorrect Answers
A:Fail over the DF during testing and check for duplicate frames or blackholes. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
B:Audit VPN identifiers before consolidating L2VPN routes on shared reflectors. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
D:Keep service signaling type and required peers in the provisioning contract. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS BGP versus LDP signaling. VPLS signaling design determines how remote sites are discovered and how service labels are exchanged. In this scenario, however, the distinguishing issue is VPLS route target site leakage and the confirming observation is: Unrelated remote sites disappear from the VPN membership and their MACs are no longer learned.
Question 916
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A VPLS operator sees an extreme increase in broadcast and unknown-unicast frames after a customer connects a redundant unprotected Ethernet ring. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect EVPN type 3 inclusive multicast route exchange and associated flooding membership.
- Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters.
- Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires.
- Inspect customer attachment loops, MAC-flap counters and VPLS flood replication rates.
Explanation
Correct Answer
D:Inspect customer attachment loops, MAC-flap counters and VPLS flood replication rates. This check examines the decisive condition for VPLS root cause of broadcast storm before any unrelated changes are made. The underlying mechanism is: An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. The confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
Incorrect Answers
A:Inspect EVPN type 3 inclusive multicast route exchange and associated flooding membership. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN inclusive multicast route. EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
B:Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
C:Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
Question 917
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A VPLS operator sees an extreme increase in broadcast and unknown-unicast frames after a customer connects a redundant unprotected Ethernet ring. Which routing or service mechanism best explains the reported behavior?
- An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge.
- EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI.
- VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain.
- VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires.
Explanation
Correct Answer
A:An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Broadcast replication returns to normal after the customer loop is isolated or protected. The targeted correction is: Enforce customer loop controls and supported storm-control limits at the PE edge.
Incorrect Answers
B:EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN inclusive multicast route. EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
C:VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
D:VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
Question 918
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A VPLS operator sees an extreme increase in broadcast and unknown-unicast frames after a customer connects a redundant unprotected Ethernet ring. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Each authorized PE appears in the replication set and controlled BUM test traffic reaches the intended sites.
- Broadcast replication returns to normal after the customer loop is isolated or protected.
- MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
- Test frames cross the intended CE attachments once without repeated amplification.
Explanation
Correct Answer
B:Broadcast replication returns to normal after the customer loop is isolated or protected. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge.
Incorrect Answers
A:Each authorized PE appears in the replication set and controlled BUM test traffic reaches the intended sites. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN inclusive multicast route. EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
C:MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
D:Test frames cross the intended CE attachments once without repeated amplification. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
Question 919
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A VPLS operator sees an extreme increase in broadcast and unknown-unicast frames after a customer connects a redundant unprotected Ethernet ring. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore correct type 3 advertisement and service membership signaling.
- Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly.
- Enforce customer loop controls and supported storm-control limits at the PE edge.
- Restore the supported VPLS split-horizon or equivalent loop-free topology behavior.
Explanation
Correct Answer
C:Enforce customer loop controls and supported storm-control limits at the PE edge. The change addresses the root behavior described here: An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. Verify success with: Broadcast replication returns to normal after the customer loop is isolated or protected.
Incorrect Answers
A:Restore correct type 3 advertisement and service membership signaling. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN inclusive multicast route. EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
B:Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
D:Restore the supported VPLS split-horizon or equivalent loop-free topology behavior. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
Question 920
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A VPLS operator sees an extreme increase in broadcast and unknown-unicast frames after a customer connects a redundant unprotected Ethernet ring. Which operational control would best prevent a recurrence of this exact failure mode?
- Test BUM delivery separately from known-unicast MAC reachability.
- Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic.
- Test broadcast storm containment before admitting additional VPLS PEs.
- Require a loop-free attachment design before adding redundant customer trunks.
Explanation
Correct Answer
D:Require a loop-free attachment design before adding redundant customer trunks. The control limits repetition of the described root condition: An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. During audits, confirm: Broadcast replication returns to normal after the customer loop is isolated or protected.
Incorrect Answers
A:Test BUM delivery separately from known-unicast MAC reachability. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN inclusive multicast route. EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
B:Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
C:Test broadcast storm containment before admitting additional VPLS PEs. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is VPLS root cause of broadcast storm and the confirming observation is: Broadcast replication returns to normal after the customer loop is isolated or protected.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests