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 73

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.

Question 721

At fictional Northpoint Access 181, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. Which targeted remediation best fits the reported behavior?

  1. Perform controlled LSP validation and only then switch the authorized service resolution.
  2. Recalculate the supported reservation and link bandwidth design before retrying.
  3. Use an appropriate segment list or routing design matching the required steering behavior.
  4. Constrain permitted VLAN membership and confirm unauthorized tag handling.

Explanation

Correct Answer

B:

Recalculate the supported reservation and link bandwidth design before retrying. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. LSP signaling succeeds with compatible reservation values and reported resource state.

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 RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

Use an appropriate segment list or routing design matching the required steering behavior. 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 LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

D:

Constrain permitted VLAN membership and confirm unauthorized tag handling. It addresses a different problem: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Here, an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 722

At fictional Northpoint Access 181, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. Why is this particular correction the best fit for the stated defect?

  1. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources.
  2. RSVP-TE can establish signaled LSPs subject to configured path constraints.
  3. Penultimate-hop popping can remove the outer transport label before the final LSR.
  4. An Ethernet port's VLAN tagging behavior must match the frames it receives.

Explanation

Correct Answer

A:

RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. Recalculate the supported reservation and link bandwidth design before retrying. LSP signaling succeeds with compatible reservation values and reported resource state.

Incorrect Answers

B:

RSVP-TE can establish signaled LSPs subject to configured path constraints. This addresses a situation in which an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route; however, an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

Penultimate-hop popping can remove the outer transport label before the final LSR. The choice would be appropriate if an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Here, an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

D:

An Ethernet port's VLAN tagging behavior must match the frames it receives. That option concerns a provider access port drops customer tagged frames because it was configured for untagged access mode. The problem here is different: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 723

At fictional Northpoint Access 181, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. What direct observation would prove the corrective action worked?

  1. The target prefix SID resolves to the planned node and the corresponding SR LSP is active.
  2. An MPLS-aware trace and service probe pass before and after the selected cutover.
  3. LSP signaling succeeds with compatible reservation values and reported resource state.
  4. Both endpoint IPv4 routes and encapsulated IPv6 packet tests succeed.

Explanation

Correct Answer

C:

LSP signaling succeeds with compatible reservation values and reported resource state. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. Recalculate the supported reservation and link bandwidth design before retrying.

Incorrect Answers

A:

The target prefix SID resolves to the planned node and the corresponding SR LSP is active. It is useful for situations where a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation; the reported fault, though, is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

B:

An MPLS-aware trace and service probe pass before and after the selected cutover. That relates to circumstances in which a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Here the problem is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

D:

Both endpoint IPv4 routes and encapsulated IPv6 packet tests succeed. The choice would be appropriate if an IPv6 service is carried through an IPv4 underlay, but the tunnel endpoint's IPv4 route has disappeared. Here, an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 724

At fictional Northpoint Access 181, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. Which failure consequence follows most closely from ignoring this issue?

  1. MPLS traffic remains broken despite restored IGP neighbors.
  2. A partial label-distribution failure persists without an alert.
  3. Subscribers see extended connectivity interruptions after routine link changes.
  4. The engineered service remains unavailable or overcommits transit capacity.

Explanation

Correct Answer

D:

The engineered service remains unavailable or overcommits transit capacity. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. Recalculate the supported reservation and link bandwidth design before retrying.

Incorrect Answers

A:

MPLS traffic remains broken despite restored IGP neighbors. This relates to a case where after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the current situation is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

B:

A partial label-distribution failure persists without an alert. It is useful for situations where monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback; the reported fault, though, is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

Subscribers see extended connectivity interruptions after routine link changes. That relates to circumstances in which a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Here the problem is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 725

In a separate fictional JNCIS-SP lab review for Linden Point 182, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. What intervention most directly restores the intended routing or switching behavior?

  1. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.
  2. Check transit MPLS forwarding state and repair the missing label operation.
  3. Check the appropriate inet6 routing instance and forwarding state.
  4. Recalculate the supported reservation and link bandwidth design before retrying.

Explanation

Correct Answer

D:

Recalculate the supported reservation and link bandwidth design before retrying. LSP signaling succeeds with compatible reservation values and reported resource state. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources.

Incorrect Answers

A:

Review RSVP path constraints and explicit-route settings, then reestablish the LSP. This could help if an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route, but not when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

B:

Check transit MPLS forwarding state and repair the missing label operation. This relates to a case where an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing; the current situation is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

Check the appropriate inet6 routing instance and forwarding state. It is useful for situations where a support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised; the reported fault, though, is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 726

In a separate fictional JNCIS-SP lab review for Linden Point 182, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. Which networking principle explains why the proposed correction is appropriate?

  1. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources.
  2. Protocol adjacency health does not prove every required MPLS forwarding entry exists.
  3. MPLS label forwarding must follow the current resolved transport topology.
  4. Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently.

Explanation

Correct Answer

A:

RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. LSP signaling succeeds with compatible reservation values and reported resource state. Recalculate the supported reservation and link bandwidth design before retrying.

Incorrect Answers

B:

Protocol adjacency health does not prove every required MPLS forwarding entry exists. This could help if monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback, but not when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

MPLS label forwarding must follow the current resolved transport topology. This relates to a case where after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the current situation is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

D:

Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. It is useful for situations where an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port; the reported fault, though, is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 727

In a separate fictional JNCIS-SP lab review for Linden Point 182, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. Which validation result would confirm the design is now functioning?

  1. An MPLS-aware trace and service probe pass before and after the selected cutover.
  2. The target loopback FEC has a valid binding and corresponding programmed label action.
  3. The interface unit is operational and the connected subnet appears in the correct routing table.
  4. LSP signaling succeeds with compatible reservation values and reported resource state.

Explanation

Correct Answer

D:

LSP signaling succeeds with compatible reservation values and reported resource state. Recalculate the supported reservation and link bandwidth design before retrying. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources.

Incorrect Answers

A:

An MPLS-aware trace and service probe pass before and after the selected cutover. This is applicable when a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; the present condition is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

B:

The target loopback FEC has a valid binding and corresponding programmed label action. It is relevant if monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback, but the reported issue is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

The interface unit is operational and the connected subnet appears in the correct routing table. This could help if a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout, but not when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 728

In a separate fictional JNCIS-SP lab review for Linden Point 182, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. What likely service impact does this condition create?

  1. A premium customer service traverses a congested or disallowed link.
  2. The engineered service remains unavailable or overcommits transit capacity.
  3. MPLS traffic cannot use the planned engineered transport path.
  4. A supposedly restrictive policy inadvertently advertises internal routes.

Explanation

Correct Answer

B:

The engineered service remains unavailable or overcommits transit capacity. Recalculate the supported reservation and link bandwidth design before retrying. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources.

Incorrect Answers

A:

A premium customer service traverses a congested or disallowed link. That could help when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route; here, an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

C:

MPLS traffic cannot use the planned engineered transport path. It is relevant if an RSVP LSP stays down but engineers only examine the ingress router's IP default route, but the reported issue is that an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

D:

A supposedly restrictive policy inadvertently advertises internal routes. This could help if a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through, but not when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link.

Question 729

At fictional Harborview ISP 183, a regional service-provider network, during a two-site transit migration, operations observes: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. Which configuration or operational correction most directly addresses this failure?

  1. Validate the advertised label behavior and egress processing expectations.
  2. Interpret MPLS TTL and traceroute behavior using the configured transport model.
  3. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.
  4. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure.

Explanation

Correct Answer

D:

Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Signaled label-switched paths have distinct control-plane establishment and error states. The failing RSVP hop is identified and the LSP reports Up after correction.

Incorrect Answers

A:

Validate the advertised label behavior and egress processing expectations. This could matter when an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. In this case, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.

B:

Interpret MPLS TTL and traceroute behavior using the configured transport model. That could help when traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut; here, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.

C:

Review negotiated hold time and keepalive settings alongside transport health, then correct the design. This is applicable when a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; the present condition is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route.

Question 730

At fictional Harborview ISP 183, a regional service-provider network, during a two-site transit migration, operations observes: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. 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. LDP discovery and the TCP-based LDP session depend on usable transport reachability.
  3. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.
  4. Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs.

Explanation

Correct Answer

A:

Signaled label-switched paths have distinct control-plane establishment and error states. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. The failing RSVP hop is identified and the LSP reports Up after correction.

Incorrect Answers

B:

LDP discovery and the TCP-based LDP session depend on usable transport reachability. This could matter when two core routers cannot form an LDP session even though they discover one another on the connected link. In this case, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.

C:

MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. That could help when operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header; here, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.

D:

Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. This is applicable when a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the present condition is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route.

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