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 2

Question 10

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. During a network acquisition, an operator proposes a permanent OSPF virtual link through a transit area with intermittent links instead of a resilient direct backbone. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes.
  2. Assume two separate nonbackbone areas exchange all interarea routes automatically even though neither connects to area 0.
  3. Assume every inter-provider VPN can be connected by advertising raw customer private addresses on an unsecured global peering session with no labels or VPN policy.
  4. Assume every pair of routers on a broadcast VLAN must display Full adjacency, and bounce the elected DR whenever another router is only Two-Way.

Explanation

Correct Answer

B:

Apply instead: Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design.

Incorrect Answers

A:

This alternative proposes: Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue OSPF multi-area backbone connectivity and virtual-link limitations.

C:

This alternative proposes: Assume every inter-provider VPN can be connected by advertising raw customer private addresses on an unsecured global peering session with no labels or VPN policy. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue OSPF multi-area backbone connectivity and virtual-link limitations.

D:

This alternative proposes: Assume every pair of routers on a broadcast VLAN must display Full adjacency, and bounce the elected DR whenever another router is only Two-Way. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue OSPF multi-area backbone connectivity and virtual-link limitations.

Question 11

A Junos service-provider routing engineer investigates the following routing and service incident: Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable.
  2. Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.
  3. Check OSPFv3 adjacency and IPv6 reachability through supported Junos ospf3 operational commands rather than assuming an IPv4 OSPFv2 adjacency proves IPv6 is working.
  4. Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.

Explanation

Correct Answer

B:

The case-specific routing and services action is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. The governing Junos routing/service principle is: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.

Incorrect Answers

A:

This alternative proposes: Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

C:

This alternative proposes: Check OSPFv3 adjacency and IPv6 reachability through supported Junos ospf3 operational commands rather than assuming an IPv4 OSPFv2 adjacency proves IPv6 is working. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

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 OSPF adjacency MTU and hello compatibility diagnosis.

Question 12

A provider routing design review considers this situation. Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side. A colleague proposes: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. Which technical principle BEST supports that action? Select ONE best answer.

  1. OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.
  2. OSPF backbone area 0 carries interarea reachability; a virtual link can join a disconnected backbone through an eligible transit area, but it is not a substitute for planned topology repair.
  3. ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage.
  4. VPLS presents multipoint Ethernet LAN semantics across provider nodes, while LDP or BGP signaling can distribute service state and labels; mixing models requires supported interworking.

Explanation

Correct Answer

A:

The relevant Junos service-provider networking principle is: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ. In the described provider-network case (Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side.), it supports the planned action: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Incorrect Answers

B:

This alternative proposes: OSPF backbone area 0 carries interarea reachability; a virtual link can join a disconnected backbone through an eligible transit area, but it is not a substitute for planned topology repair. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

C:

This alternative proposes: ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

D:

This alternative proposes: VPLS presents multipoint Ethernet LAN semantics across provider nodes, while LDP or BGP signaling can distribute service state and labels; mixing models requires supported interworking. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

Question 13

A Juniper service-provider engineer needs decisive verification evidence for this situation. Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.
  2. Inspect specific prefixes at the ABR, area range configuration, policy match criteria, summary LSA presence and forwarding toward the aggregated destinations.
  3. Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
  4. Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.

Explanation

Correct Answer

A:

The direct discriminating observation is: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers. In the stated situation (Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side.), the intended acceptance outcome is: The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.

Incorrect Answers

B:

This alternative proposes: Inspect specific prefixes at the ABR, area range configuration, policy match criteria, summary LSA presence and forwarding toward the aggregated destinations. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

C:

This alternative proposes: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

D:

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 OSPF adjacency MTU and hello compatibility diagnosis.

Question 14

A service-provider acceptance team reviews the result of a provider-service change. Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side. The intended verification is: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers. Which outcome BEST demonstrates success? Select ONE best answer.

  1. The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
  2. The appropriate designated and backup routers maintain required adjacencies and exchange reachability across the shared Ethernet without unnecessary resets.
  3. The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.
  4. The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.

Explanation

Correct Answer

C:

The verified success outcome is: The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted. Confirm this by: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.

Incorrect Answers

A:

This alternative proposes: The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

B:

That option concerns OSPF designated router election on a multiaccess segment. The related controlled intervention is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

D:

That option concerns VPLS site identifiers multihoming and service convergence. The related controlled intervention is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Question 15

A Junos service-provider routing engineer investigates this service-provider network scenario. Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Choose PIM dense or sparse behavior according to multicast receiver distribution and verify that each involved interface uses a compatible supported mode.
  2. Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.
  3. Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
  4. Separate route distinguishers for VPN-IPv4 address uniqueness from route targets that control eligible VPN route import and export policies.
  5. Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Explanation

Correct Answers

B:

The direct discriminating observation is: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.

E:

The case-specific routing and services action is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. The governing Junos routing/service principle is: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ. Verify the decision through: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.

Incorrect Answers

A:

This alternative proposes: Choose PIM dense or sparse behavior according to multicast receiver distribution and verify that each involved interface uses a compatible supported mode. It concerns a different Junos engineering issue PIM dense mode versus sparse mode interface deployment, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

C:

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 OSPF adjacency MTU and hello compatibility diagnosis in the stated situation (Two Junos P routers hear OSPF hellos and show neighbor state ExStart after a transport change introduced mismatched MTU at one side.). A better case-specific check is: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.

D:

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 OSPF adjacency MTU and hello compatibility diagnosis.

Question 16

A Junos service-provider routing engineer investigates the following routing and service incident: An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  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. Check OSPFv3 adjacency and IPv6 reachability through supported Junos ospf3 operational commands rather than assuming an IPv4 OSPFv2 adjacency proves IPv6 is working.
  3. Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.
  4. 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 Answer

C:

The case-specific routing and services action is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

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 OSPF adjacency MTU and hello compatibility diagnosis.

B:

This alternative proposes: Check OSPFv3 adjacency and IPv6 reachability through supported Junos ospf3 operational commands rather than assuming an IPv4 OSPFv2 adjacency proves IPv6 is working. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

D:

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 OSPF adjacency MTU and hello compatibility diagnosis.

Question 17

A provider routing design review considers this situation. An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency. A colleague proposes: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. Which technical principle BEST supports that action? Select ONE best answer.

  1. Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered.
  2. OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.
  3. A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions.
  4. 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.

Explanation

Correct Answer

B:

The relevant Junos service-provider networking principle is: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ. In the described provider-network case (An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency.), it supports the planned action: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Incorrect Answers

A:

This alternative proposes: Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

C:

This alternative proposes: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

D:

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 OSPF adjacency MTU and hello compatibility diagnosis.

Question 18

A Juniper service-provider engineer needs decisive verification evidence for this situation. An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Check area IDs, ABR relationships, backbone LSA visibility, virtual-link state, and show ospf neighbor and database before adjusting policies.
  2. Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.
  3. Compare show ospf interface, election priorities, router IDs, two-way versus full neighbors, and current DR/BDR state after planned link transitions.
  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

B:

The direct discriminating observation is: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers. In the stated situation (An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency.), the intended acceptance outcome is: The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.

Incorrect Answers

A:

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 OSPF adjacency MTU and hello compatibility diagnosis.

C:

This alternative proposes: Compare show ospf interface, election priorities, router IDs, two-way versus full neighbors, and current DR/BDR state after planned link transitions. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

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 OSPF adjacency MTU and hello compatibility diagnosis.

Question 19

A service-provider acceptance team reviews the result of a provider-service change. An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency. The intended verification is: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers. Which outcome BEST demonstrates success? Select ONE best answer.

  1. The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
  2. Premium voice packets enter their intended forwarding class while unmarked best-effort traffic remains appropriately classified.
  3. The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.
  4. All site prefixes move between areas without routing loops, and the proposed backbone topology survives its agreed failure test.

Explanation

Correct Answer

C:

The verified success outcome is: The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted. Confirm this by: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers. The related controlled intervention is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Incorrect Answers

A:

This alternative proposes: The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

B:

That option concerns Junos CoS behavior aggregate versus multifield classifiers. The related controlled intervention is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

D:

That option concerns OSPF multi-area backbone connectivity and virtual-link limitations. The related controlled intervention is: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Question 20

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Conclude that working OSPFv2 routes automatically provide IPv6 reachability on Junos without any OSPFv3 or other IPv6 routing configuration.
  2. Disable OSPF on every provider interface merely because one neighbor is stuck in ExStart during database negotiation.
  3. Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes.
  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: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.

Incorrect Answers

A:

This alternative proposes: Conclude that working OSPFv2 routes automatically provide IPv6 reachability on Junos without any OSPFv3 or other IPv6 routing configuration. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

C:

This alternative proposes: Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.

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 OSPF adjacency MTU and hello compatibility diagnosis.

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