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 76

Question 750

In a separate fictional JNCIS-SP lab review for Windmere Fiber 188, a carrier-edge and core routing team, following a monitored network change window, engineers find: A network test expects the ingress PE to swap a label that it should actually impose. What technical principle underlies the right remedy?

  1. Protocol adjacency health does not prove every required MPLS forwarding entry exists.
  2. Segment routing uses advertised segment identifiers to steer packets across an MPLS topology.
  3. Route reflectors distribute selected IBGP reachability within the configured client topology.
  4. MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it.

Explanation

Correct Answer

D:

MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it. Packet observations match the intended push, swap, and disposition stages. Identify the ingress, transit, and egress LSR roles before modifying label rules.

Incorrect Answers

A:

Protocol adjacency health does not prove every required MPLS forwarding entry exists. 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 a network test expects the ingress PE to swap a label that it should actually impose.

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 a network test expects the ingress PE to swap a label that it should actually impose.

C:

Route reflectors distribute selected IBGP reachability within the configured client topology. This relates to a case where an internal client learns routes from another client only intermittently after the route-reflector peering address changes; the current situation is that a network test expects the ingress PE to swap a label that it should actually impose.

Question 751

In a separate fictional JNCIS-SP lab review for Windmere Fiber 188, a carrier-edge and core routing team, following a monitored network change window, engineers find: A network test expects the ingress PE to swap a label that it should actually impose. Which acceptance finding demonstrates the affected service has recovered?

  1. Packet observations match the intended push, swap, and disposition stages.
  2. A targeted incoming label maps to the intended outgoing label and interface.
  3. The penultimate and egress forwarding entries match the intended label disposition.
  4. A capture shows outer packets with the approved source and destination and working return traffic.

Explanation

Correct Answer

A:

Packet observations match the intended push, swap, and disposition stages. Identify the ingress, transit, and egress LSR roles before modifying label rules. MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it.

Incorrect Answers

B:

A targeted incoming label maps to the intended outgoing label and interface. It is relevant if an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing, but the reported issue is that a network test expects the ingress PE to swap a label that it should actually impose.

C:

The penultimate and egress forwarding entries match the intended label disposition. This could help if an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP, but not when a network test expects the ingress PE to swap a label that it should actually impose.

D:

A capture shows outer packets with the approved source and destination and working return traffic. This relates to a case where a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL; the current situation is that a network test expects the ingress PE to swap a label that it should actually impose.

Question 752

In a separate fictional JNCIS-SP lab review for Windmere Fiber 188, a carrier-edge and core routing team, following a monitored network change window, engineers find: A network test expects the ingress PE to swap a label that it should actually impose. What is the direct residual network risk if the fault remains unresolved?

  1. A correct label stack is broken by applying the wrong role assumption.
  2. Customers experience a blackhole hidden by otherwise present route advertisements.
  3. MPLS traffic remains broken despite restored IGP neighbors.
  4. A transit route remains unavailable because neighbor behavior is inconsistent.

Explanation

Correct Answer

A:

A correct label stack is broken by applying the wrong role assumption. Identify the ingress, transit, and egress LSR roles before modifying label rules. MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it.

Incorrect Answers

B:

Customers experience a blackhole hidden by otherwise present route advertisements. This is applicable when a service path references an LSP that is down, but its IP route remains visible in the route table; the present condition is that a network test expects the ingress PE to swap a label that it should actually impose.

C:

MPLS traffic remains broken despite restored IGP neighbors. It is relevant if after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device, but the reported issue is that a network test expects the ingress PE to swap a label that it should actually impose.

D:

A transit route remains unavailable because neighbor behavior is inconsistent. This could help if OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology, but not when a network test expects the ingress PE to swap a label that it should actually impose.

Question 753

At fictional Meadowcrest Telecom 189, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Which targeted remediation best fits the reported behavior?

  1. Correct the SID assignment and confirm the intended segment path resolves to that node.
  2. Restore the intended LSP or safe route resolution and verify the forwarding next hop.
  3. Validate the advertised label behavior and egress processing expectations.
  4. Align supported member configuration and verify aggregation state and distributed traffic.

Explanation

Correct Answer

C:

Validate the advertised label behavior and egress processing expectations. Penultimate-hop popping can remove the outer transport label before the final LSR. The penultimate and egress forwarding entries match the intended label disposition.

Incorrect Answers

A:

Correct the SID assignment and confirm the intended segment path resolves to that node. This could matter when a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. In this case, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

B:

Restore the intended LSP or safe route resolution and verify the forwarding next hop. That could help when a service path references an LSP that is down, but its IP route remains visible in the route table; here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

Align supported member configuration and verify aggregation state and distributed traffic. It is relevant if a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ, but the reported issue is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 754

At fictional Meadowcrest Telecom 189, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Why is this particular correction the best fit for the stated defect?

  1. Segment routing uses advertised segment identifiers to steer packets across an MPLS topology.
  2. Penultimate-hop popping can remove the outer transport label before the final LSR.
  3. MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it.
  4. Route reflectors distribute selected IBGP reachability within the configured client topology.

Explanation

Correct Answer

B:

Penultimate-hop popping can remove the outer transport label before the final LSR. Validate the advertised label behavior and egress processing expectations. The penultimate and egress forwarding entries match the intended label disposition.

Incorrect Answers

A:

Segment routing uses advertised segment identifiers to steer packets across an MPLS topology. It addresses a different problem: A provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. Here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

C:

MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it. That could help when a network test expects the ingress PE to swap a label that it should actually impose; here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

Route reflectors distribute selected IBGP reachability within the configured client topology. This is applicable when an internal client learns routes from another client only intermittently after the route-reflector peering address changes; the present condition is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 755

At fictional Meadowcrest Telecom 189, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. What direct observation would prove the corrective action worked?

  1. Packet capture and forwarding state show the intended outgoing transport label.
  2. The penultimate and egress forwarding entries match the intended label disposition.
  3. The RSVP LSP is up with the intended transit hop sequence.
  4. MAC entries stabilize on the intended interface after repairing the bridge path.

Explanation

Correct Answer

B:

The penultimate and egress forwarding entries match the intended label disposition. Penultimate-hop popping can remove the outer transport label before the final LSR. Validate the advertised label behavior and egress processing expectations.

Incorrect Answers

A:

Packet capture and forwarding state show the intended outgoing transport label. That option concerns operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. The problem here is different: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

C:

The RSVP LSP is up with the intended transit hop sequence. This could matter when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. In this case, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

MAC entries stabilize on the intended interface after repairing the bridge path. That could help when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 756

At fictional Meadowcrest Telecom 189, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Which failure consequence follows most closely from ignoring this issue?

  1. Packets cannot travel the intended MPLS transport path.
  2. A planned maintenance window causes an avoidable customer outage.
  3. Healthy MPLS transport is disrupted by a false fault diagnosis.
  4. Traffic follows an obsolete service path or reaches the wrong customer site.

Explanation

Correct Answer

C:

Healthy MPLS transport is disrupted by a false fault diagnosis. Penultimate-hop popping can remove the outer transport label before the final LSR. Validate the advertised label behavior and egress processing expectations.

Incorrect Answers

A:

Packets cannot travel the intended MPLS transport path. The choice would be appropriate if an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

B:

A planned maintenance window causes an avoidable customer outage. That option concerns a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. The problem here is different: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

Traffic follows an obsolete service path or reaches the wrong customer site. This could matter when a MAC is learned on an unexpected aggregation interface following a customer circuit move. In this case, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 757

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 190, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. What intervention most directly restores the intended routing or switching behavior?

  1. Recalculate the supported reservation and link bandwidth design before retrying.
  2. Perform controlled LSP validation and only then switch the authorized service resolution.
  3. Validate the advertised label behavior and egress processing expectations.
  4. Use the supported IS-IS overload behavior during maintenance and remove it when forwarding readiness is verified.

Explanation

Correct Answer

C:

Validate the advertised label behavior and egress processing expectations. The penultimate and egress forwarding entries match the intended label disposition. Penultimate-hop popping can remove the outer transport label before the final LSR.

Incorrect Answers

A:

Recalculate the supported reservation and link bandwidth design before retrying. This addresses a situation in which an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; however, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

B:

Perform controlled LSP validation and only then switch the authorized service resolution. The choice would be appropriate if a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

Use the supported IS-IS overload behavior during maintenance and remove it when forwarding readiness is verified. It addresses a different problem: A newly rebooted core router attracts transit traffic while its forwarding state is still being restored. Here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 758

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 190, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Which networking principle explains why the proposed correction is appropriate?

  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. IS-IS system IDs must uniquely represent participating routers in the routing domain.

Explanation

Correct Answer

C:

Penultimate-hop popping can remove the outer transport label before the final LSR. The penultimate and egress forwarding entries match the intended label disposition. Validate the advertised label behavior and egress processing expectations.

Incorrect Answers

A:

RSVP-TE can establish signaled LSPs subject to configured path constraints. 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 operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

B:

A route's presence is insufficient if its selected MPLS transport next hop is unusable. This addresses a situation in which a service path references an LSP that is down, but its IP route remains visible in the route table; however, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

IS-IS system IDs must uniquely represent participating routers in the routing domain. That option concerns a device cloned from a lab template has the same IS-IS system ID as a production router. The problem here is different: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 759

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 190, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Which validation result would confirm the design is now functioning?

  1. The active label operation now uses the recovered egress next hop.
  2. The penultimate and egress forwarding entries match the intended label disposition.
  3. LSP signaling succeeds with compatible reservation values and reported resource state.
  4. The target prefix has the planned preference while unrelated routes retain prior selection.

Explanation

Correct Answer

B:

The penultimate and egress forwarding entries match the intended label disposition. Validate the advertised label behavior and egress processing expectations. Penultimate-hop popping can remove the outer transport label before the final LSR.

Incorrect Answers

A:

The active label operation now uses the recovered egress next hop. It is useful for situations where after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the reported fault, though, is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

C:

LSP signaling succeeds with compatible reservation values and reported resource state. This addresses a situation in which an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; however, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

The target prefix has the planned preference while unrelated routes retain prior selection. The choice would be appropriate if a broad routing policy term changes preference for all imported prefixes instead of only the intended test network. Here, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

Question 760

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 190, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. What likely service impact does this condition create?

  1. Healthy MPLS transport is disrupted by a false fault diagnosis.
  2. Labeled packets are discarded at the affected core node.
  3. Customers experience a blackhole hidden by otherwise present route advertisements.
  4. Half the expected capacity is unavailable and link failover is fragile.

Explanation

Correct Answer

A:

Healthy MPLS transport is disrupted by a false fault diagnosis. Validate the advertised label behavior and egress processing expectations. Penultimate-hop popping can remove the outer transport label before the final LSR.

Incorrect Answers

B:

Labeled packets are discarded at the affected core node. It is useful for situations where an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing; the reported fault, though, is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

C:

Customers experience a blackhole hidden by otherwise present route advertisements. That relates to circumstances in which a service path references an LSP that is down, but its IP route remains visible in the route table. Here the problem is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

D:

Half the expected capacity is unavailable and link failover is fragile. This addresses a situation in which a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ; however, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.

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