Question 880
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two customers reuse the same pseudowire site identifier and destination addressing, causing ambiguous service advertisements at a route reflector. Which operational control would best prevent a recurrence of this exact failure mode?
- Validate ESI consistency before enabling dual-homed production traffic.
- Run per-EVI negative and positive import checks during onboarding.
- Fail over the DF during testing and check for duplicate frames or blackholes.
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
Explanation
Correct Answer
D:Audit VPN identifiers before consolidating L2VPN routes on shared reflectors. The control limits repetition of the described root condition: BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. During audits, confirm: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Incorrect Answers
A:Validate ESI consistency before enabling dual-homed production traffic. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
B:Run per-EVI negative and positive import checks during onboarding. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN BGP route target not imported. BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. In this scenario, however, the distinguishing issue is BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
C: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 BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Question 881
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A BGP-signaled Layer 2 site learns peer service NLRI but will not join the intended customer VPN because the receiving RT filter does not match. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare RT export values and local import membership for the L2VPN instance.
- Inspect local and remote site IDs and the BGP L2VPN route connection mapping.
- Inspect BGP L2VPN route distinguishers and the relevant service NLRI.
- Inspect whether VPLS uses BGP autodiscovery/signaling or explicit LDP neighbor configuration.
Explanation
Correct Answer
A:Compare RT export values and local import membership for the L2VPN instance. This check examines the decisive condition for BGP L2VPN route target mismatch before any unrelated changes are made. The underlying mechanism is: Route targets control membership and distribution of BGP-based L2VPN service advertisements. The confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Incorrect Answers
B:Inspect local and remote site IDs and the BGP L2VPN route connection mapping. This is a plausible diagnostic check 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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
C: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
D: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Question 882
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A BGP-signaled Layer 2 site learns peer service NLRI but will not join the intended customer VPN because the receiving RT filter does not match. Which routing or service mechanism best explains the reported behavior?
- BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology.
- Route targets control membership and distribution of BGP-based L2VPN service advertisements.
- BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide.
- VPLS signaling design determines how remote sites are discovered and how service labels are exchanged.
Explanation
Correct Answer
B:Route targets control membership and distribution of BGP-based L2VPN service advertisements. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered. The targeted correction is: Align exact RT policies for the participating customer sites.
Incorrect Answers
A:BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. This is a plausible protocol explanation 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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
D: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Question 883
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A BGP-signaled Layer 2 site learns peer service NLRI but will not join the intended customer VPN because the receiving RT filter does not match. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
- Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
- The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
- Both peers advertise a matching ESI and remote control-plane state recognizes the multi-attached segment.
Explanation
Correct Answer
C:The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Route targets control membership and distribution of BGP-based L2VPN service advertisements.
Incorrect Answers
A:Each site advertises its planned unique identity and the remote connection mapping is unambiguous. This is a plausible observed evidence 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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
B: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
D:Both peers advertise a matching ESI and remote control-plane state recognizes the multi-attached segment. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Question 884
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A BGP-signaled Layer 2 site learns peer service NLRI but will not join the intended customer VPN because the receiving RT filter does not match. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Assign unique service site IDs and align site ranges according to the intended topology.
- Assign unique appropriate service RDs and verify per-tenant RT imports.
- Align supported control-word settings at both pseudowire ends.
- Align exact RT policies for the participating customer sites.
Explanation
Correct Answer
D:Align exact RT policies for the participating customer sites. The change addresses the root behavior described here: Route targets control membership and distribution of BGP-based L2VPN service advertisements. Verify success with: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Incorrect Answers
A:Assign unique service site IDs and align site ranges according to the intended topology. This is a plausible configuration or operational fix 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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
B: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
C:Align supported control-word settings at both pseudowire ends. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically Pseudowire control-word handling. A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. In this scenario, however, the distinguishing issue is BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Question 885
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A BGP-signaled Layer 2 site learns peer service NLRI but will not join the intended customer VPN because the receiving RT filter does not match. Which operational control would best prevent a recurrence of this exact failure mode?
- Use positive and negative RT import tests for each new Layer 2 VPN tenant.
- Maintain a per-VPN site-ID allocation register.
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
- Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning.
Explanation
Correct Answer
A:Use positive and negative RT import tests for each new Layer 2 VPN tenant. The control limits repetition of the described root condition: Route targets control membership and distribution of BGP-based L2VPN service advertisements. During audits, confirm: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Incorrect Answers
B: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
C: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 BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
D:Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically Layer 2 interworking mismatch. Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. In this scenario, however, the distinguishing issue is BGP L2VPN route target mismatch and the confirming observation is: The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
Question 886
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Two sites in the same BGP-signaled L2VPN were provisioned with identical site identifiers and the service fails to map remote connections predictably. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect duplicate MAC detection and mobility events before assuming a legitimate workload move.
- Inspect local and remote site IDs and the BGP L2VPN route connection mapping.
- Compare RT export values and local import membership for the L2VPN instance.
- Inspect Ethernet segment reachability advertisements and fast convergence or mass-withdraw behavior.
Explanation
Correct Answer
B:Inspect local and remote site IDs and the BGP L2VPN route connection mapping. This check examines the decisive condition for BGP L2VPN site ID collision before any unrelated changes are made. The underlying mechanism is: BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. The confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Incorrect Answers
A:Inspect duplicate MAC detection and mobility events before assuming a legitimate workload move. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
C:Compare RT export values and local import membership for the L2VPN instance. This is a plausible diagnostic check 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 BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
D:Inspect Ethernet segment reachability advertisements and fast convergence or mass-withdraw behavior. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Question 887
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Two sites in the same BGP-signaled L2VPN were provisioned with identical site identifiers and the service fails to map remote connections predictably. Which routing or service mechanism best explains the reported behavior?
- Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration.
- Route targets control membership and distribution of BGP-based L2VPN service advertisements.
- BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology.
- EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability.
Explanation
Correct Answer
C:BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Each site advertises its planned unique identity and the remote connection mapping is unambiguous. The targeted correction is: Assign unique service site IDs and align site ranges according to the intended topology.
Incorrect Answers
A:Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
B:Route targets control membership and distribution of BGP-based L2VPN service advertisements. This is a plausible protocol explanation 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 BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
D:EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Question 888
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two sites in the same BGP-signaled L2VPN were provisioned with identical site identifiers and the service fails to map remote connections predictably. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
- The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered.
- Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
- Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Explanation
Correct Answer
D:Each site advertises its planned unique identity and the remote connection mapping is unambiguous. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology.
Incorrect Answers
A:The duplicate source is corrected and MAC ownership stabilizes on one authorized site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
B:The receiver imports intended L2VPN NLRI while unrelated tenants' services remain filtered. This is a plausible observed evidence 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 BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
C:Remote forwarding moves away from the failed PE after the segment withdrawal or protection event. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Question 889
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two sites in the same BGP-signaled L2VPN were provisioned with identical site identifiers and the service fails to map remote connections predictably. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Assign unique service site IDs and align site ranges according to the intended topology.
- Resolve the duplicate MAC condition and use supported detection or suppression controls.
- Align exact RT policies for the participating customer sites.
- Restore the supported Ethernet segment failure signaling and backup forwarding path.
Explanation
Correct Answer
A:Assign unique service site IDs and align site ranges according to the intended topology. The change addresses the root behavior described here: BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. Verify success with: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Incorrect Answers
B:Resolve the duplicate MAC condition and use supported detection or suppression controls. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
C:Align exact RT policies for the participating customer sites. This is a plausible configuration or operational fix 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 BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
D:Restore the supported Ethernet segment failure signaling and backup forwarding path. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Question 890
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two sites in the same BGP-signaled L2VPN were provisioned with identical site identifiers and the service fails to map remote connections predictably. Which operational control would best prevent a recurrence of this exact failure mode?
- Alert on oscillating MAC addresses that exceed planned mobility behavior.
- Maintain a per-VPN site-ID allocation register.
- Use positive and negative RT import tests for each new Layer 2 VPN tenant.
- Test PE failure recovery with live MAC entries, not only a ping to the surviving PE.
Explanation
Correct Answer
B:Maintain a per-VPN site-ID allocation register. The control limits repetition of the described root condition: BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. During audits, confirm: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Incorrect Answers
A:Alert on oscillating MAC addresses that exceed planned mobility behavior. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
C: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 BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
D:Test PE failure recovery with live MAC entries, not only a ping to the surviving PE. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests