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 72

Question 710

In a separate fictional JNCIS-SP lab review for Crestland Networks 178, a carrier-edge and core routing team, following a monitored network change window, engineers find: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Which networking principle explains why the proposed correction is appropriate?

  1. Segment routing uses advertised segment identifiers to steer packets across an MPLS topology.
  2. MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding.
  3. Protocol adjacency health does not prove every required MPLS forwarding entry exists.
  4. GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint.

Explanation

Correct Answer

B:

MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding. The link carries protected MPLS traffic only after the required label state is available. Apply the supported LDP and IGP synchronization design and verify staged activation.

Incorrect Answers

A:

Segment routing uses advertised segment identifiers to steer packets across an MPLS topology. That relates to circumstances in which a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. Here the problem is that a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

C:

Protocol adjacency health does not prove every required MPLS forwarding entry exists. The choice would be appropriate if monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Here, a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

D:

GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. That option concerns a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. The problem here is different: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

Question 711

In a separate fictional JNCIS-SP lab review for Crestland Networks 178, a carrier-edge and core routing team, following a monitored network change window, engineers find: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Which validation result would confirm the design is now functioning?

  1. The selected service resolves over the intended RSVP LSP and follows engineered hops.
  2. The target prefix SID resolves to the planned node and the corresponding SR LSP is active.
  3. The link carries protected MPLS traffic only after the required label state is available.
  4. The authorized IPv6 prefixes arrive in the intended inet6 table without IPv4 policy changes.

Explanation

Correct Answer

C:

The link carries protected MPLS traffic only after the required label state is available. Apply the supported LDP and IGP synchronization design and verify staged activation. MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding.

Incorrect Answers

A:

The selected service resolves over the intended RSVP LSP and follows engineered hops. 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 a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

B:

The target prefix SID resolves to the planned node and the corresponding SR LSP is active. That relates to circumstances in which a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. Here the problem is that a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

D:

The authorized IPv6 prefixes arrive in the intended inet6 table without IPv4 policy changes. The choice would be appropriate if an established BGP peer exchanges IPv4 but rejects all authorized IPv6 prefixes due to a misplaced family-specific filter. Here, a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

Question 712

In a separate fictional JNCIS-SP lab review for Crestland Networks 178, a carrier-edge and core routing team, following a monitored network change window, engineers find: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. What likely service impact does this condition create?

  1. Traffic bypasses an approved low-latency or protected path.
  2. Customers experience a blackhole hidden by otherwise present route advertisements.
  3. Traffic is briefly blackholed during normal network convergence.
  4. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes.

Explanation

Correct Answer

C:

Traffic is briefly blackholed during normal network convergence. Apply the supported LDP and IGP synchronization design and verify staged activation. MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding.

Incorrect Answers

A:

Traffic bypasses an approved low-latency or protected path. This relates to a case where a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change; the current situation is that a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

B:

Customers experience a blackhole hidden by otherwise present route advertisements. It is useful for situations where a service path references an LSP that is down, but its IP route remains visible in the route table; the reported fault, though, is that a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

D:

Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. This addresses a situation in which a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; however, a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage.

Question 713

At fictional Silverlake Routing 179, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Which configuration or operational correction most directly addresses this failure?

  1. Check LDP transport address reachability and session parameters through the IGP.
  2. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.
  3. Enable the intended IPv6 OSPFv3 configuration and verify neighbor and route state.
  4. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.

Explanation

Correct Answer

D:

Review RSVP path constraints and explicit-route settings, then reestablish the LSP. RSVP-TE can establish signaled LSPs subject to configured path constraints. The RSVP LSP is up with the intended transit hop sequence.

Incorrect Answers

A:

Check LDP transport address reachability and session parameters through the IGP. This could help if two core routers cannot form an LDP session even though they discover one another on the connected link, but not when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

B:

Inspect label stack, bottom-of-stack indicator, and the expected transport operation. This relates to a case where operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header; the current situation is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

Enable the intended IPv6 OSPFv3 configuration and verify neighbor and route state. It is useful for situations where an IPv6 prefix is missing across a point-to-point link because OSPFv2 was configured but OSPFv3 was omitted; the reported fault, though, is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 714

At fictional Silverlake Routing 179, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Which Junos forwarding or control-plane rule applies to this case?

  1. RSVP-TE can establish signaled LSPs subject to configured path constraints.
  2. A route's presence is insufficient if its selected MPLS transport next hop is unusable.
  3. Penultimate-hop popping can remove the outer transport label before the final LSR.
  4. Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs.

Explanation

Correct Answer

A:

RSVP-TE can establish signaled LSPs subject to configured path constraints. Review RSVP path constraints and explicit-route settings, then reestablish the LSP. The RSVP LSP is up with the intended transit hop sequence.

Incorrect Answers

B:

A route's presence is insufficient if its selected MPLS transport next hop is unusable. This could help if a service path references an LSP that is down, but its IP route remains visible in the route table, but not when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

Penultimate-hop popping can remove the outer transport label before the final LSR. This relates to a case where an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP; the current situation is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

D:

Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. It is useful for situations where a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the reported fault, though, is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 715

At fictional Silverlake Routing 179, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. What operational evidence best establishes successful remediation?

  1. The RSVP LSP is up with the intended transit hop sequence.
  2. Packet observations match the intended push, swap, and disposition stages.
  3. A targeted incoming label maps to the intended outgoing label and interface.
  4. The port's intentional blocking reason and root path are verified in control-plane output.

Explanation

Correct Answer

A:

The RSVP LSP is up with the intended transit hop sequence. RSVP-TE can establish signaled LSPs subject to configured path constraints. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.

Incorrect Answers

B:

Packet observations match the intended push, swap, and disposition stages. It is relevant if a network test expects the ingress PE to swap a label that it should actually impose, but the reported issue is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

A targeted incoming label maps to the intended outgoing label and interface. This could help if an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing, but not when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

D:

The port's intentional blocking reason and root path are verified in control-plane output. This relates to a case where a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics; the current situation is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 716

At fictional Silverlake Routing 179, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Which operational harm would persist without the intended correction?

  1. Transport LSPs are absent despite healthy basic IP routing.
  2. Packets cannot travel the intended MPLS transport path.
  3. A correct broadcast network is disrupted by unnecessary configuration changes.
  4. A premium customer service traverses a congested or disallowed link.

Explanation

Correct Answer

D:

A premium customer service traverses a congested or disallowed link. RSVP-TE can establish signaled LSPs subject to configured path constraints. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.

Incorrect Answers

A:

Transport LSPs are absent despite healthy basic IP routing. That could help when two core routers cannot form an LDP session even though they discover one another on the connected link; here, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

B:

Packets cannot travel the intended MPLS transport path. This is applicable when an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop; the present condition is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

A correct broadcast network is disrupted by unnecessary configuration changes. It is relevant if on a broadcast segment, one non-designated router shows a peer at 2-Way and an operator incorrectly treats it as a failure, but the reported issue is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 717

In a separate fictional JNCIS-SP lab review for Seabrook Metro 180, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. What should the Junos specialist change first to resolve this specific fault?

  1. Restore the intended LSP or safe route resolution and verify the forwarding next hop.
  2. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.
  3. Recalculate the supported reservation and link bandwidth design before retrying.
  4. Enable and verify supported nonstop active routing with required redundancy prerequisites.

Explanation

Correct Answer

B:

Review RSVP path constraints and explicit-route settings, then reestablish the LSP. The RSVP LSP is up with the intended transit hop sequence. RSVP-TE can establish signaled LSPs subject to configured path constraints.

Incorrect Answers

A:

Restore the intended LSP or safe route resolution and verify the forwarding next hop. This could matter when a service path references an LSP that is down, but its IP route remains visible in the route table. In this case, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

Recalculate the supported reservation and link bandwidth design before retrying. This is applicable when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; the present condition is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

D:

Enable and verify supported nonstop active routing with required redundancy prerequisites. It is relevant if traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state, but the reported issue is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 718

In a separate fictional JNCIS-SP lab review for Seabrook Metro 180, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. What technical principle underlies the right remedy?

  1. Signaled label-switched paths have distinct control-plane establishment and error states.
  2. RSVP-TE can establish signaled LSPs subject to configured path constraints.
  3. MPLS label forwarding must follow the current resolved transport topology.
  4. Bridge-table observations must be interpreted alongside actual physical and logical port membership.

Explanation

Correct Answer

B:

RSVP-TE can establish signaled LSPs subject to configured path constraints. The RSVP LSP is up with the intended transit hop sequence. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.

Incorrect Answers

A:

Signaled label-switched paths have distinct control-plane establishment and error states. It addresses a different problem: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. Here, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

MPLS label forwarding must follow the current resolved transport topology. That could help when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; here, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

D:

Bridge-table observations must be interpreted alongside actual physical and logical port membership. This is applicable when a MAC is learned on an unexpected aggregation interface following a customer circuit move; the present condition is that an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 719

In a separate fictional JNCIS-SP lab review for Seabrook Metro 180, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Which acceptance finding demonstrates the affected service has recovered?

  1. The RSVP LSP is up with the intended transit hop sequence.
  2. The link carries protected MPLS traffic only after the required label state is available.
  3. A controlled packet trace follows the intended segment program under the chosen IGP topology.
  4. An L1 router installs the intended route toward the L1-L2 boundary and reaches test destinations.

Explanation

Correct Answer

A:

The RSVP LSP is up with the intended transit hop sequence. Review RSVP path constraints and explicit-route settings, then reestablish the LSP. RSVP-TE can establish signaled LSPs subject to configured path constraints.

Incorrect Answers

B:

The link carries protected MPLS traffic only after the required label state is available. It addresses a different problem: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Here, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

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, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

D:

An L1 router installs the intended route toward the L1-L2 boundary and reaches test destinations. That could help when an L1-only site lacks an approved route to reach destinations in the backbone after a level-transition change; here, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

Question 720

In a separate fictional JNCIS-SP lab review for Seabrook Metro 180, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. What is the direct residual network risk if the fault remains unresolved?

  1. A premium customer service traverses a congested or disallowed link.
  2. A sensitive workload unexpectedly traverses a different core link.
  3. A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer.
  4. Duplicate identity produces unstable topology and confusing route calculations.

Explanation

Correct Answer

A:

A premium customer service traverses a congested or disallowed link. Review RSVP path constraints and explicit-route settings, then reestablish the LSP. RSVP-TE can establish signaled LSPs subject to configured path constraints.

Incorrect Answers

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: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

C:

A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer. It addresses a different problem: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Here, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

D:

Duplicate identity produces unstable topology and confusing route calculations. This could matter when two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template. In this case, an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route.

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