Question 870
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An MPLS Layer 2 service has intermittent packet ordering or parsing issues because its endpoints disagree about use of the pseudowire control word. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
- Include control-word agreement and payload parsing in L2VPN acceptance tests.
- Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning.
- Test broadcast storm containment before admitting additional VPLS PEs.
Explanation
Correct Answer
B:Include control-word agreement and payload parsing in L2VPN acceptance tests. The control limits repetition of the described root condition: A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. During audits, confirm: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Incorrect Answers
A: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
C: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
D: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Question 871
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A remote PE withdraws a pseudowire label while the local PE still has transport reachability and attempts to forward customer frames. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires.
- Inspect EVPN route type 2 MAC/IP reachability and the remote MAC entry in the forwarding table.
- Compare remote label mapping and withdraw state against the targeted LDP session.
- Inspect attachment circuit type and the pseudowire's configured interworking mode.
Explanation
Correct Answer
C:Compare remote label mapping and withdraw state against the targeted LDP session. This check examines the decisive condition for LDP pseudowire label withdrawal before any unrelated changes are made. The underlying mechanism is: An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. The confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
Incorrect Answers
A: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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
B:Inspect EVPN route type 2 MAC/IP reachability and the remote MAC entry in the forwarding table. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
D:Inspect attachment circuit type and the pseudowire's configured interworking mode. This is a plausible diagnostic check 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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
Question 872
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A remote PE withdraws a pseudowire label while the local PE still has transport reachability and attempts to forward customer frames. Which routing or service mechanism best explains the reported behavior?
- VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires.
- EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding.
- Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical.
- An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP.
Explanation
Correct Answer
D:An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: A fresh valid service label mapping is present before forwarding is restored. The targeted correction is: Repair the remote service signaling and reestablish the expected VC label state.
Incorrect Answers
A: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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
B:EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
C:Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. This is a plausible protocol explanation 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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
Question 873
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A remote PE withdraws a pseudowire label while the local PE still has transport reachability and attempts to forward customer frames. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- A fresh valid service label mapping is present before forwarding is restored.
- Test frames cross the intended CE attachments once without repeated amplification.
- The remote PE receives the type 2 route and resolves the host MAC to the correct destination PE.
- The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Explanation
Correct Answer
A:A fresh valid service label mapping is present before forwarding is restored. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP.
Incorrect Answers
B: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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
C:The remote PE receives the type 2 route and resolves the host MAC to the correct destination PE. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
D:The CE-facing frames are correctly interpreted at the remote attachment after supported interworking. This is a plausible observed evidence 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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
Question 874
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A remote PE withdraws a pseudowire label while the local PE still has transport reachability and attempts to forward customer frames. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore the supported VPLS split-horizon or equivalent loop-free topology behavior.
- Repair the remote service signaling and reestablish the expected VC label state.
- Restore MAC learning and authorized type 2 route export within the EVPN instance.
- Use a supported pseudowire interworking configuration or adapt the service at the boundary.
Explanation
Correct Answer
B:Repair the remote service signaling and reestablish the expected VC label state. The change addresses the root behavior described here: An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. Verify success with: A fresh valid service label mapping is present before forwarding is restored.
Incorrect Answers
A: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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
C:Restore MAC learning and authorized type 2 route export within the EVPN instance. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
D:Use a supported pseudowire interworking configuration or adapt the service at the boundary. This is a plausible configuration or operational fix 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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
Question 875
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A remote PE withdraws a pseudowire label while the local PE still has transport reachability and attempts to forward customer frames. Which operational control would best prevent a recurrence of this exact failure mode?
- Test broadcast storm containment before admitting additional VPLS PEs.
- Track control-plane MAC routes alongside local bridge-table entries.
- Monitor service-label mapping events apart from core transport failures.
- Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning.
Explanation
Correct Answer
C:Monitor service-label mapping events apart from core transport failures. The control limits repetition of the described root condition: An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. During audits, confirm: A fresh valid service label mapping is present before forwarding is restored.
Incorrect Answers
A: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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
B:Track control-plane MAC routes alongside local bridge-table entries. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
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 LDP pseudowire label withdrawal and the confirming observation is: A fresh valid service label mapping is present before forwarding is restored.
Question 876
During a backbone POP acceptance review, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect EVPN RT values and the receiving EVI's route-import policy.
- Inspect Ethernet segment identifier, DF election result and per-VLAN forwarder eligibility.
- Inspect control-word negotiation and egress frame parsing for the specific pseudowire type.
- Inspect BGP L2VPN route distinguishers and the relevant service NLRI.
Explanation
Correct Answer
D:Inspect BGP L2VPN route distinguishers and the relevant service NLRI. This check examines the decisive condition for BGP Layer 2 VPN route distinguisher before any unrelated changes are made. The underlying mechanism is: BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. The confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Incorrect Answers
A:Inspect EVPN RT values and the receiving EVI's route-import policy. This is a plausible diagnostic check 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.
B: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 BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
C:Inspect control-word negotiation and egress frame parsing for the specific pseudowire type. This is a plausible diagnostic check 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 Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Question 877
During an overnight NOC investigation, 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 routing or service mechanism best explains the reported behavior?
- BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide.
- BGP EVPN route receipt and local service membership are separate; route targets control eligible imports.
- EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment.
- A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format.
Explanation
Correct Answer
A:BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Distinct RDs preserve separate advertisements and only correct tenant membership is imported. The targeted correction is: Assign unique appropriate service RDs and verify per-tenant RT imports.
Incorrect Answers
B:BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. This is a plausible protocol explanation 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: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 BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
D:A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. This is a plausible protocol explanation 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 Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Question 878
During a customer service restoration, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The EVI imports only its authorized remote MAC reachability when RT settings match.
- Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
- Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site.
- The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Explanation
Correct Answer
B:Distinct RDs preserve separate advertisements and only correct tenant membership is imported. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide.
Incorrect Answers
A:The EVI imports only its authorized remote MAC reachability when RT settings match. This is a plausible observed evidence 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: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 BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
D:The endpoints agree on control-word use and CE traffic is decoded correctly after label removal. This is a plausible observed evidence 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 Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Question 879
During an edge-to-core 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 response or focused corrective action best addresses this situation without changing unrelated components?
- Align the EVI's RT import/export conventions without opening other tenants.
- Align multihoming and DF-election configuration for the shared Ethernet segment.
- Assign unique appropriate service RDs and verify per-tenant RT imports.
- Align supported control-word settings at both pseudowire ends.
Explanation
Correct Answer
C:Assign unique appropriate service RDs and verify per-tenant RT imports. The change addresses the root behavior described here: BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. Verify success with: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Incorrect Answers
A:Align the EVI's RT import/export conventions without opening other tenants. This is a plausible configuration or operational fix 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.
B: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 BGP Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
D: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 Layer 2 VPN route distinguisher and the confirming observation is: Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests