Question 760
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: VPNv4 control-plane shows a remote prefix with the correct-looking RT, but the local VRF routing table excludes it due to an extra import policy. Which operational control would best prevent a recurrence of this exact failure mode?
- Test CE-to-VPN advertisements independently of CE-PE session status.
- Verify each negotiated address family during VPN onboarding.
- Require service-route and labeled-transport checks as separate release gates.
- Record RT and policy reasons for each rejected customer service route.
Explanation
Correct Answer
D:Record RT and policy reasons for each rejected customer service route. The control limits repetition of the described root condition: RT association is necessary for many VPN designs, but additional VRF policy can still reject or modify a candidate route. During audits, confirm: The route passes the full import policy chain and appears in the intended customer table.
Incorrect Answers
A:Test CE-to-VPN advertisements independently of CE-PE session status. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically CE EBGP policy export. A usable CE-PE peering is distinct from approving VRF routes for VPNv4 distribution. In this scenario, however, the distinguishing issue is Imported VPN route rejected from local VRF and the confirming observation is: The route passes the full import policy chain and appears in the intended customer table.
B:Verify each negotiated address family during VPN onboarding. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically MP-BGP VPNv4 family absent. An established BGP session for IPv4 unicast does not automatically enable VPNv4 address-family exchange. In this scenario, however, the distinguishing issue is Imported VPN route rejected from local VRF and the confirming observation is: The route passes the full import policy chain and appears in the intended customer table.
C:Require service-route and labeled-transport checks as separate release gates. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically MPLS transport label missing. A usable L3VPN data path requires provider transport reachability in addition to customer service route advertisements. In this scenario, however, the distinguishing issue is Imported VPN route rejected from local VRF and the confirming observation is: The route passes the full import policy chain and appears in the intended customer table.
Question 761
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Two service providers need to exchange customer VRF reachability across an AS border using a simple per-customer interface relationship. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect whether the ASBRs have corresponding per-VRF interfaces and ordinary interconnection routing.
- Inspect negotiated VPNv6 address family and IPv6-specific VRF route policy.
- Inspect the VPN route's BGP next hop and the IGP/MPLS path to that specific loopback.
- Compare hub/spoke route-target import/export policy with the route distribution topology.
Explanation
Correct Answer
A:Inspect whether the ASBRs have corresponding per-VRF interfaces and ordinary interconnection routing. This check examines the decisive condition for Interprovider VPN option A before any unrelated changes are made. The underlying mechanism is: Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core. The confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Incorrect Answers
B:Inspect negotiated VPNv6 address family and IPv6-specific VRF route policy. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically IPv6 VPN reachability. IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
C:Inspect the VPN route's BGP next hop and the IGP/MPLS path to that specific loopback. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically VPN next-hop not reachable. VPN control-plane reachability is not enough; the remote PE next hop must resolve to a usable provider transport path. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
D:Compare hub/spoke route-target import/export policy with the route distribution topology. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically VPN hub-and-spoke controlled import. VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Question 762
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two service providers need to exchange customer VRF reachability across an AS border using a simple per-customer interface relationship. Which routing or service mechanism best explains the reported behavior?
- L3VPN separation starts at the correct PE customer interface association with the VRF.
- Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core.
- IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success.
- VPN control-plane reachability is not enough; the remote PE next hop must resolve to a usable provider transport path.
Explanation
Correct Answer
B:Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants. The targeted correction is: Configure controlled per-customer ASBR-to-ASBR VRF peering where scale permits.
Incorrect Answers
A:L3VPN separation starts at the correct PE customer interface association with the VRF. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically Customer CE interface mapped wrong VRF. L3VPN separation starts at the correct PE customer interface association with the VRF. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
C:IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically IPv6 VPN reachability. IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
D:VPN control-plane reachability is not enough; the remote PE next hop must resolve to a usable provider transport path. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically VPN next-hop not reachable. VPN control-plane reachability is not enough; the remote PE next hop must resolve to a usable provider transport path. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Question 763
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two service providers need to exchange customer VRF reachability across an AS border using a simple per-customer interface relationship. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The customer prefix appears only in the intended VRF table and not as an accidental global route.
- IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE.
- The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
- The remote PE loopback is reachable through labeled transport and the VPN route becomes usable.
Explanation
Correct Answer
C:The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core.
Incorrect Answers
A:The customer prefix appears only in the intended VRF table and not as an accidental global route. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Customer CE interface mapped wrong VRF. L3VPN separation starts at the correct PE customer interface association with the VRF. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
B:IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically IPv6 VPN reachability. IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
D:The remote PE loopback is reachable through labeled transport and the VPN route becomes usable. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically VPN next-hop not reachable. VPN control-plane reachability is not enough; the remote PE next hop must resolve to a usable provider transport path. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Question 764
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two service providers need to exchange customer VRF reachability across an AS border using a simple per-customer interface relationship. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Coordinate unique RT conventions or explicit RT translation across the boundary.
- Attach the CE logical interface to the correct instance type and VRF.
- Enable the supported IPv6 VPN family with matching route targets and forwarding.
- Configure controlled per-customer ASBR-to-ASBR VRF peering where scale permits.
Explanation
Correct Answer
D:Configure controlled per-customer ASBR-to-ASBR VRF peering where scale permits. The change addresses the root behavior described here: Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core. Verify success with: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Incorrect Answers
A:Coordinate unique RT conventions or explicit RT translation across the boundary. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Inter-AS route target collision. Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
B:Attach the CE logical interface to the correct instance type and VRF. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Customer CE interface mapped wrong VRF. L3VPN separation starts at the correct PE customer interface association with the VRF. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
C:Enable the supported IPv6 VPN family with matching route targets and forwarding. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically IPv6 VPN reachability. IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Question 765
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two service providers need to exchange customer VRF reachability across an AS border using a simple per-customer interface relationship. Which operational control would best prevent a recurrence of this exact failure mode?
- Account for per-VPN interconnect growth before selecting option A for hundreds of tenants.
- Exchange tenant RT inventories and negative-route import tests before turn-up.
- Include interface-to-tenant mapping validation in turn-up checklists.
- Verify IPv4 and IPv6 VPN route sets separately during dual-stack expansion.
Explanation
Correct Answer
A:Account for per-VPN interconnect growth before selecting option A for hundreds of tenants. The control limits repetition of the described root condition: Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core. During audits, confirm: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Incorrect Answers
B:Exchange tenant RT inventories and negative-route import tests before turn-up. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Inter-AS route target collision. Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
C:Include interface-to-tenant mapping validation in turn-up checklists. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Customer CE interface mapped wrong VRF. L3VPN separation starts at the correct PE customer interface association with the VRF. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
D:Verify IPv4 and IPv6 VPN route sets separately during dual-stack expansion. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically IPv6 VPN reachability. IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. In this scenario, however, the distinguishing issue is Interprovider VPN option A and the confirming observation is: The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Question 766
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A provider wants to exchange VPN-labeled routes at ASBRs without maintaining a separate physical or logical VRF connection for each customer. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect each VRF's route distinguisher and the resulting VPN-IPv4 prefix identifiers.
- Inspect VPN route/label exchange support between ASBRs and route-target control.
- Check which prefixes and RTs are imported into the shared-services and tenant VRFs.
- Compare hub/spoke route-target import/export policy with the route distribution topology.
Explanation
Correct Answer
B:Inspect VPN route/label exchange support between ASBRs and route-target control. This check examines the decisive condition for Interprovider VPN option B before any unrelated changes are made. The underlying mechanism is: Interprovider option B can exchange labeled VPNv4 routes between ASBRs to extend VPNs across provider domains. The confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Incorrect Answers
A:Inspect each VRF's route distinguisher and the resulting VPN-IPv4 prefix identifiers. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically Route distinguisher for overlapping customer routes. A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
C:Check which prefixes and RTs are imported into the shared-services and tenant VRFs. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically VRF route leaking to shared service. Shared service access requires deliberate selective route leaking, not global RT membership across all tenants. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
D:Compare hub/spoke route-target import/export policy with the route distribution topology. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically VPN hub-and-spoke controlled import. VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Question 767
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A provider wants to exchange VPN-labeled routes at ASBRs without maintaining a separate physical or logical VRF connection for each customer. Which routing or service mechanism best explains the reported behavior?
- A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import.
- Shared service access requires deliberate selective route leaking, not global RT membership across all tenants.
- Interprovider option B can exchange labeled VPNv4 routes between ASBRs to extend VPNs across provider domains.
- VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches.
Explanation
Correct Answer
C:Interprovider option B can exchange labeled VPNv4 routes between ASBRs to extend VPNs across provider domains. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control. The targeted correction is: Establish the supported labeled VPN inter-AS peering with strict import/export policies.
Incorrect Answers
A:A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically Route distinguisher for overlapping customer routes. A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
B:Shared service access requires deliberate selective route leaking, not global RT membership across all tenants. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically VRF route leaking to shared service. Shared service access requires deliberate selective route leaking, not global RT membership across all tenants. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
D:VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically VPN hub-and-spoke controlled import. VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Question 768
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A provider wants to exchange VPN-labeled routes at ASBRs without maintaining a separate physical or logical VRF connection for each customer. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The core holds separate VPNv4 routes with distinct RDs for the identical customer IPv4 prefix.
- Each tenant reaches the authorized DNS prefix but cannot install another tenant's unrelated prefixes.
- Branch VRFs lack direct peer branch routes while the hub has the intended forwarding reachability.
- The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Explanation
Correct Answer
D:The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Interprovider option B can exchange labeled VPNv4 routes between ASBRs to extend VPNs across provider domains.
Incorrect Answers
A:The core holds separate VPNv4 routes with distinct RDs for the identical customer IPv4 prefix. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Route distinguisher for overlapping customer routes. A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
B:Each tenant reaches the authorized DNS prefix but cannot install another tenant's unrelated prefixes. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically VRF route leaking to shared service. Shared service access requires deliberate selective route leaking, not global RT membership across all tenants. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
C:Branch VRFs lack direct peer branch routes while the hub has the intended forwarding reachability. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically VPN hub-and-spoke controlled import. VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Question 769
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A provider wants to exchange VPN-labeled routes at ASBRs without maintaining a separate physical or logical VRF connection for each customer. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Establish the supported labeled VPN inter-AS peering with strict import/export policies.
- Configure unique appropriate RDs on each relevant PE routing instance.
- Import only scoped shared-service and return-path routes with appropriate policy.
- Implement asymmetric hub/spoke RT exchange and validate hub routing and return paths.
Explanation
Correct Answer
A:Establish the supported labeled VPN inter-AS peering with strict import/export policies. The change addresses the root behavior described here: Interprovider option B can exchange labeled VPNv4 routes between ASBRs to extend VPNs across provider domains. Verify success with: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Incorrect Answers
B:Configure unique appropriate RDs on each relevant PE routing instance. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Route distinguisher for overlapping customer routes. A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
C:Import only scoped shared-service and return-path routes with appropriate policy. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically VRF route leaking to shared service. Shared service access requires deliberate selective route leaking, not global RT membership across all tenants. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
D:Implement asymmetric hub/spoke RT exchange and validate hub routing and return paths. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically VPN hub-and-spoke controlled import. VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Question 770
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A provider wants to exchange VPN-labeled routes at ASBRs without maintaining a separate physical or logical VRF connection for each customer. Which operational control would best prevent a recurrence of this exact failure mode?
- Check RD uniqueness separately from route target policy when onboarding overlapping tenants.
- Test tenant isolation and label forwarding across the AS boundary.
- Keep negative cross-tenant tests and a shared-service route inventory.
- Test branch-to-branch isolation even when all BGP sessions are healthy.
Explanation
Correct Answer
B:Test tenant isolation and label forwarding across the AS boundary. The control limits repetition of the described root condition: Interprovider option B can exchange labeled VPNv4 routes between ASBRs to extend VPNs across provider domains. During audits, confirm: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Incorrect Answers
A:Check RD uniqueness separately from route target policy when onboarding overlapping tenants. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Route distinguisher for overlapping customer routes. A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
C:Keep negative cross-tenant tests and a shared-service route inventory. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically VRF route leaking to shared service. Shared service access requires deliberate selective route leaking, not global RT membership across all tenants. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
D:Test branch-to-branch isolation even when all BGP sessions are healthy. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically VPN hub-and-spoke controlled import. VPN hub-and-spoke restrictions are enforced through route distribution and topology policy, not merely by naming sites branches. In this scenario, however, the distinguishing issue is Interprovider VPN option B and the confirming observation is: The intended VPNv4 labeled reachability is exchanged at ASBRs with correct tenant import control.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests