cert
cert-1
cert-2

Pass Juniper JN0-664 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
JN0-664 Exam - Verified By Experts
JN0-664 Premium File

JN0-664 Premium File

$69.99
$76.99
  • Premium File 96 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 20 downloads in the last 7 days
block-screenshots
Juniper JN0-664 Practice Test 35

Question 340

A Junos service-provider routing engineer investigates this service-provider network scenario. A provider changes an RT export value but expects remote PE VRFs to import the same routes despite no matching import targets. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Inspect broadcast-network DR and BDR election state and interface priority before attempting to control database exchange behavior on an Ethernet shared segment.
  2. Separate route distinguishers for VPN-IPv4 address uniqueness from route targets that control eligible VPN route import and export policies.
  3. Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
  4. Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population.
  5. 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

B:

The case-specific routing and services action is: Separate route distinguishers for VPN-IPv4 address uniqueness from route targets that control eligible VPN route import and export policies. Verify the decision through: Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population.

D:

The direct discriminating observation is: Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population. In the stated situation (A provider changes an RT export value but expects remote PE VRFs to import the same routes despite no matching import targets.), the intended acceptance outcome is: Two customers may use the same internal subnet without conflated control-plane identities and only authorized VPNs import each others' prefixes.

Incorrect Answers

A:

This alternative proposes: Inspect broadcast-network DR and BDR election state and interface priority before attempting to control database exchange behavior on an Ethernet shared segment. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue Layer 3 VPN route distinguishers versus route targets.

C:

This alternative proposes: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue Layer 3 VPN route distinguishers versus route targets.

E:

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 Layer 3 VPN route distinguishers versus route targets.

Question 341

A Junos service-provider routing engineer investigates the following routing and service incident: An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
  2. Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
  3. 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.
  4. Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Explanation

Correct Answer

C:

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. The governing Junos routing/service principle is: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0.

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

D:

This alternative proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 342

A provider routing design review considers this situation. An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match. A colleague proposes: 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. Which technical principle BEST supports that action? Select ONE best answer.

  1. The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0.
  2. ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees.
  3. 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.
  4. 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.

Explanation

Correct Answer

A:

The relevant Junos service-provider networking principle is: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0. In the described provider-network case (An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match.), it supports the planned action: 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.

Incorrect Answers

B:

This alternative proposes: ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

C:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

D:

This alternative proposes: 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. It concerns a different Junos engineering issue PE to CE routing and customer route redistribution, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 343

A Juniper service-provider engineer needs decisive verification evidence for this situation. An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
  2. Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
  3. Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
  4. Inspect BGP negotiated family, VPNv6 table, instance.inet6.0, RT import, IPv6 CE routing, next-hop transport and IPv6 forwarding counters.

Explanation

Correct Answer

C:

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. In the stated situation (An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match.), the intended acceptance outcome is: The correct VPN route is visible in the intended customer VRF with a valid forwarding next hop and is absent from unauthorized VRFs.

Incorrect Answers

A:

This alternative proposes: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

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.

D:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 344

A service-provider acceptance team reviews the result of a provider-service change. An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match. The intended verification is: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. Which outcome BEST demonstrates success? Select ONE best answer.

  1. The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
  2. The correct VPN route is visible in the intended customer VRF with a valid forwarding next hop and is absent from unauthorized VRFs.
  3. Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls.
  4. 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: The correct VPN route is visible in the intended customer VRF with a valid forwarding next hop and is absent from unauthorized VRFs. Confirm this by: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.

Incorrect Answers

A:

That option concerns VPLS site identifiers multihoming and service convergence. The related controlled intervention 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.

C:

That option concerns Layer 3 VPN hub spoke topology and controlled Internet breakout. The related controlled intervention 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.

D:

That option concerns Interprovider Layer 3 VPN options and carrier of carriers. The related controlled intervention 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.

Question 345

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An MPLS provider PE receives a VPNv4 route but the customer route remains missing from ACME.inet.0 because the RT policy does not match. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Create two circuits with different VC identifiers and assume LDP can automatically infer they belong to the same customer service because the physical ports are Up.
  2. Assume every route present in bgp.l3vpn.0 is automatically installed into every customer's instance.inet.0 regardless of import policies.
  3. Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.
  4. 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.

Explanation

Correct Answer

B:

That conflicts with the edge-to-cloud principle: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0.

Incorrect Answers

A:

This alternative proposes: Create two circuits with different VC identifiers and assume LDP can automatically infer they belong to the same customer service because the physical ports are Up. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

C:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

D:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 346

A Junos service-provider routing engineer investigates the following routing and service incident: 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. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol.
  2. Separate route distinguishers for VPN-IPv4 address uniqueness from route targets that control eligible VPN route import and export policies.
  3. Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.
  4. 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.

Explanation

Correct Answer

D:

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. The governing Junos routing/service principle is: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0. Verify the decision through: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.

Incorrect Answers

A:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

B:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

C:

This alternative proposes: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 347

A provider routing design review considers this situation. 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. A colleague proposes: 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. Which technical principle BEST supports that action? Select ONE best answer.

  1. 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.
  2. 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.
  3. Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding.
  4. The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0.

Explanation

Correct Answer

D:

The relevant Junos service-provider networking principle is: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0. In the described provider-network case (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.), it supports the planned action: 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.

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

B:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

C:

This alternative proposes: Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 348

A Juniper service-provider engineer needs decisive verification evidence for this situation. 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 observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
  2. Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
  3. 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.
  4. Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy.

Explanation

Correct Answer

A:

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. In the stated situation (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.), the intended acceptance outcome is: The correct VPN route is visible in the intended customer VRF with a valid forwarding next hop and is absent from unauthorized VRFs.

Incorrect Answers

B:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables in the stated situation (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.). A better case-specific check is: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. The more targeted 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.

D:

This alternative proposes: Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

Question 349

A service-provider acceptance team reviews the result of a provider-service change. 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. The intended verification is: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. Which outcome BEST demonstrates success? Select ONE best answer.

  1. The correct VPN route is visible in the intended customer VRF with a valid forwarding next hop and is absent from unauthorized VRFs.
  2. The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.
  3. Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged.
  4. Customer multicast subscribers receive their authorized streams through the VPN without flooding other tenants or depending on unavailable default multicast underlay features.

Explanation

Correct Answer

A:

The verified success outcome is: The correct VPN route is visible in the intended customer VRF with a valid forwarding next hop and is absent from unauthorized VRFs. Confirm this by: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. The related controlled intervention 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.

Incorrect Answers

B:

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 VPNv4 bgp.l3vpn.0 versus customer VRF route tables in the stated situation (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.). A better case-specific check is: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. The more targeted 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.

C:

This alternative proposes: Authorized IPv6 subnets communicate across customer sites while overlapping IPv4 tenant routing remains isolated and unchanged. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

D:

This alternative proposes: Customer multicast subscribers receive their authorized streams through the VPN without flooding other tenants or depending on unavailable default multicast underlay features. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables.

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.

  1. 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.
  2. Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
  3. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
  4. Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
  5. 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.

Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests