McAfee Secured

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

100% Juniper JN0-364 Guaranteed Success With Testking Training Materials

Get Real JN0-364 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

69 Questions & Answers with Testing Engine

"Service Provider Routing and Switching, Specialist (JNCIS-SP) Exam", also known as JN0-364 exam, is a Juniper certification exam.

Pass your tests with the always up-to-date JN0-364 Exam Engine. Your JN0-364 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 93

Question 920

In a separate fictional JNCIS-SP lab review for Seabrook Metro 230, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution. What likely service impact does this condition create?

  1. A hidden encapsulation or decapsulation fault persists behind a green interface alarm.
  2. Overlay routes remain configured but customer packets never reach the remote site.
  3. IPv6 routing does not converge across the link.
  4. Tunnel establishment loops or collapses during forwarding changes.

Explanation

Correct Answer

D:

Tunnel establishment loops or collapses during forwarding changes. Ensure that the GRE outer endpoint resolves through the physical underlay instead of through the tunnel itself. A tunnel must not rely on its own encapsulated path to reach the outer endpoint.

Incorrect Answers

A:

A hidden encapsulation or decapsulation fault persists behind a green interface alarm. That could help when monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; here, a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution.

B:

Overlay routes remain configured but customer packets never reach the remote site. This is applicable when a configured GRE tunnel stays unusable after the remote outer IP endpoint changes; the present condition is that a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution.

C:

IPv6 routing does not converge across the link. It is relevant if an IPv6 prefix is missing across a point-to-point link because OSPFv2 was configured but OSPFv3 was omitted, but the reported issue is that a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution.

Question 921

At fictional Northpoint Access 231, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Which configuration or operational correction most directly addresses this failure?

  1. Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic.
  2. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy.
  3. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends.
  4. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.

Explanation

Correct Answer

C:

Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service.

Incorrect Answers

A:

Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. This could matter when a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. In this case, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

B:

Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. That could help when large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU; here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

D:

Inspect label stack, bottom-of-stack indicator, and the expected transport operation. It is relevant if operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header, but the reported issue is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 922

At fictional Northpoint Access 231, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Which Junos forwarding or control-plane rule applies to this case?

  1. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.
  2. GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint.
  3. A tunnel must not rely on its own encapsulated path to reach the outer endpoint.
  4. IS-IS can advertise enabled IPv6 information independently of IPv4 reachability.

Explanation

Correct Answer

A:

Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service.

Incorrect Answers

B:

GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. This could matter when a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. In this case, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

C:

A tunnel must not rely on its own encapsulated path to reach the outer endpoint. That could help when a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution; here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

D:

IS-IS can advertise enabled IPv6 information independently of IPv4 reachability. This is applicable when a core network runs IS-IS for IPv4 but has no IPv6 service reachability after dual-stack activation; the present condition is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 923

At fictional Northpoint Access 231, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. What operational evidence best establishes successful remediation?

  1. The outer endpoint routes through the physical transit and tunnel probes succeed without recursion.
  2. Outer reachability and an encapsulated test both succeed over the tunnel.
  3. A controlled packet trace follows the intended segment program under the chosen IGP topology.
  4. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service.

Explanation

Correct Answer

D:

Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends.

Incorrect Answers

A:

The outer endpoint routes through the physical transit and tunnel probes succeed without recursion. That option concerns a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution. The problem here is different: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

B:

Outer reachability and an encapsulated test both succeed over the tunnel. It addresses a different problem: A configured GRE tunnel stays unusable after the remote outer IP endpoint changes. Here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

C:

A controlled packet trace follows the intended segment program under the chosen IGP topology. This could matter when a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path. In this case, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 924

At fictional Northpoint Access 231, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Which operational harm would persist without the intended correction?

  1. Tunnel establishment loops or collapses during forwarding changes.
  2. Overlay routes remain configured but customer packets never reach the remote site.
  3. A hidden encapsulation or decapsulation fault persists behind a green interface alarm.
  4. MPLS traffic cannot use the planned engineered transport path.

Explanation

Correct Answer

C:

A hidden encapsulation or decapsulation fault persists behind a green interface alarm. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends.

Incorrect Answers

A:

Tunnel establishment loops or collapses during forwarding changes. The choice would be appropriate if a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution. Here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

B:

Overlay routes remain configured but customer packets never reach the remote site. That option concerns a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. The problem here is different: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

D:

MPLS traffic cannot use the planned engineered transport path. This could matter when an RSVP LSP stays down but engineers only examine the ingress router's IP default route. In this case, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 925

In a separate fictional JNCIS-SP lab review for Linden Point 232, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. What should the Junos specialist change first to resolve this specific fault?

  1. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends.
  2. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy.
  3. Use the approved source address and confirm matching outer-packet forwarding and policy.
  4. Restore suitable L1-L2 connectivity or the documented route-leaking/default behavior.

Explanation

Correct Answer

A:

Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.

Incorrect Answers

B:

Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. The choice would be appropriate if large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. Here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

C:

Use the approved source address and confirm matching outer-packet forwarding and policy. That option concerns a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. The problem here is different: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

D:

Restore suitable L1-L2 connectivity or the documented route-leaking/default behavior. It addresses a different problem: An L1-only site lacks an approved route to reach destinations in the backbone after a level-transition change. Here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 926

In a separate fictional JNCIS-SP lab review for Linden Point 232, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. What technical principle underlies the right remedy?

  1. Tunnel endpoints must use source and destination addresses that the underlay can route and permit.
  2. GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint.
  3. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.
  4. A passive interface can advertise connected reachability without sending OSPF hellos to customers.

Explanation

Correct Answer

C:

Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends.

Incorrect Answers

A:

Tunnel endpoints must use source and destination addresses that the underlay can route and permit. That relates to circumstances in which a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Here the problem is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

B:

GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. This addresses a situation in which a configured GRE tunnel stays unusable after the remote outer IP endpoint changes; however, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

D:

A passive interface can advertise connected reachability without sending OSPF hellos to customers. That option concerns a provider PE inadvertently attempts to form an OSPF adjacency on a customer LAN that should advertise reachability only. The problem here is different: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 927

In a separate fictional JNCIS-SP lab review for Linden Point 232, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Which acceptance finding demonstrates the affected service has recovered?

  1. The outer endpoint routes through the physical transit and tunnel probes succeed without recursion.
  2. A capture shows outer packets with the approved source and destination and working return traffic.
  3. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service.
  4. Expected DR and BDR peers are Full while the relevant non-DR relationship can legitimately remain 2-Way.

Explanation

Correct Answer

C:

Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.

Incorrect Answers

A:

The outer endpoint routes through the physical transit and tunnel probes succeed without recursion. It is useful for situations where a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution; the reported fault, though, is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

B:

A capture shows outer packets with the approved source and destination and working return traffic. That relates to circumstances in which a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Here the problem is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

D:

Expected DR and BDR peers are Full while the relevant non-DR relationship can legitimately remain 2-Way. The choice would be appropriate if on a broadcast segment, one non-designated router shows a peer at 2-Way and an operator incorrectly treats it as a failure. Here, monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 928

In a separate fictional JNCIS-SP lab review for Linden Point 232, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. What is the direct residual network risk if the fault remains unresolved?

  1. Applications suffer selective stalls and retransmissions.
  2. Tunnel establishment loops or collapses during forwarding changes.
  3. Traffic follows an obsolete service path or reaches the wrong customer site.
  4. A hidden encapsulation or decapsulation fault persists behind a green interface alarm.

Explanation

Correct Answer

D:

A hidden encapsulation or decapsulation fault persists behind a green interface alarm. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.

Incorrect Answers

A:

Applications suffer selective stalls and retransmissions. This relates to a case where large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU; the current situation is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

B:

Tunnel establishment loops or collapses during forwarding changes. It is useful for situations where a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution; the reported fault, though, is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

C:

Traffic follows an obsolete service path or reaches the wrong customer site. That relates to circumstances in which a MAC is learned on an unexpected aggregation interface following a customer circuit move. Here the problem is that monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered.

Question 929

At fictional Harborview ISP 233, a regional service-provider network, during a two-site transit migration, operations observes: A bundled uplink has two configured members but only one is usable because the second member's operational parameters differ. Which targeted remediation best fits the reported behavior?

  1. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.
  2. Align supported member configuration and verify aggregation state and distributed traffic.
  3. Enable and verify supported nonstop active routing with required redundancy prerequisites.
  4. Compare protocol route state with the active route and forwarding-table next-hop installation.

Explanation

Correct Answer

B:

Align supported member configuration and verify aggregation state and distributed traffic. A link aggregation group forwards correctly only over members meeting the operational bundle requirements. Both intended links join the bundle and sample traffic uses approved members.

Incorrect Answers

A:

Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. This could help if a provider assumes graceful restart will work during a routing process restart without considering neighbor support, but not when a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ.

C:

Enable and verify supported nonstop active routing with required redundancy prerequisites. It is useful for situations where traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state; the reported fault, though, is that a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ.

D:

Compare protocol route state with the active route and forwarding-table next-hop installation. That relates to circumstances in which an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Here the problem is that a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ.

Question 930

At fictional Harborview ISP 233, a regional service-provider network, during a two-site transit migration, operations observes: A bundled uplink has two configured members but only one is usable because the second member's operational parameters differ. Why is this particular correction the best fit for the stated defect?

  1. A link aggregation group forwards correctly only over members meeting the operational bundle requirements.
  2. High availability must be evaluated by usable service forwarding as well as control-plane states.
  3. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.
  4. A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane.

Explanation

Correct Answer

A:

A link aggregation group forwards correctly only over members meeting the operational bundle requirements. Align supported member configuration and verify aggregation state and distributed traffic. Both intended links join the bundle and sample traffic uses approved members.

Incorrect Answers

B:

High availability must be evaluated by usable service forwarding as well as control-plane states. This could help if an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover, but not when a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ.

C:

Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. This relates to a case where a provider assumes graceful restart will work during a routing process restart without considering neighbor support; the current situation is that a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ.

D:

A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. It is useful for situations where the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change; the reported fault, though, is that a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests