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 70

Question 690

At fictional Stonefield Telecom 173, a regional service-provider network, during a two-site transit migration, operations observes: Two core routers cannot form an LDP session even though they discover one another on the connected link. Why is this particular correction the best fit for the stated defect?

  1. A prefix SID normally expresses reachability to a node or prefix along the underlying shortest path.
  2. Segment routing uses advertised segment identifiers to steer packets across an MPLS topology.
  3. BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers.
  4. LDP discovery and the TCP-based LDP session depend on usable transport reachability.

Explanation

Correct Answer

D:

LDP discovery and the TCP-based LDP session depend on usable transport reachability. Check LDP transport address reachability and session parameters through the IGP. The LDP neighbor is operational and exchanges label mappings for expected FECs.

Incorrect Answers

A:

A prefix SID normally expresses reachability to a node or prefix along the underlying shortest path. It is relevant if a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path, but the reported issue is that two core routers cannot form an LDP session even though they discover one another on the connected link.

B:

Segment routing uses advertised segment identifiers to steer packets across an MPLS topology. This could help if a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation, but not when two core routers cannot form an LDP session even though they discover one another on the connected link.

C:

BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers. This relates to a case where a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; the current situation is that two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 691

At fictional Stonefield Telecom 173, a regional service-provider network, during a two-site transit migration, operations observes: Two core routers cannot form an LDP session even though they discover one another on the connected link. What direct observation would prove the corrective action worked?

  1. The link carries protected MPLS traffic only after the required label state is available.
  2. All transit hops display usable label bindings for the target FEC.
  3. The target table contains the approved route while unrelated tenant tables remain unchanged.
  4. The LDP neighbor is operational and exchanges label mappings for expected FECs.

Explanation

Correct Answer

D:

The LDP neighbor is operational and exchanges label mappings for expected FECs. LDP discovery and the TCP-based LDP session depend on usable transport reachability. Check LDP transport address reachability and session parameters through the IGP.

Incorrect Answers

A:

The link carries protected MPLS traffic only after the required label state is available. This is applicable when a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage; the present condition is that two core routers cannot form an LDP session even though they discover one another on the connected link.

B:

All transit hops display usable label bindings for the target FEC. It is relevant if an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop, but the reported issue is that two core routers cannot form an LDP session even though they discover one another on the connected link.

C:

The target table contains the approved route while unrelated tenant tables remain unchanged. This could help if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table, but not when two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 692

At fictional Stonefield Telecom 173, a regional service-provider network, during a two-site transit migration, operations observes: Two core routers cannot form an LDP session even though they discover one another on the connected link. Which failure consequence follows most closely from ignoring this issue?

  1. Traffic is briefly blackholed during normal network convergence.
  2. MPLS traffic remains broken despite restored IGP neighbors.
  3. Traffic unexpectedly overloads a low-capacity link.
  4. Transport LSPs are absent despite healthy basic IP routing.

Explanation

Correct Answer

D:

Transport LSPs are absent despite healthy basic IP routing. LDP discovery and the TCP-based LDP session depend on usable transport reachability. Check LDP transport address reachability and session parameters through the IGP.

Incorrect Answers

A:

Traffic is briefly blackholed during normal network convergence. That could help when a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage; here, two core routers cannot form an LDP session even though they discover one another on the connected link.

B:

MPLS traffic remains broken despite restored IGP neighbors. This is applicable when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the present condition is that two core routers cannot form an LDP session even though they discover one another on the connected link.

C:

Traffic unexpectedly overloads a low-capacity link. It is relevant if an intended core link metric is truncated by a mismatched metric-style design and fails to shift paths as expected, but the reported issue is that two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 693

In a separate fictional JNCIS-SP lab review for Clearwater Peering 174, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Two core routers cannot form an LDP session even though they discover one another on the connected link. What intervention most directly restores the intended routing or switching behavior?

  1. Apply the supported LDP and IGP synchronization design and verify staged activation.
  2. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure.
  3. Check LDP transport address reachability and session parameters through the IGP.
  4. Use root protection on designated protected links and verify superior BPDU handling.

Explanation

Correct Answer

C:

Check LDP transport address reachability and session parameters through the IGP. The LDP neighbor is operational and exchanges label mappings for expected FECs. LDP discovery and the TCP-based LDP session depend on usable transport reachability.

Incorrect Answers

A:

Apply the supported LDP and IGP synchronization design and verify staged activation. This could matter when a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. In this case, two core routers cannot form an LDP session even though they discover one another on the connected link.

B:

Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. That could help when an RSVP LSP stays down but engineers only examine the ingress router's IP default route; here, two core routers cannot form an LDP session even though they discover one another on the connected link.

D:

Use root protection on designated protected links and verify superior BPDU handling. It is relevant if a customer-facing bridge advertises a superior root and takes over the provider STP topology, but the reported issue is that two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 694

In a separate fictional JNCIS-SP lab review for Clearwater Peering 174, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Two core routers cannot form an LDP session even though they discover one another on the connected link. Which networking principle explains why the proposed correction is appropriate?

  1. LDP distributes label mappings needed for label-switched forwarding paths.
  2. LDP discovery and the TCP-based LDP session depend on usable transport reachability.
  3. MPLS transit forwarding depends on installed label operations at each participating node.
  4. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.

Explanation

Correct Answer

B:

LDP discovery and the TCP-based LDP session depend on usable transport reachability. The LDP neighbor is operational and exchanges label mappings for expected FECs. Check LDP transport address reachability and session parameters through the IGP.

Incorrect Answers

A:

LDP distributes label mappings needed for label-switched forwarding paths. It addresses a different problem: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Here, two core routers cannot form an LDP session even though they discover one another on the connected link.

C:

MPLS transit forwarding depends on installed label operations at each participating node. That could help when an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing; here, two core routers cannot form an LDP session even though they discover one another on the connected link.

D:

Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. This is applicable when a provider assumes graceful restart will work during a routing process restart without considering neighbor support; the present condition is that two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 695

In a separate fictional JNCIS-SP lab review for Clearwater Peering 174, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Two core routers cannot form an LDP session even though they discover one another on the connected link. Which validation result would confirm the design is now functioning?

  1. The route resolves through an operational LSP and test traffic reaches the remote endpoint.
  2. The active label operation now uses the recovered egress next hop.
  3. The LDP neighbor is operational and exchanges label mappings for expected FECs.
  4. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval.

Explanation

Correct Answer

C:

The LDP neighbor is operational and exchanges label mappings for expected FECs. Check LDP transport address reachability and session parameters through the IGP. LDP discovery and the TCP-based LDP session depend on usable transport reachability.

Incorrect Answers

A:

The route resolves through an operational LSP and test traffic reaches the remote endpoint. That option concerns a service path references an LSP that is down, but its IP route remains visible in the route table. The problem here is different: Two core routers cannot form an LDP session even though they discover one another on the connected link.

B:

The active label operation now uses the recovered egress next hop. It addresses a different problem: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Here, two core routers cannot form an LDP session even though they discover one another on the connected link.

D:

Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. That could help when a provider assumes graceful restart will work during a routing process restart without considering neighbor support; here, two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 696

In a separate fictional JNCIS-SP lab review for Clearwater Peering 174, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Two core routers cannot form an LDP session even though they discover one another on the connected link. What likely service impact does this condition create?

  1. MPLS traffic remains broken despite restored IGP neighbors.
  2. A sensitive workload unexpectedly traverses a different core link.
  3. Traffic leaks or becomes blackholed at the L2/L3 boundary.
  4. Transport LSPs are absent despite healthy basic IP routing.

Explanation

Correct Answer

D:

Transport LSPs are absent despite healthy basic IP routing. Check LDP transport address reachability and session parameters through the IGP. LDP discovery and the TCP-based LDP session depend on usable transport reachability.

Incorrect Answers

A:

MPLS traffic remains broken despite restored IGP neighbors. The choice would be appropriate if after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Here, two core routers cannot form an LDP session even though they discover one another on the connected link.

B:

A sensitive workload unexpectedly traverses a different core link. That option concerns a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path. The problem here is different: Two core routers cannot form an LDP session even though they discover one another on the connected link.

C:

Traffic leaks or becomes blackholed at the L2/L3 boundary. It addresses a different problem: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Here, two core routers cannot form an LDP session even though they discover one another on the connected link.

Question 697

At fictional Glenwood Connectivity 175, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Which configuration or operational correction most directly addresses this failure?

  1. Perform controlled LSP validation and only then switch the authorized service resolution.
  2. Restore the intended LSP or safe route resolution and verify the forwarding next hop.
  3. Check label advertisements for the FEC and restore a valid LDP downstream binding.
  4. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration.

Explanation

Correct Answer

C:

Check label advertisements for the FEC and restore a valid LDP downstream binding. LDP distributes label mappings needed for label-switched forwarding paths. All transit hops display usable label bindings for the target FEC.

Incorrect Answers

A:

Perform controlled LSP validation and only then switch the authorized service resolution. This addresses a situation in which a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; however, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

B:

Restore the intended LSP or safe route resolution and verify the forwarding next hop. The choice would be appropriate if a service path references an LSP that is down, but its IP route remains visible in the route table. Here, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

D:

Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. It addresses a different problem: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. Here, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

Question 698

At fictional Glenwood Connectivity 175, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Which Junos forwarding or control-plane rule applies to this case?

  1. Signaled label-switched paths have distinct control-plane establishment and error states.
  2. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits.
  3. LDP distributes label mappings needed for label-switched forwarding paths.
  4. A passive interface can advertise connected reachability without sending OSPF hellos to customers.

Explanation

Correct Answer

C:

LDP distributes label mappings needed for label-switched forwarding paths. Check label advertisements for the FEC and restore a valid LDP downstream binding. All transit hops display usable label bindings for the target FEC.

Incorrect Answers

A:

Signaled label-switched paths have distinct control-plane establishment and error states. That relates to circumstances in which an RSVP LSP stays down but engineers only examine the ingress router's IP default route. Here the problem is that an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

B:

MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. This addresses a situation in which a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; however, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

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: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

Question 699

At fictional Glenwood Connectivity 175, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. What operational evidence best establishes successful remediation?

  1. All transit hops display usable label bindings for the target FEC.
  2. The RSVP LSP is up with the intended transit hop sequence.
  3. The penultimate and egress forwarding entries match the intended label disposition.
  4. Both client sessions stabilize and expected reflected routes reach peers.

Explanation

Correct Answer

A:

All transit hops display usable label bindings for the target FEC. LDP distributes label mappings needed for label-switched forwarding paths. Check label advertisements for the FEC and restore a valid LDP downstream binding.

Incorrect Answers

B:

The RSVP LSP is up with the intended transit hop sequence. That relates to circumstances in which an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Here the problem is that an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

C:

The penultimate and egress forwarding entries match the intended label disposition. This addresses a situation in which an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP; however, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

D:

Both client sessions stabilize and expected reflected routes reach peers. The choice would be appropriate if an internal client learns routes from another client only intermittently after the route-reflector peering address changes. Here, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

Question 700

At fictional Glenwood Connectivity 175, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Which operational harm would persist without the intended correction?

  1. Packets cannot travel the intended MPLS transport path.
  2. Traffic bypasses an approved low-latency or protected path.
  3. Labeled packets are discarded at the affected core node.
  4. Misdiagnosis delays restoration because absent control-plane information is overlooked.

Explanation

Correct Answer

A:

Packets cannot travel the intended MPLS transport path. LDP distributes label mappings needed for label-switched forwarding paths. Check label advertisements for the FEC and restore a valid LDP downstream binding.

Incorrect Answers

B:

Traffic bypasses an approved low-latency or protected path. It is useful for situations where a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change; the reported fault, though, is that an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

C:

Labeled packets are discarded at the affected core node. That relates to circumstances in which an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. Here the problem is that an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

D:

Misdiagnosis delays restoration because absent control-plane information is overlooked. This addresses a situation in which operators expect a customer prefix from another area but only inspect local interface counters and never examine link-state advertisements; however, an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop.

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