Juniper JN0-664 Practice Test 41
Question 400
A provider change-review board examines this Junos service case. A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model. Which THREE statements together give an appropriate corrective action, supporting diagnostic check and success outcome? Select THREE answers.
- Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
- Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP.
- The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
- Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Explanation
Correct Answers
C:Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
E:The direct discriminating observation is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
F:The case-specific routing and services action is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Incorrect Answers
A:That option concerns PE to CE routing and customer route redistribution. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
B:That option concerns IS-IS level one level two hierarchy and area boundaries. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
D:That option concerns Layer 2 pseudowire MTU and control-word interworking. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
Question 401
A Junos service-provider routing engineer investigates the following routing and service incident: An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Separate route distinguishers for VPN-IPv4 address uniqueness from route targets that control eligible VPN route import and export policies.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
- Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
- Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Explanation
Correct Answer
D:The case-specific routing and services action is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. The governing Junos routing/service principle is: IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity.
Incorrect Answers
A:This alternative proposes: Separate route distinguishers for VPN-IPv4 address uniqueness from route targets that control eligible VPN route import and export policies. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
B:This alternative proposes: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 402
A provider routing design review considers this situation. An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family. A colleague proposes: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. Which technical principle BEST supports that action? Select ONE best answer.
- Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access.
- IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity.
- Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
- MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity. In the described provider-network case (An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family.), it supports the planned action: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Incorrect Answers
A:This alternative proposes: Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
D:This alternative proposes: MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 403
A Juniper service-provider engineer needs decisive verification evidence for this situation. An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect VPN route label, resolved tunnel in inet.3, label-switched path, control-plane next hop, penultimate-hop behavior and egress VRF lookup.
- Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability.
- Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
- Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
Explanation
Correct Answer
D:The direct discriminating observation is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. In the stated situation (An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family.), the intended acceptance outcome is: Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged.
Incorrect Answers
A:This alternative proposes: Inspect VPN route label, resolved tunnel in inet.3, label-switched path, control-plane next hop, penultimate-hop behavior and egress VRF lookup. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
B:This alternative proposes: Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. It concerns a different Junos engineering issue PE to CE routing and customer route redistribution, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 404
A service-provider acceptance team reviews the result of a provider-service change. An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family. The intended verification is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. Which outcome BEST demonstrates success? Select ONE best answer.
- Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged.
- The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
- The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
- Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls.
Explanation
Correct Answer
A:The verified success outcome is: Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged. Confirm this by: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
Incorrect Answers
B:This alternative proposes: The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:That option concerns Multiprotocol BGP family negotiations and VPN routes. The related controlled intervention is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
D:That option concerns Layer 3 VPN hub spoke topology and controlled Internet breakout. The related controlled intervention is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Question 405
A Junos service-provider routing engineer investigates this service-provider network scenario. An enterprise enables IPv6 at two branches but finds only IPv4 VPN routes in bgp.l3vpn.0 because its PEs have not negotiated the suitable IPv6 VPN family. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
- Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
- Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
Explanation
Correct Answers
A:The case-specific routing and services action is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. The governing Junos routing/service principle is: IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity. Verify the decision through: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
B:The direct discriminating observation is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
Incorrect Answers
C:This alternative proposes: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
D:This alternative proposes: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
E:This alternative proposes: Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 406
A Junos service-provider routing engineer investigates the following routing and service incident: A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
- Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
Explanation
Correct Answer
A:The case-specific routing and services action is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Incorrect Answers
B:This alternative proposes: Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
D:This alternative proposes: Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 407
A provider routing design review considers this situation. A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing. A colleague proposes: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. Which technical principle BEST supports that action? Select ONE best answer.
- IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity.
- Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.
- An RD distinguishes overlapping customer prefix routes in MP-BGP VPN NLRI, whereas RT extended communities guide import/export membership across VPN routing instances.
- SoO identifies the originating customer site for policy-based loop prevention; OSPF sham links can influence customer OSPF path choice across the VPN backbone in particular backdoor-link designs.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity. In the described provider-network case (A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing.), it supports the planned action: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Incorrect Answers
B:This alternative proposes: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: An RD distinguishes overlapping customer prefix routes in MP-BGP VPN NLRI, whereas RT extended communities guide import/export membership across VPN routing instances. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
D:This alternative proposes: SoO identifies the originating customer site for policy-based loop prevention; OSPF sham links can influence customer OSPF path choice across the VPN backbone in particular backdoor-link designs. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 408
A Juniper service-provider engineer needs decisive verification evidence for this situation. A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
- Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
- Check area IDs, ABR relationships, backbone LSA visibility, virtual-link state, and show ospf neighbor and database before adjusting policies.
- Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
Explanation
Correct Answer
B:The direct discriminating observation is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. In the stated situation (A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing.), the intended acceptance outcome is: Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged.
Incorrect Answers
A:This alternative proposes: Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: Check area IDs, ABR relationships, backbone LSA visibility, virtual-link state, and show ospf neighbor and database before adjusting policies. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
D:This alternative proposes: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding in the stated situation (A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing.). A better case-specific check is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. The more targeted action is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Question 409
A service-provider acceptance team reviews the result of a provider-service change. A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing. The intended verification is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. Which outcome BEST demonstrates success? Select ONE best answer.
- The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.
- The ingress PE pushes an appropriate label stack and the egress PE forwards the packet in the authorized customer context without exposing traffic to another VPN.
- Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged.
- The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
Explanation
Correct Answer
C:The verified success outcome is: Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged. Confirm this by: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. The related controlled intervention is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
Incorrect Answers
A:This alternative proposes: The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding in the stated situation (A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing.). A better case-specific check is: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. The more targeted action is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
B:That option concerns MPLS VPN transport label stack and next hop. The related controlled intervention is: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
D:This alternative proposes: The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
Question 410
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A remote PE receives IPv6 VPN NLRI but the subscriber VRF has no instance.inet6.0 route because the corresponding RT import policy is missing. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Import every spoke RT into all customer VRFs when the design explicitly requires isolation except for a controlled central inspection service.
- Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup.
- Assume every MAC learned on an EVPN remote PE must be discovered exclusively by data-plane flood without any BGP MAC/IP advertisement.
- Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.
Explanation
Correct Answer
D:That conflicts with the edge-to-cloud principle: IPv6 Layer 3 VPN routes use address-family-specific control-plane and forwarding information; a working IPv4 tenant VRF does not itself establish IPv6 connectivity.
Incorrect Answers
A:This alternative proposes: Import every spoke RT into all customer VRFs when the design explicitly requires isolation except for a controlled central inspection service. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
B:This alternative proposes: Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.
C:This alternative proposes: Assume every MAC learned on an EVPN remote PE must be discovered exclusively by data-plane flood without any BGP MAC/IP advertisement. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue IPv6 Layer 3 VPN VPNv6 route families and forwarding.