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 82

Question 810

At fictional Crestland Networks 203, a regional service-provider network, during a two-site transit migration, operations observes: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Which Junos forwarding or control-plane rule applies to this case?

  1. MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding.
  2. MPLS label forwarding must follow the current resolved transport topology.
  3. IS-IS levels separate routing scope and require a deliberate interlevel reachability design.
  4. Protocol adjacency health does not prove every required MPLS forwarding entry exists.

Explanation

Correct Answer

D:

Protocol adjacency health does not prove every required MPLS forwarding entry exists. Add validation of both FEC label mappings and active MPLS forwarding entries. The target loopback FEC has a valid binding and corresponding programmed label action.

Incorrect Answers

A:

MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding. It is relevant if a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage, but the reported issue is that monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

B:

MPLS label forwarding must follow the current resolved transport topology. This could help if after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device, but not when monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

C:

IS-IS levels separate routing scope and require a deliberate interlevel reachability design. This relates to a case where an L1-only site lacks an approved route to reach destinations in the backbone after a level-transition change; the current situation is that monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 811

At fictional Crestland Networks 203, a regional service-provider network, during a two-site transit migration, operations observes: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. What operational evidence best establishes successful remediation?

  1. The active label operation now uses the recovered egress next hop.
  2. The selected service resolves over the intended RSVP LSP and follows engineered hops.
  3. The contributor is visible and the generated default returns with the expected forwarding next hop.
  4. The target loopback FEC has a valid binding and corresponding programmed label action.

Explanation

Correct Answer

D:

The target loopback FEC has a valid binding and corresponding programmed label action. Protocol adjacency health does not prove every required MPLS forwarding entry exists. Add validation of both FEC label mappings and active MPLS forwarding entries.

Incorrect Answers

A:

The active label operation now uses the recovered egress next hop. This is applicable when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the present condition is that monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

B:

The selected service resolves over the intended RSVP LSP and follows engineered hops. It is relevant if a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change, but the reported issue is that monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

C:

The contributor is visible and the generated default returns with the expected forwarding next hop. This could help if a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route, but not when monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 812

At fictional Crestland Networks 203, a regional service-provider network, during a two-site transit migration, operations observes: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Which operational harm would persist without the intended correction?

  1. The engineered service remains unavailable or overcommits transit capacity.
  2. A partial label-distribution failure persists without an alert.
  3. MPLS traffic remains broken despite restored IGP neighbors.
  4. Services remain blackholed despite a received BGP update.

Explanation

Correct Answer

B:

A partial label-distribution failure persists without an alert. Protocol adjacency health does not prove every required MPLS forwarding entry exists. Add validation of both FEC label mappings and active MPLS forwarding entries.

Incorrect Answers

A:

The engineered service remains unavailable or overcommits transit capacity. That could help when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; here, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

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 monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

D:

Services remain blackholed despite a received BGP update. This could help if an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability, but not when monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 813

In a separate fictional JNCIS-SP lab review for Silverlake Routing 204, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. What should the Junos specialist change first to resolve this specific fault?

  1. Correct the SID assignment and confirm the intended segment path resolves to that node.
  2. Recalculate the supported reservation and link bandwidth design before retrying.
  3. Add validation of both FEC label mappings and active MPLS forwarding entries.
  4. Use root protection on designated protected links and verify superior BPDU handling.

Explanation

Correct Answer

C:

Add validation of both FEC label mappings and active MPLS forwarding entries. The target loopback FEC has a valid binding and corresponding programmed label action. Protocol adjacency health does not prove every required MPLS forwarding entry exists.

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, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

B:

Recalculate the supported reservation and link bandwidth design before retrying. That could help when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; here, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

D:

Use root protection on designated protected links and verify superior BPDU handling. It is relevant if a customer-facing bridge advertises a superior root and takes over the provider STP topology, but the reported issue is that monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 814

In a separate fictional JNCIS-SP lab review for Silverlake Routing 204, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. What technical principle underlies the right remedy?

  1. LDP discovery and the TCP-based LDP session depend on usable transport reachability.
  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. Link-local IPv6 addresses are scoped to a link and require an appropriate interface context.

Explanation

Correct Answer

C:

Protocol adjacency health does not prove every required MPLS forwarding entry exists. The target loopback FEC has a valid binding and corresponding programmed label action. Add validation of both FEC label mappings and active MPLS forwarding entries.

Incorrect Answers

A:

LDP discovery and the TCP-based LDP session depend on usable transport reachability. It addresses a different problem: Two core routers cannot form an LDP session even though they discover one another on the connected link. Here, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

B:

MPLS traffic can fail if shortest-path selection moves onto a link without ready label forwarding. This could matter when a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. In this case, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

D:

Link-local IPv6 addresses are scoped to a link and require an appropriate interface context. This is applicable when an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; the present condition is that monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 815

In a separate fictional JNCIS-SP lab review for Silverlake Routing 204, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Which acceptance finding demonstrates the affected service has recovered?

  1. A controlled packet trace follows the intended segment program under the chosen IGP topology.
  2. The target prefix SID resolves to the planned node and the corresponding SR LSP is active.
  3. The target loopback FEC has a valid binding and corresponding programmed label action.
  4. A correctly sized customer frame traverses the entire provider handoff without drops.

Explanation

Correct Answer

C:

The target loopback FEC has a valid binding and corresponding programmed label action. Add validation of both FEC label mappings and active MPLS forwarding entries. Protocol adjacency health does not prove every required MPLS forwarding entry exists.

Incorrect Answers

A:

A controlled packet trace follows the intended segment program under the chosen IGP topology. 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: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

B:

The target prefix SID resolves to the planned node and the corresponding SR LSP is active. 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, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

D:

A correctly sized customer frame traverses the entire provider handoff without drops. That could help when a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU; here, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 816

In a separate fictional JNCIS-SP lab review for Silverlake Routing 204, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. What is the direct residual network risk if the fault remains unresolved?

  1. Healthy MPLS transport is disrupted by a false fault diagnosis.
  2. An SID collision or wrong label steers packets onto an unintended destination.
  3. A partial label-distribution failure persists without an alert.
  4. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes.

Explanation

Correct Answer

C:

A partial label-distribution failure persists without an alert. Add validation of both FEC label mappings and active MPLS forwarding entries. Protocol adjacency health does not prove every required MPLS forwarding entry exists.

Incorrect Answers

A:

Healthy MPLS transport is disrupted by a false fault diagnosis. 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, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

B:

An SID collision or wrong label steers packets onto an unintended destination. That option concerns a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. The problem here is different: Monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

D:

Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. This could matter when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. In this case, monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback.

Question 817

At fictional Seabrook Metro 205, a regional service-provider network, during a preproduction design validation, operations observes: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Which targeted remediation best fits the reported behavior?

  1. Recalculate the supported reservation and link bandwidth design before retrying.
  2. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.
  3. Perform controlled LSP validation and only then switch the authorized service resolution.
  4. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.

Explanation

Correct Answer

C:

Perform controlled LSP validation and only then switch the authorized service resolution. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. An MPLS-aware trace and service probe pass before and after the selected cutover.

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, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

B:

Review RSVP path constraints and explicit-route settings, then reestablish the LSP. The choice would be appropriate if an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Here, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

D:

Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. It addresses a different problem: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Here, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 818

At fictional Seabrook Metro 205, a regional service-provider network, during a preproduction design validation, operations observes: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. 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. RSVP-TE can establish signaled LSPs subject to configured path constraints.
  3. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits.
  4. Virtual switching can provide separate Layer 2 forwarding contexts for tenants.

Explanation

Correct Answer

C:

MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. Perform controlled LSP validation and only then switch the authorized service resolution. An MPLS-aware trace and service probe pass before and after the selected cutover.

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 MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

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, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

D:

Virtual switching can provide separate Layer 2 forwarding contexts for tenants. That option concerns two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. The problem here is different: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 819

At fictional Seabrook Metro 205, a regional service-provider network, during a preproduction design validation, operations observes: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. What direct observation would prove the corrective action worked?

  1. LSP signaling succeeds with compatible reservation values and reported resource state.
  2. A controlled packet trace follows the intended segment program under the chosen IGP topology.
  3. The service route is visible on remote devices while unrelated prefixes remain suppressed.
  4. An MPLS-aware trace and service probe pass before and after the selected cutover.

Explanation

Correct Answer

D:

An MPLS-aware trace and service probe pass before and after the selected cutover. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. Perform controlled LSP validation and only then switch the authorized service resolution.

Incorrect Answers

A:

LSP signaling succeeds with compatible reservation values and reported resource state. It is useful for situations where an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; the reported fault, though, is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

B:

A controlled packet trace follows the intended segment program under the chosen IGP topology. That relates to circumstances in which a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path. Here the problem is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

C:

The service route is visible on remote devices while unrelated prefixes remain suppressed. This addresses a situation in which a customer service route never reaches another IS-IS area because the required export policy omits it; however, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 820

At fictional Seabrook Metro 205, a regional service-provider network, during a preproduction design validation, operations observes: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Which failure consequence follows most closely from ignoring this issue?

  1. A planned maintenance window causes an avoidable customer outage.
  2. Labeled packets are discarded at the affected core node.
  3. An incorrect topology conclusion prompts needless routing changes.
  4. Traffic engineering intent fails despite the community being visible.

Explanation

Correct Answer

A:

A planned maintenance window causes an avoidable customer outage. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. Perform controlled LSP validation and only then switch the authorized service resolution.

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 a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

C:

An incorrect topology conclusion prompts needless routing changes. That relates to circumstances in which traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. Here the problem is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

D:

Traffic engineering intent fails despite the community being visible. This addresses a situation in which an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning; however, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

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