Juniper JN0-664 Practice Test 36
Question 350
A Junos service-provider routing engineer investigates this service-provider network scenario. A remote VPN prefix exists in bgp.l3vpn.0 as hidden due to an unresolved transport next hop and the engineer attempts to correct only the CE interface subnet. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Trace a VPNv4 prefix from MP-BGP reception to a customer VRF routing table, distinguishing provider VPN control-plane storage and installed customer forwarding routes.
- Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
- Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
- Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
Explanation
Correct Answers
A:The case-specific routing and services action is: Trace a VPNv4 prefix from MP-BGP reception to a customer VRF routing table, distinguishing provider VPN control-plane storage and installed customer forwarding routes.
E:The direct discriminating observation is: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
Incorrect Answers
B: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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.
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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.
D:This alternative proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.
Question 351
A Junos service-provider routing engineer investigates the following routing and service incident: A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
- Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone.
- Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
Explanation
Correct Answer
C:PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability. Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
Incorrect Answers
A: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 PE to CE routing and customer route redistribution.
B:This alternative proposes: Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
D: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 PE to CE routing and customer route redistribution.
Question 352
A provider routing design review considers this situation. A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match. A colleague proposes: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability.
- OSPF Type 1 external metrics include internal cost toward the ASBR, whereas Type 2 external metrics primarily compare the advertised external metric with internal tie behavior.
- In a typical BGP/MPLS L3VPN, an outer transport label carries traffic toward the egress PE and an inner VPN label selects the egress service context as supported by the implementation.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability. In the described provider-network case (A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match.), it supports the planned action: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Incorrect Answers
A: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 PE to CE routing and customer route redistribution.
C:This alternative proposes: OSPF Type 1 external metrics include internal cost toward the ASBR, whereas Type 2 external metrics primarily compare the advertised external metric with internal tie behavior. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
D:This alternative proposes: In a typical BGP/MPLS L3VPN, an outer transport label carries traffic toward the egress PE and an inner VPN label selects the egress service context as supported by the implementation. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
Question 353
A Juniper service-provider engineer needs decisive verification evidence for this situation. A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
- Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population.
- Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover.
- Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
Explanation
Correct Answer
D:In the stated situation (A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match.), the intended acceptance outcome is: Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks.
Incorrect Answers
A:This alternative proposes: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
B:This alternative proposes: Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
C:This alternative proposes: Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
Question 354
A service-provider acceptance team reviews the result of a provider-service change. A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match. The intended verification is: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. Which outcome BEST demonstrates success? Select ONE best answer.
- All site prefixes move between areas without routing loops, and the proposed backbone topology survives its agreed failure test.
- Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks.
- 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
B:The verified success outcome is: Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks. Confirm this by: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
Incorrect Answers
A:That option concerns OSPF multi-area backbone connectivity and virtual-link limitations. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
C:That option concerns IPv6 Layer 3 VPN VPNv6 route families and forwarding. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
D:That option concerns Interprovider Layer 3 VPN options and carrier of carriers. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Question 355
A Junos service-provider routing engineer investigates this service-provider network scenario. A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
- Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
- Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
- Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design.
- Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
Explanation
Correct Answers
B:The case-specific routing and services action is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies. The governing Junos routing/service principle is: PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability.
E:The direct discriminating observation is: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. In the stated situation (A new branch CE and PE have an Established BGP session but its route is absent from the provider's VPN export policy match.), the intended acceptance outcome is: Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks.
Incorrect Answers
A:This alternative proposes: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
C: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 PE to CE routing and customer route redistribution.
D:This alternative proposes: Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
Question 356
A Junos service-provider routing engineer investigates the following routing and service incident: A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone.
- Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol.
- Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
- Examine external route Type 1 versus Type 2 cost behavior and the forwarding cost toward the ASBR when determining why routers choose different exits.
Explanation
Correct Answer
C:The case-specific routing and services action is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies. The governing Junos routing/service principle is: PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability. Verify the decision through: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
Incorrect Answers
A:This alternative proposes: Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
B:This alternative proposes: Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
D:This alternative proposes: Examine external route Type 1 versus Type 2 cost behavior and the forwarding cost toward the ASBR when determining why routers choose different exits. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
Question 357
A provider routing design review considers this situation. A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site. A colleague proposes: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies. Which technical principle BEST supports that action? Select ONE best answer.
- An RD distinguishes overlapping customer prefix routes in MP-BGP VPN NLRI, whereas RT extended communities guide import/export membership across VPN routing instances.
- OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.
- PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability.
- 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
C:The relevant Junos service-provider networking principle is: PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability. In the described provider-network case (A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site.), it supports the planned action: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Incorrect Answers
A: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 PE to CE routing and customer route redistribution.
B:This alternative proposes: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ. It concerns a different Junos engineering issue OSPF adjacency MTU and hello compatibility diagnosis, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
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 PE to CE routing and customer route redistribution.
Question 358
A Juniper service-provider engineer needs decisive verification evidence for this situation. A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
- Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.
- Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.
- Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
Explanation
Correct Answer
D:The direct discriminating observation is: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. In the stated situation (A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site.), the intended acceptance outcome is: Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks.
Incorrect Answers
A:This alternative proposes: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
B:This alternative proposes: Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
C:This alternative proposes: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue PE to CE routing and customer route redistribution in the stated situation (A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site.). A better case-specific check is: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. The more targeted action is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Question 359
A service-provider acceptance team reviews the result of a provider-service change. A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site. The intended verification is: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. Which outcome BEST demonstrates success? Select ONE best answer.
- Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls.
- Customer multicast subscribers receive their authorized streams through the VPN without flooding other tenants or depending on unavailable default multicast underlay features.
- The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
- Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks.
Explanation
Correct Answer
D:The verified success outcome is: Each site advertises and learns only authorized enterprise routes, without leaking internal core routes or other tenants' networks. Confirm this by: Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Incorrect Answers
A:That option concerns Layer 3 VPN hub spoke topology and controlled Internet breakout. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
B:That option concerns Multicast VPN provider and customer traffic separation. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
C:That option concerns VPLS site identifiers multihoming and service convergence. The related controlled intervention is: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Question 360
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A static customer prefix is present in a PE's global routing table rather than the expected tenant VRF and cannot be seen at the remote site. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.
- Add a customer access interface to the provider's global inet.0 table and expect its overlapping RFC1918 subnet to remain isolated from every other tenant.
- Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability.
- Treat an RD as an access-control filter and set identical RDs for every unrelated VPN while leaving permissive RT import policy unrestricted.
Explanation
Correct Answer
B:Apply instead: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
Incorrect Answers
A:This alternative proposes: Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
C:This alternative proposes: Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue PE to CE routing and customer route redistribution.
D:This alternative proposes: Treat an RD as an access-control filter and set identical RDs for every unrelated VPN while leaving permissive RT import policy unrestricted. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue PE to CE routing and customer route redistribution.