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 96

Question 950

In a separate fictional JNCIS-SP lab review for Windmere Fiber 238, a carrier-edge and core routing team, following a monitored network change window, engineers find: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Which networking principle explains why the proposed correction is appropriate?

  1. LAG availability depends on traffic being redirected to healthy active members after failure.
  2. A link aggregation group forwards correctly only over members meeting the operational bundle requirements.
  3. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change.
  4. An Ethernet port's VLAN tagging behavior must match the frames it receives.

Explanation

Correct Answer

C:

Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Configure and validate supported GRES readiness before an authorized controlled failover.

Incorrect Answers

A:

LAG availability depends on traffic being redirected to healthy active members after failure. That relates to circumstances in which a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Here the problem is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

B:

A link aggregation group forwards correctly only over members meeting the operational bundle requirements. 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, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

D:

An Ethernet port's VLAN tagging behavior must match the frames it receives. That option concerns a provider access port drops customer tagged frames because it was configured for untagged access mode. The problem here is different: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

Question 951

In a separate fictional JNCIS-SP lab review for Windmere Fiber 238, a carrier-edge and core routing team, following a monitored network change window, engineers find: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Which validation result would confirm the design is now functioning?

  1. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval.
  2. The backup becomes master during a controlled failure and hosts retain gateway reachability.
  3. The target loopback FEC has a valid binding and corresponding programmed label action.
  4. The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget.

Explanation

Correct Answer

D:

The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Configure and validate supported GRES readiness before an authorized controlled failover. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change.

Incorrect Answers

A:

Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. It is useful for situations where a provider assumes graceful restart will work during a routing process restart without considering neighbor support; the reported fault, though, is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

B:

The backup becomes master during a controlled failure and hosts retain gateway reachability. That relates to circumstances in which an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect. Here the problem is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

C:

The target loopback FEC has a valid binding and corresponding programmed label action. This addresses a situation in which monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback; however, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

Question 952

In a separate fictional JNCIS-SP lab review for Windmere Fiber 238, a carrier-edge and core routing team, following a monitored network change window, engineers find: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. What likely service impact does this condition create?

  1. A single gateway device fault disconnects all hosts on the VLAN.
  2. Maintenance triggers avoidable traffic loss and prolonged recovery.
  3. A nominally redundant network fails its practical customer continuity requirement.
  4. Unrelated subscribers change transit paths after a narrowly intended policy update.

Explanation

Correct Answer

B:

Maintenance triggers avoidable traffic loss and prolonged recovery. Configure and validate supported GRES readiness before an authorized controlled failover. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change.

Incorrect Answers

A:

A single gateway device fault disconnects all hosts on the VLAN. This relates to a case where an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; the current situation is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

C:

A nominally redundant network fails its practical customer continuity requirement. That relates to circumstances in which an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover. Here the problem is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

D:

Unrelated subscribers change transit paths after a narrowly intended policy update. This addresses a situation in which a broad routing policy term changes preference for all imported prefixes instead of only the intended test network; however, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.

Question 953

At fictional Meadowcrest Telecom 239, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. Which configuration or operational correction most directly addresses this failure?

  1. Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains.
  2. Correct VRRP group association, priority, and failover behavior on the gateway pair.
  3. Enable and verify supported nonstop active routing with required redundancy prerequisites.
  4. Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance.

Explanation

Correct Answer

C:

Enable and verify supported nonstop active routing with required redundancy prerequisites. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover.

Incorrect Answers

A:

Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains. This could help if a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets, but not when traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

B:

Correct VRRP group association, priority, and failover behavior on the gateway pair. This relates to a case where an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; the current situation is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

Create or correct the routed IRB interface and associate it with the intended VLAN and routing instance. That relates to circumstances in which customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Here the problem is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 954

At fictional Meadowcrest Telecom 239, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. Which Junos forwarding or control-plane rule applies to this case?

  1. BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers.
  2. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation.
  3. VRRP provides a shared virtual gateway address with an active router and standby candidates.
  4. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.

Explanation

Correct Answer

B:

NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. Enable and verify supported nonstop active routing with required redundancy prerequisites. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover.

Incorrect Answers

A:

BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers. It is relevant if a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow, but the reported issue is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

VRRP provides a shared virtual gateway address with an active router and standby candidates. This relates to a case where an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; the current situation is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. It is useful for situations where provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; the reported fault, though, is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 955

At fictional Meadowcrest Telecom 239, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. What operational evidence best establishes successful remediation?

  1. Both intended links join the bundle and sample traffic uses approved members.
  2. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover.
  3. During a staged failover, probes reach the customer service within the approved recovery threshold.
  4. The active label operation now uses the recovered egress next hop.

Explanation

Correct Answer

B:

BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. Enable and verify supported nonstop active routing with required redundancy prerequisites.

Incorrect Answers

A:

Both intended links join the bundle and sample traffic uses approved members. This is applicable when a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ; the present condition is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

During a staged failover, probes reach the customer service within the approved recovery threshold. This could help if an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover, but not when traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

The active label operation now uses the recovered egress next hop. This relates to a case where after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the current situation is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 956

At fictional Meadowcrest Telecom 239, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. Which operational harm would persist without the intended correction?

  1. A single gateway device fault disconnects all hosts on the VLAN.
  2. A supervisor failure forces routing protocol reconvergence and drops customer traffic.
  3. Subscribers suffer flooding or Layer 2 interruption after a supervisor failure.
  4. Unnecessary physical changes introduce instability without fixing the actual topology constraint.

Explanation

Correct Answer

B:

A supervisor failure forces routing protocol reconvergence and drops customer traffic. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. Enable and verify supported nonstop active routing with required redundancy prerequisites.

Incorrect Answers

A:

A single gateway device fault disconnects all hosts on the VLAN. That could help when an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

Subscribers suffer flooding or Layer 2 interruption after a supervisor failure. It is relevant if a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets, but the reported issue is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

Unnecessary physical changes introduce instability without fixing the actual topology constraint. This could help if a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics, but not when traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 957

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 240, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. What should the Junos specialist change first to resolve this specific fault?

  1. Configure and validate supported GRES readiness before an authorized controlled failover.
  2. Configure supported BFD monitoring with the neighbor protocol and validate failure detection behavior.
  3. Enable and verify supported nonstop active routing with required redundancy prerequisites.
  4. Perform controlled LSP validation and only then switch the authorized service resolution.

Explanation

Correct Answer

C:

Enable and verify supported nonstop active routing with required redundancy prerequisites. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation.

Incorrect Answers

A:

Configure and validate supported GRES readiness before an authorized controlled failover. This could matter when a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. In this case, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

B:

Configure supported BFD monitoring with the neighbor protocol and validate failure detection behavior. That could help when a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

Perform controlled LSP validation and only then switch the authorized service resolution. It is relevant if a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested, but the reported issue is that traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 958

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 240, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. What technical principle underlies the right remedy?

  1. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change.
  2. VRRP provides a shared virtual gateway address with an active router and standby candidates.
  3. Junos BGP exports only routes accepted by the applicable export policy.
  4. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation.

Explanation

Correct Answer

D:

NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. Enable and verify supported nonstop active routing with required redundancy prerequisites.

Incorrect Answers

A:

Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. It addresses a different problem: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

B:

VRRP provides a shared virtual gateway address with an active router and standby candidates. This could matter when an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect. In this case, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

Junos BGP exports only routes accepted by the applicable export policy. That could help when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 959

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 240, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. Which acceptance finding demonstrates the affected service has recovered?

  1. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover.
  2. Both intended links join the bundle and sample traffic uses approved members.
  3. MAC tables and customer bridge forwarding remain stable during controlled switchover.
  4. LSP signaling succeeds with compatible reservation values and reported resource state.

Explanation

Correct Answer

A:

BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. Enable and verify supported nonstop active routing with required redundancy prerequisites. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation.

Incorrect Answers

B:

Both intended links join the bundle and sample traffic uses approved members. It addresses a different problem: A bundled uplink has two configured members but only one is usable because the second member's operational parameters differ. Here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

MAC tables and customer bridge forwarding remain stable during controlled switchover. This could matter when a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. In this case, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

LSP signaling succeeds with compatible reservation values and reported resource state. That could help when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 960

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 240, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. What is the direct residual network risk if the fault remains unresolved?

  1. A nominally redundant network fails its practical customer continuity requirement.
  2. A supervisor failure forces routing protocol reconvergence and drops customer traffic.
  3. Half the expected capacity is unavailable and link failover is fragile.
  4. Control-plane churn follows repeated elections among unsuitable devices.

Explanation

Correct Answer

B:

A supervisor failure forces routing protocol reconvergence and drops customer traffic. Enable and verify supported nonstop active routing with required redundancy prerequisites. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation.

Incorrect Answers

A:

A nominally redundant network fails its practical customer continuity requirement. The choice would be appropriate if an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover. Here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

Half the expected capacity is unavailable and link failover is fragile. It addresses a different problem: A bundled uplink has two configured members but only one is usable because the second member's operational parameters differ. Here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

Control-plane churn follows repeated elections among unsuitable devices. This could matter when an unplanned access router becomes designated router after its interface receives an unexpectedly high priority. In this case, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

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