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 69

Question 680

In a separate fictional JNCIS-SP lab review for Orchard Link 170, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. What likely service impact does this condition create?

  1. A routine template update makes the provider bridge vulnerable to a customer-induced loop.
  2. Traffic traverses unsuitable links and topology changes become disruptive.
  3. Customer equipment captures the root role and disrupts forwarding.
  4. MPLS traffic cannot use the planned engineered transport path.

Explanation

Correct Answer

A:

A routine template update makes the provider bridge vulnerable to a customer-induced loop. Restore the documented protection features and run controlled BPDU and failover tests. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation.

Incorrect Answers

B:

Traffic traverses unsuitable links and topology changes become disruptive. This is applicable when a low-capacity access switch becomes STP root after a new bridge priority setting; the present condition is that a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.

C:

Customer equipment captures the root role and disrupts forwarding. 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 a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.

D:

MPLS traffic cannot use the planned engineered transport path. This could help if an RSVP LSP stays down but engineers only examine the ingress router's IP default route, but not when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards.

Question 681

At fictional Oakshore Peering 171, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Which configuration or operational correction most directly addresses this failure?

  1. Perform controlled LSP validation and only then switch the authorized service resolution.
  2. Identify the ingress, transit, and egress LSR roles before modifying label rules.
  3. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.
  4. Correct the static next hop to a reachable transit address and confirm the selected route can resolve.

Explanation

Correct Answer

C:

Inspect label stack, bottom-of-stack indicator, and the expected transport operation. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Packet capture and forwarding state show the intended outgoing transport label.

Incorrect Answers

A:

Perform controlled LSP validation and only then switch the authorized service resolution. This could matter when a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. In this case, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

B:

Identify the ingress, transit, and egress LSR roles before modifying label rules. That could help when a network test expects the ingress PE to swap a label that it should actually impose; here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

Correct the static next hop to a reachable transit address and confirm the selected route can resolve. It is relevant if a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface, but the reported issue is that operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 682

At fictional Oakshore Peering 171, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Which Junos forwarding or control-plane rule applies to this case?

  1. LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths.
  2. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.
  3. MPLS TTL handling can affect the hop visibility of path diagnostics.
  4. IS-IS elects a designated intermediate system on broadcast networks to manage pseudonode representation.

Explanation

Correct Answer

B:

MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Inspect label stack, bottom-of-stack indicator, and the expected transport operation. Packet capture and forwarding state show the intended outgoing transport label.

Incorrect Answers

A:

LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths. It addresses a different problem: A tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

C:

MPLS TTL handling can affect the hop visibility of path diagnostics. 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, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

IS-IS elects a designated intermediate system on broadcast networks to manage pseudonode representation. This is applicable when operators see two possible LAN-designated routers and assume the wrong one leads routing for the shared segment; the present condition is that operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 683

At fictional Oakshore Peering 171, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. What operational evidence best establishes successful remediation?

  1. Packet capture and forwarding state show the intended outgoing transport label.
  2. Packet observations match the intended push, swap, and disposition stages.
  3. The target prefix SID resolves to the planned node and the corresponding SR LSP is active.
  4. Relevant LSAs are refreshed consistently and the route remains active across the observation period.

Explanation

Correct Answer

A:

Packet capture and forwarding state show the intended outgoing transport label. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.

Incorrect Answers

B:

Packet observations match the intended push, swap, and disposition stages. It addresses a different problem: A network test expects the ingress PE to swap a label that it should actually impose. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

C:

The target prefix SID resolves to the planned node and the corresponding SR LSP is active. 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, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

Relevant LSAs are refreshed consistently and the route remains active across the observation period. That could help when an OSPF route vanishes intermittently because a neighbor cannot refresh topology information after repeated link resets; here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 684

At fictional Oakshore Peering 171, a regional service-provider network, during a planned PE-to-core handoff, operations observes: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Which operational harm would persist without the intended correction?

  1. A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer.
  2. A planned maintenance window causes an avoidable customer outage.
  3. A premium customer service traverses a congested or disallowed link.
  4. No adjacency forms, so link-state routes cannot traverse that link.

Explanation

Correct Answer

A:

A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.

Incorrect Answers

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: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

C:

A premium customer service traverses a congested or disallowed link. It addresses a different problem: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

No adjacency forms, so link-state routes cannot traverse that link. This could matter when an IS-IS neighbor remains down after an interface template disables its hello transmission. In this case, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 685

In a separate fictional JNCIS-SP lab review for Brookridge Metro 172, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. What should the Junos specialist change first to resolve this specific fault?

  1. Apply the supported LDP and IGP synchronization design and verify staged activation.
  2. Correct the SID assignment and confirm the intended segment path resolves to that node.
  3. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.
  4. Run a controlled member failure test and verify surviving-link service forwarding.

Explanation

Correct Answer

C:

Inspect label stack, bottom-of-stack indicator, and the expected transport operation. Packet capture and forwarding state show the intended outgoing transport label. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.

Incorrect Answers

A:

Apply the supported LDP and IGP synchronization design and verify staged activation. This addresses a situation in which a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage; however, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

B:

Correct the SID assignment and confirm the intended segment path resolves to that node. The choice would be appropriate if a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

Run a controlled member failure test and verify surviving-link service forwarding. It addresses a different problem: A provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 686

In a separate fictional JNCIS-SP lab review for Brookridge Metro 172, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. What technical principle underlies the right remedy?

  1. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.
  2. MPLS transit forwarding depends on installed label operations at each participating node.
  3. MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it.
  4. An established BGP session does not by itself establish which received path will be preferred.

Explanation

Correct Answer

A:

MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Packet capture and forwarding state show the intended outgoing transport label. Inspect label stack, bottom-of-stack indicator, and the expected transport operation.

Incorrect Answers

B:

MPLS transit forwarding depends on installed label operations at each participating node. This addresses a situation in which an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing; however, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

C:

MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it. The choice would be appropriate if a network test expects the ingress PE to swap a label that it should actually impose. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

An established BGP session does not by itself establish which received path will be preferred. That option concerns a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. The problem here is different: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 687

In a separate fictional JNCIS-SP lab review for Brookridge Metro 172, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Which acceptance finding demonstrates the affected service has recovered?

  1. The failing RSVP hop is identified and the LSP reports Up after correction.
  2. The active label operation now uses the recovered egress next hop.
  3. Packet capture and forwarding state show the intended outgoing transport label.
  4. Peer SPF paths avoid the router while overloaded and normal paths return after it is cleared.

Explanation

Correct Answer

C:

Packet capture and forwarding state show the intended outgoing transport label. Inspect label stack, bottom-of-stack indicator, and the expected transport operation. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.

Incorrect Answers

A:

The failing RSVP hop is identified and the LSP reports Up after correction. It is useful for situations where an RSVP LSP stays down but engineers only examine the ingress router's IP default route; the reported fault, though, is that operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

B:

The active label operation now uses the recovered egress next hop. That relates to circumstances in which after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Here the problem is that operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

Peer SPF paths avoid the router while overloaded and normal paths return after it is cleared. The choice would be appropriate if a newly rebooted core router attracts transit traffic while its forwarding state is still being restored. Here, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 688

In a separate fictional JNCIS-SP lab review for Brookridge Metro 172, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: Operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. What is the direct residual network risk if the fault remains unresolved?

  1. A sensitive workload unexpectedly traverses a different core link.
  2. A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer.
  3. A partial label-distribution failure persists without an alert.
  4. IPv6 Internet service fails while IPv4 peering looks healthy.

Explanation

Correct Answer

B:

A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer. Inspect label stack, bottom-of-stack indicator, and the expected transport operation. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.

Incorrect Answers

A:

A sensitive workload unexpectedly traverses a different core link. This relates to a case where a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path; the current situation is that operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

C:

A partial label-distribution failure persists without an alert. That relates to circumstances in which monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Here the problem is that operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

D:

IPv6 Internet service fails while IPv4 peering looks healthy. This addresses a situation in which an established BGP peer exchanges IPv4 but rejects all authorized IPv6 prefixes due to a misplaced family-specific filter; however, operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header.

Question 689

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 targeted remediation best fits the reported behavior?

  1. Use an appropriate segment list or routing design matching the required steering behavior.
  2. Check LDP transport address reachability and session parameters through the IGP.
  3. Verify renewed label forwarding entries after the IGP path change and correct stale state.
  4. Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery.

Explanation

Correct Answer

B:

Check LDP transport address reachability and session parameters through the IGP. 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.

Incorrect Answers

A:

Use an appropriate segment list or routing design matching the required steering behavior. This could help 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 not when two core routers cannot form an LDP session even though they discover one another on the connected link.

C:

Verify renewed label forwarding entries after the IGP path change and correct stale state. 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 two core routers cannot form an LDP session even though they discover one another on the connected link.

D:

Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery. That relates to circumstances in which a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree. Here the problem is that two core routers cannot form an LDP session even though they discover one another on the connected link.

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.

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