Question 820
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A PE receives packets with only the VPN service label after the upstream core router removes the transport label, confusing a troubleshooting team expecting two labels at every hop. Which operational control would best prevent a recurrence of this exact failure mode?
- Require service-route and labeled-transport checks as separate release gates.
- Verify post-label customer delivery using CE-facing counters and neighbor tests.
- Test label reachability and unauthorized route separation at the provider boundary.
- Document expected label-stack depth at each monitored hop.
Explanation
Correct Answer
D:Document expected label-stack depth at each monitored hop. The control limits repetition of the described root condition: Penultimate-hop popping can remove an outer transport label before the egress PE while retaining the service label for VPN context. During audits, confirm: The receiving PE resolves the remaining service label into the intended VRF forwarding path.
Incorrect Answers
A: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 LSP penultimate-hop pop effect and the confirming observation is: The receiving PE resolves the remaining service label into the intended VRF forwarding path.
B:Verify post-label customer delivery using CE-facing counters and neighbor tests. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically VPN service egress CE next hop. Successful MPLS service-label disposition does not guarantee the final customer next hop is reachable. In this scenario, however, the distinguishing issue is LSP penultimate-hop pop effect and the confirming observation is: The receiving PE resolves the remaining service label into the intended VRF forwarding path.
C:Test label reachability and unauthorized route separation at the provider boundary. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Carrier supporting carrier labeled service. Carrier-of-carriers service can transport another carrier's label-switched traffic across a provider without importing every downstream customer route. In this scenario, however, the distinguishing issue is LSP penultimate-hop pop effect and the confirming observation is: The receiving PE resolves the remaining service label into the intended VRF forwarding path.
Question 821
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An interprovider VPN deployment uses an RT already assigned to an unrelated tenant in the neighboring provider, causing unintended route imports. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare RT namespaces and explicit import/export policies across both providers.
- Inspect the VRF export aggregate and contributing prefixes against tenant address ownership.
- Trace the customer's default VRF route and next-hop path to the intended shared firewall service.
- Inspect RT imports and whether every authorized site can learn all other site prefixes.
Explanation
Correct Answer
A:Compare RT namespaces and explicit import/export policies across both providers. This check examines the decisive condition for Inter-AS route target collision before any unrelated changes are made. The underlying mechanism is: Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships. The confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Incorrect Answers
B:Inspect the VRF export aggregate and contributing prefixes against tenant address ownership. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically VRF export summary overscoped. VPN export summaries must respect each tenant's address scope; a broad aggregate can attract unrelated traffic even if RTs are correct. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
C:Trace the customer's default VRF route and next-hop path to the intended shared firewall service. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically L3VPN Internet breakout design. Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
D:Inspect RT imports and whether every authorized site can learn all other site prefixes. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Question 822
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An interprovider VPN deployment uses an RT already assigned to an unrelated tenant in the neighboring provider, causing unintended route imports. Which routing or service mechanism best explains the reported behavior?
- VPN export summaries must respect each tenant's address scope; a broad aggregate can attract unrelated traffic even if RTs are correct.
- Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships.
- Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology.
- A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs.
Explanation
Correct Answer
B:Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Test imports contain only the intended interprovider tenant prefixes after translation or filtering. The targeted correction is: Coordinate unique RT conventions or explicit RT translation across the boundary.
Incorrect Answers
A:VPN export summaries must respect each tenant's address scope; a broad aggregate can attract unrelated traffic even if RTs are correct. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically VRF export summary overscoped. VPN export summaries must respect each tenant's address scope; a broad aggregate can attract unrelated traffic even if RTs are correct. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
C:Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically L3VPN Internet breakout design. Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
D:A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Question 823
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An interprovider VPN deployment uses an RT already assigned to an unrelated tenant in the neighboring provider, causing unintended route imports. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Outbound customer traffic traverses the approved firewall and follows a valid return route.
- Every authorized site has the intended remote site routes without unwanted tenant routes.
- Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
- The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants.
Explanation
Correct Answer
C:Test imports contain only the intended interprovider tenant prefixes after translation or filtering. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships.
Incorrect Answers
A:Outbound customer traffic traverses the approved firewall and follows a valid return route. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically L3VPN Internet breakout design. Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
B:Every authorized site has the intended remote site routes without unwanted tenant routes. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
D:The ASBR customer VRFs exchange approved routes over their service interconnects without exposing other tenants. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Interprovider VPN option A. Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Question 824
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An interprovider VPN deployment uses an RT already assigned to an unrelated tenant in the neighboring provider, causing unintended route imports. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Constrain VPN route aggregation to the verified customer allocation.
- Implement the contracted centralized breakout with a controlled default and return-path architecture.
- Configure a tested shared VPN membership policy or equivalent explicit import/export design.
- Coordinate unique RT conventions or explicit RT translation across the boundary.
Explanation
Correct Answer
D:Coordinate unique RT conventions or explicit RT translation across the boundary. The change addresses the root behavior described here: Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships. Verify success with: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Incorrect Answers
A:Constrain VPN route aggregation to the verified customer allocation. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically VRF export summary overscoped. VPN export summaries must respect each tenant's address scope; a broad aggregate can attract unrelated traffic even if RTs are correct. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
B:Implement the contracted centralized breakout with a controlled default and return-path architecture. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically L3VPN Internet breakout design. Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
C:Configure a tested shared VPN membership policy or equivalent explicit import/export design. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Question 825
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An interprovider VPN deployment uses an RT already assigned to an unrelated tenant in the neighboring provider, causing unintended route imports. Which operational control would best prevent a recurrence of this exact failure mode?
- Exchange tenant RT inventories and negative-route import tests before turn-up.
- Validate security inspection and symmetric routing for each tenant.
- Maintain a site reachability matrix and retest after VRF changes.
- Account for per-VPN interconnect growth before selecting option A for hundreds of tenants.
Explanation
Correct Answer
A:Exchange tenant RT inventories and negative-route import tests before turn-up. The control limits repetition of the described root condition: Route targets have policy meaning across AS boundaries; overlapping assignment can connect unintended VPN memberships. During audits, confirm: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Incorrect Answers
B:Validate security inspection and symmetric routing for each tenant. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically L3VPN Internet breakout design. Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
C:Maintain a site reachability matrix and retest after VRF changes. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
D:Account for per-VPN interconnect growth before selecting option A for hundreds of tenants. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Interprovider VPN option A. Interprovider option A uses per-VPN VRF interconnections at ASBRs rather than exchanging VPNv4 directly across a shared core. In this scenario, however, the distinguishing issue is Inter-AS route target collision and the confirming observation is: Test imports contain only the intended interprovider tenant prefixes after translation or filtering.
Question 826
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: Two VPN sites have both a private backdoor OSPF connection and an MPLS VPN service, but OSPF intra-area routing over the backdoor wins over the desired provider path. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect RT imports and whether every authorized site can learn all other site prefixes.
- Inspect OSPF path types and the applicability of a sham-link design for the PE-to-PE VPN.
- Inspect each VRF's route distinguisher and the resulting VPN-IPv4 prefix identifiers.
- Inspect negotiated VPNv6 address family and IPv6-specific VRF route policy.
Explanation
Correct Answer
B:Inspect OSPF path types and the applicability of a sham-link design for the PE-to-PE VPN. This check examines the decisive condition for Sham link OSPF backdoor preference before any unrelated changes are made. The underlying mechanism is: An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue. The confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Incorrect Answers
A:Inspect RT imports and whether every authorized site can learn all other site prefixes. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
C: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
D: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Question 827
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: Two VPN sites have both a private backdoor OSPF connection and an MPLS VPN service, but OSPF intra-area routing over the backdoor wins over the desired provider path. Which routing or service mechanism best explains the reported behavior?
- A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs.
- A route distinguisher makes overlapping customer IPv4 prefixes distinguishable in VPN-IPv4 NLRI, but does not by itself decide route import.
- An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue.
- IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success.
Explanation
Correct Answer
C:An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding. The targeted correction is: Configure a supported sham link only when the customer's OSPF design requires it and transport is validated.
Incorrect Answers
A:A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
B: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
D: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Question 828
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: Two VPN sites have both a private backdoor OSPF connection and an MPLS VPN service, but OSPF intra-area routing over the backdoor wins over the desired provider path. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Every authorized site has the intended remote site routes without unwanted tenant routes.
- The core holds separate VPNv4 routes with distinct RDs for the identical customer IPv4 prefix.
- IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE.
- The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Explanation
Correct Answer
D:The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue.
Incorrect Answers
A:Every authorized site has the intended remote site routes without unwanted tenant routes. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
B: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
C: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Question 829
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: Two VPN sites have both a private backdoor OSPF connection and an MPLS VPN service, but OSPF intra-area routing over the backdoor wins over the desired provider path. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure a supported sham link only when the customer's OSPF design requires it and transport is validated.
- Configure a tested shared VPN membership policy or equivalent explicit import/export design.
- Configure unique appropriate RDs on each relevant PE routing instance.
- Enable the supported IPv6 VPN family with matching route targets and forwarding.
Explanation
Correct Answer
A:Configure a supported sham link only when the customer's OSPF design requires it and transport is validated. The change addresses the root behavior described here: An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue. Verify success with: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Incorrect Answers
B:Configure a tested shared VPN membership policy or equivalent explicit import/export design. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
C: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
D: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Question 830
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Two VPN sites have both a private backdoor OSPF connection and an MPLS VPN service, but OSPF intra-area routing over the backdoor wins over the desired provider path. Which operational control would best prevent a recurrence of this exact failure mode?
- Maintain a site reachability matrix and retest after VRF changes.
- Model backdoor failure and path restoration before modifying customer OSPF area design.
- Check RD uniqueness separately from route target policy when onboarding overlapping tenants.
- Verify IPv4 and IPv6 VPN route sets separately during dual-stack expansion.
Explanation
Correct Answer
B:Model backdoor failure and path restoration before modifying customer OSPF area design. The control limits repetition of the described root condition: An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue. During audits, confirm: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Incorrect Answers
A:Maintain a site reachability matrix and retest after VRF changes. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Full-mesh VPN routing. A full-mesh L3VPN needs an appropriate route distribution relationship among all participating VRFs. In this scenario, however, the distinguishing issue is Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
C: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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
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 Sham link OSPF backdoor preference and the confirming observation is: The PE-provided path competes in the expected OSPF intra-area calculation with correct forwarding.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests