Question 790
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: IPv4 L3VPN routes work but a new IPv6 service prefix never arrives at a remote PE even though both CEs have IPv6 addresses. Which operational control would best prevent a recurrence of this exact failure mode?
- Model backdoor failure and path restoration before modifying customer OSPF area design.
- Verify IPv4 and IPv6 VPN route sets separately during dual-stack expansion.
- Verify each negotiated address family during VPN onboarding.
- Watch hidden VPN routes and underlay route loss together.
Explanation
Correct Answer
B:Verify IPv4 and IPv6 VPN route sets separately during dual-stack expansion. The control limits repetition of the described root condition: IPv6 L3VPN route exchange needs the appropriate MP-BGP address family and IPv6 route handling independent of IPv4 VPN success. During audits, confirm: IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE.
Incorrect Answers
A:Model backdoor failure and path restoration before modifying customer OSPF area design. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Sham link OSPF backdoor preference. An OSPF sham link can make the provider path appear as an intra-area option to address a backdoor path-type preference issue. In this scenario, however, the distinguishing issue is IPv6 VPN reachability and the confirming observation is: IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE.
C: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 IPv6 VPN reachability and the confirming observation is: IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE.
D:Watch hidden VPN routes and underlay route loss together. This is a plausible preventive practice 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 IPv6 VPN reachability and the confirming observation is: IPv6 VPN routes appear and their transport next hops resolve to the correct remote PE.
Question 791
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A customer multicast source is reachable at one L3VPN site but receivers at another site obtain no stream despite ordinary unicast VPN traffic working. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect site-of-origin marking and route rejection at the two PE-to-CE boundaries.
- Compare exported route targets on the VPNv4 route with the receiving VRF's import policy.
- Inspect multicast VPN control-plane signaling and provider multicast transport separately from unicast VRF routes.
- Inspect the VPN route's BGP next hop and the IGP/MPLS path to that specific loopback.
Explanation
Correct Answer
C:Inspect multicast VPN control-plane signaling and provider multicast transport separately from unicast VRF routes. This check examines the decisive condition for MVPN receiver routing absent before any unrelated changes are made. The underlying mechanism is: L3VPN unicast reachability alone does not establish an MVPN multicast distribution tree. The confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Incorrect Answers
A:Inspect site-of-origin marking and route rejection at the two PE-to-CE boundaries. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically Site-of-origin multihoming loop. A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
B:Compare exported route targets on the VPNv4 route with the receiving VRF's import policy. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically Route target export membership. Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
D: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 MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Question 792
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A customer multicast source is reachable at one L3VPN site but receivers at another site obtain no stream despite ordinary unicast VPN traffic working. Which routing or service mechanism best explains the reported behavior?
- A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site.
- Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs.
- VPN control-plane reachability is not enough; the remote PE next hop must resolve to a usable provider transport path.
- L3VPN unicast reachability alone does not establish an MVPN multicast distribution tree.
Explanation
Correct Answer
D:L3VPN unicast reachability alone does not establish an MVPN multicast distribution tree. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source. The targeted correction is: Configure supported multicast VPN distribution and receiver/source membership controls.
Incorrect Answers
A:A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically Site-of-origin multihoming loop. A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
B:Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically Route target export membership. Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
C: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 MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Question 793
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A customer multicast source is reachable at one L3VPN site but receivers at another site obtain no stream despite ordinary unicast VPN traffic working. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
- A route tagged for the site is not reintroduced into it via the alternate PE.
- The remote route contains an RT accepted by the receiver and appears in the intended VRF.
- The remote PE loopback is reachable through labeled transport and the VPN route becomes usable.
Explanation
Correct Answer
A:The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: L3VPN unicast reachability alone does not establish an MVPN multicast distribution tree.
Incorrect Answers
B:A route tagged for the site is not reintroduced into it via the alternate PE. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Site-of-origin multihoming loop. A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
C:The remote route contains an RT accepted by the receiver and appears in the intended VRF. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically Route target export membership. Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
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 MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Question 794
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A customer multicast source is reachable at one L3VPN site but receivers at another site obtain no stream despite ordinary unicast VPN traffic working. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Set consistent site-of-origin policy across the site's participating attachments.
- Configure supported multicast VPN distribution and receiver/source membership controls.
- Align the approved export RT and receiving import RT policy without broadening tenant access.
- Restore underlying PE loopback routing and label reachability.
Explanation
Correct Answer
B:Configure supported multicast VPN distribution and receiver/source membership controls. The change addresses the root behavior described here: L3VPN unicast reachability alone does not establish an MVPN multicast distribution tree. Verify success with: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Incorrect Answers
A:Set consistent site-of-origin policy across the site's participating attachments. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Site-of-origin multihoming loop. A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
C:Align the approved export RT and receiving import RT policy without broadening tenant access. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically Route target export membership. Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
D:Restore underlying PE loopback routing and label reachability. This is a plausible configuration or operational fix 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 MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Question 795
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A customer multicast source is reachable at one L3VPN site but receivers at another site obtain no stream despite ordinary unicast VPN traffic working. Which operational control would best prevent a recurrence of this exact failure mode?
- Test site failover for reflected own-site routes and unintended loops.
- Validate positive and negative intersite route-target import tests.
- Include multicast-over-VPN traffic tests in multisite service acceptance.
- Watch hidden VPN routes and underlay route loss together.
Explanation
Correct Answer
C:Include multicast-over-VPN traffic tests in multisite service acceptance. The control limits repetition of the described root condition: L3VPN unicast reachability alone does not establish an MVPN multicast distribution tree. During audits, confirm: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Incorrect Answers
A:Test site failover for reflected own-site routes and unintended loops. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Site-of-origin multihoming loop. A site-of-origin attribute can prevent a multi-homed VPN site from reimporting routes that originated at that same site. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
B:Validate positive and negative intersite route-target import tests. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Route target export membership. Route targets are extended-community policy selectors controlling which VPN routes are imported into customer VRFs. In this scenario, however, the distinguishing issue is MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
D:Watch hidden VPN routes and underlay route loss together. This is a plausible preventive practice 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 MVPN receiver routing absent and the confirming observation is: The MVPN state and receiver membership form an end-to-end tree carrying the authorized multicast source.
Question 796
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An MVPN application is seen in the wrong tenant VRF after shared multicast policy objects were used without tenant filtering. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Trace the customer's default VRF route and next-hop path to the intended shared firewall service.
- Inspect recursive default next hops and routing-instance leak targets on both sides.
- Inspect the logical CE-facing interface's routing-instance membership and route table location.
- Inspect multicast routing instance association and source/group import eligibility.
Explanation
Correct Answer
D:Inspect multicast routing instance association and source/group import eligibility. This check examines the decisive condition for MVPN source and group isolation before any unrelated changes are made. The underlying mechanism is: MVPN distribution must preserve tenant membership and multicast source/group policy, separate from provider transport connectivity. The confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
Incorrect Answers
A: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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
B:Inspect recursive default next hops and routing-instance leak targets on both sides. This is a plausible diagnostic check for a different Layer 3 VPNs condition, specifically VRF routing-loop via defaults. Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop. In this scenario, however, the distinguishing issue is MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
C:Inspect the logical CE-facing interface's routing-instance membership and route table location. This is a plausible diagnostic check 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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
Question 797
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An MVPN application is seen in the wrong tenant VRF after shared multicast policy objects were used without tenant filtering. Which routing or service mechanism best explains the reported behavior?
- MVPN distribution must preserve tenant membership and multicast source/group policy, separate from provider transport connectivity.
- Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology.
- Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop.
- L3VPN separation starts at the correct PE customer interface association with the VRF.
Explanation
Correct Answer
A:MVPN distribution must preserve tenant membership and multicast source/group policy, separate from provider transport connectivity. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Only the intended tenant receives the authorized multicast group after policy isolation. The targeted correction is: Correct multicast VPN import and VRF membership filters for the affected source/group.
Incorrect Answers
B: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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
C:Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop. This is a plausible protocol explanation for a different Layer 3 VPNs condition, specifically VRF routing-loop via defaults. Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop. In this scenario, however, the distinguishing issue is MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
D: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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
Question 798
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An MVPN application is seen in the wrong tenant VRF after shared multicast policy objects were used without tenant filtering. 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.
- Only the intended tenant receives the authorized multicast group after policy isolation.
- Outbound customer traffic traverses the approved firewall and follows a valid return route.
- Forwarding resolution terminates at a real egress rather than recursing between VRF defaults.
Explanation
Correct Answer
B:Only the intended tenant receives the authorized multicast group after policy isolation. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: MVPN distribution must preserve tenant membership and multicast source/group policy, separate from provider transport connectivity.
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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
C: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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
D:Forwarding resolution terminates at a real egress rather than recursing between VRF defaults. This is a plausible observed evidence for a different Layer 3 VPNs condition, specifically VRF routing-loop via defaults. Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop. In this scenario, however, the distinguishing issue is MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
Question 799
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An MVPN application is seen in the wrong tenant VRF after shared multicast policy objects were used without tenant filtering. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Attach the CE logical interface to the correct instance type and VRF.
- Implement the contracted centralized breakout with a controlled default and return-path architecture.
- Correct multicast VPN import and VRF membership filters for the affected source/group.
- Replace cyclic defaults with specific shared-service routes and valid exit paths.
Explanation
Correct Answer
C:Correct multicast VPN import and VRF membership filters for the affected source/group. The change addresses the root behavior described here: MVPN distribution must preserve tenant membership and multicast source/group policy, separate from provider transport connectivity. Verify success with: Only the intended tenant receives the authorized multicast group after policy isolation.
Incorrect Answers
A: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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
D:Replace cyclic defaults with specific shared-service routes and valid exit paths. This is a plausible configuration or operational fix for a different Layer 3 VPNs condition, specifically VRF routing-loop via defaults. Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop. In this scenario, however, the distinguishing issue is MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
Question 800
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An MVPN application is seen in the wrong tenant VRF after shared multicast policy objects were used without tenant filtering. Which operational control would best prevent a recurrence of this exact failure mode?
- Include interface-to-tenant mapping validation in turn-up checklists.
- Validate security inspection and symmetric routing for each tenant.
- Run traceroute and recursion loop tests for shared-VRF changes.
- Test negative multicast delivery across isolated VPN tenants.
Explanation
Correct Answer
D:Test negative multicast delivery across isolated VPN tenants. The control limits repetition of the described root condition: MVPN distribution must preserve tenant membership and multicast source/group policy, separate from provider transport connectivity. During audits, confirm: Only the intended tenant receives the authorized multicast group after policy isolation.
Incorrect Answers
A: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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
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 MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
C:Run traceroute and recursion loop tests for shared-VRF changes. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically VRF routing-loop via defaults. Bidirectional default leaking without terminal specific reachability can create a persistent inter-VRF loop. In this scenario, however, the distinguishing issue is MVPN source and group isolation and the confirming observation is: Only the intended tenant receives the authorized multicast group after policy isolation.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests