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 83

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.

Question 821

In a separate fictional JNCIS-SP lab review for Northpoint Access 206, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. What intervention most directly restores the intended routing or switching 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. Repair IPv4 underlay reachability to the tunnel endpoint before modifying IPv6 customer prefixes.

Explanation

Correct Answer

A:

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. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits.

Incorrect Answers

B:

Recalculate the supported reservation and link bandwidth design before retrying. This relates to a case where an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; the current situation is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

C:

Use an appropriate segment list or routing design matching the required steering behavior. It is useful for situations 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 reported fault, though, is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

D:

Repair IPv4 underlay reachability to the tunnel endpoint before modifying IPv6 customer prefixes. That relates to circumstances in which an IPv6 service is carried through an IPv4 underlay, but the tunnel endpoint's IPv4 route has disappeared. Here the problem is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 822

In a separate fictional JNCIS-SP lab review for Northpoint Access 206, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Which networking principle explains why the proposed correction is appropriate?

  1. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits.
  2. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination.
  3. A route's presence is insufficient if its selected MPLS transport next hop is unusable.
  4. IPv4 and IPv6 route lookups use separate address-family tables.

Explanation

Correct Answer

A:

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. Perform controlled LSP validation and only then switch the authorized service resolution.

Incorrect Answers

B:

MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. This could help if operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header, but not when a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

C:

A route's presence is insufficient if its selected MPLS transport next hop is unusable. This relates to a case where a service path references an LSP that is down, but its IP route remains visible in the route table; the current situation is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

D:

IPv4 and IPv6 route lookups use separate address-family tables. 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 a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 823

In a separate fictional JNCIS-SP lab review for Northpoint Access 206, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Which validation result would confirm the design is now functioning?

  1. The LDP neighbor is operational and exchanges label mappings for expected FECs.
  2. Packet observations match the intended push, swap, and disposition stages.
  3. A controlled path failure produces the designed BFD event and route withdrawal within target bounds.
  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. 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.

Incorrect Answers

A:

The LDP neighbor is operational and exchanges label mappings for expected FECs. This is applicable when two core routers cannot form an LDP session even though they discover one another on the connected link; the present condition is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

B:

Packet observations match the intended push, swap, and disposition stages. It is relevant if a network test expects the ingress PE to swap a label that it should actually impose, but the reported issue is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

C:

A controlled path failure produces the designed BFD event and route withdrawal within target bounds. This could help if a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow, but not when a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 824

In a separate fictional JNCIS-SP lab review for Northpoint Access 206, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. What likely service impact does this condition create?

  1. Healthy MPLS transport is disrupted by a false fault diagnosis.
  2. An incorrect topology conclusion prompts needless routing changes.
  3. A planned maintenance window causes an avoidable customer outage.
  4. A false no-route diagnosis delays the actual IPv6 repair.

Explanation

Correct Answer

C:

A planned maintenance window causes an avoidable customer outage. 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.

Incorrect Answers

A:

Healthy MPLS transport is disrupted by a false fault diagnosis. That could help when an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP; here, a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

B:

An incorrect topology conclusion prompts needless routing changes. This is applicable when traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut; the present condition is that a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

D:

A false no-route diagnosis delays the actual IPv6 repair. This could help if a support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised, but not when a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested.

Question 825

At fictional Linden Point 207, a regional service-provider network, during a core-routing acceptance test, operations observes: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. Which configuration or operational correction most directly addresses this failure?

  1. Associate the link-local next hop with the correct egress interface and validate neighbor resolution.
  2. Correct the IPv6 family and import policy scope, then check received and advertised inet6 routes.
  3. Perform controlled LSP validation and only then switch the authorized service resolution.
  4. Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables.

Explanation

Correct Answer

D:

Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. The inet6 route is active and a controlled IPv6 probe reaches the prefix.

Incorrect Answers

A:

Associate the link-local next hop with the correct egress interface and validate neighbor resolution. This could matter when an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design. In this case, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

B:

Correct the IPv6 family and import policy scope, then check received and advertised inet6 routes. That could help when an established BGP peer exchanges IPv4 but rejects all authorized IPv6 prefixes due to a misplaced family-specific filter; here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

C:

Perform controlled LSP validation and only then switch the authorized service resolution. 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 IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

Question 826

At fictional Linden Point 207, a regional service-provider network, during a core-routing acceptance test, operations observes: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. Which Junos forwarding or control-plane rule applies to this case?

  1. Link-local IPv6 addresses are scoped to a link and require an appropriate interface context.
  2. IPv4 and IPv6 route lookups use separate address-family tables.
  3. BGP address-family negotiation determines which network-layer reachability data can be exchanged.
  4. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family.

Explanation

Correct Answer

D:

IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables. The inet6 route is active and a controlled IPv6 probe reaches the prefix.

Incorrect Answers

A:

Link-local IPv6 addresses are scoped to a link and require an appropriate interface context. It addresses a different problem: An IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design. Here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

B:

IPv4 and IPv6 route lookups use separate address-family tables. This could matter when a support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised. In this case, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

C:

BGP address-family negotiation determines which network-layer reachability data can be exchanged. That could help when an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

Question 827

At fictional Linden Point 207, a regional service-provider network, during a core-routing acceptance test, operations observes: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. What operational evidence best establishes successful remediation?

  1. The inet6 route is active and a controlled IPv6 probe reaches the prefix.
  2. Remote routers learn intended IPv6 prefixes and forward IPv6 probes end to end.
  3. Both endpoint IPv4 routes and encapsulated IPv6 packet tests succeed.
  4. MAC entries stabilize on the intended interface after repairing the bridge path.

Explanation

Correct Answer

A:

The inet6 route is active and a controlled IPv6 probe reaches the prefix. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables.

Incorrect Answers

B:

Remote routers learn intended IPv6 prefixes and forward IPv6 probes end to end. It addresses a different problem: A core network runs IS-IS for IPv4 but has no IPv6 service reachability after dual-stack activation. Here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

C:

Both endpoint IPv4 routes and encapsulated IPv6 packet tests succeed. This could matter when an IPv6 service is carried through an IPv4 underlay, but the tunnel endpoint's IPv4 route has disappeared. In this case, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

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 IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

Question 828

At fictional Linden Point 207, a regional service-provider network, during a core-routing acceptance test, operations observes: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. Which operational harm would persist without the intended correction?

  1. IPv6 service fails across a still-configured but unusable tunnel.
  2. IPv6 customers lose service even when IPv4 routing remains healthy.
  3. A false no-route diagnosis delays the actual IPv6 repair.
  4. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable.

Explanation

Correct Answer

B:

IPv6 customers lose service even when IPv4 routing remains healthy. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables.

Incorrect Answers

A:

IPv6 service fails across a still-configured but unusable tunnel. 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 IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

C:

A false no-route diagnosis delays the actual IPv6 repair. It addresses a different problem: A support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised. Here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

D:

Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. This could matter when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. In this case, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

Question 829

In a separate fictional JNCIS-SP lab review for Harborview ISP 208, a carrier-edge and core routing team, following a monitored network change window, engineers find: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. What should the Junos specialist change first to resolve this specific fault?

  1. Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables.
  2. Enable the supported IS-IS IPv6 reachability and confirm advertisements and routes.
  3. Correct the IPv6 family and import policy scope, then check received and advertised inet6 routes.
  4. Configure the supported IPv6 IS-IS family and confirm prefix reachability at intended levels.

Explanation

Correct Answer

A:

Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables. The inet6 route is active and a controlled IPv6 probe reaches the prefix. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family.

Incorrect Answers

B:

Enable the supported IS-IS IPv6 reachability and confirm advertisements and routes. The choice would be appropriate if a core network runs IS-IS for IPv4 but has no IPv6 service reachability after dual-stack activation. Here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

C:

Correct the IPv6 family and import policy scope, then check received and advertised inet6 routes. That option concerns an established BGP peer exchanges IPv4 but rejects all authorized IPv6 prefixes due to a misplaced family-specific filter. The problem here is different: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

D:

Configure the supported IPv6 IS-IS family and confirm prefix reachability at intended levels. It addresses a different problem: An IPv6 service prefix is missing from an IS-IS network because the necessary topology and family capability were not enabled. Here, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

Question 830

In a separate fictional JNCIS-SP lab review for Harborview ISP 208, a carrier-edge and core routing team, following a monitored network change window, engineers find: An IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. What technical principle underlies the right remedy?

  1. IPv4 and IPv6 route lookups use separate address-family tables.
  2. Link-local IPv6 addresses are scoped to a link and require an appropriate interface context.
  3. Routing policy terms should match only their explicitly intended routes before altering route attributes.
  4. IPv6 forwarding requires a usable route and resolvable next hop in the correct address family.

Explanation

Correct Answer

D:

IPv6 forwarding requires a usable route and resolvable next hop in the correct address family. The inet6 route is active and a controlled IPv6 probe reaches the prefix. Correct IPv6 next-hop reachability and inspect the inet6 routing and forwarding tables.

Incorrect Answers

A:

IPv4 and IPv6 route lookups use separate address-family tables. That relates to circumstances in which a support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised. Here the problem is that an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

B:

Link-local IPv6 addresses are scoped to a link and require an appropriate interface context. This addresses a situation in which an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; however, an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

C:

Routing policy terms should match only their explicitly intended routes before altering route attributes. 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 IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface.

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