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 65

Question 640

In a separate fictional JNCIS-SP lab review for Fairhaven Broadband 160, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge. What is the direct residual network risk if the fault remains unresolved?

  1. Traffic traverses unsuitable links and topology changes become disruptive.
  2. A redundant Layer 2 link becomes a forwarding loop and floods the provider network.
  3. Unnecessary physical changes introduce instability without fixing the actual topology constraint.
  4. The backbone link stays out of the routing topology or an unsafe bypass is introduced.

Explanation

Correct Answer

B:

A redundant Layer 2 link becomes a forwarding loop and floods the provider network. Configure supported loop protection where appropriate and test loss-of-BPDU behavior. Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs.

Incorrect Answers

A:

Traffic traverses unsuitable links and topology changes become disruptive. This relates to a case where a low-capacity access switch becomes STP root after a new bridge priority setting; the current situation is that a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge.

C:

Unnecessary physical changes introduce instability without fixing the actual topology constraint. That relates to circumstances in which a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. Here the problem is that a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge.

D:

The backbone link stays out of the routing topology or an unsafe bypass is introduced. This addresses a situation in which a provider IS-IS circuit stops forming neighbors after the authentication key is changed on only one end; however, a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge.

Question 641

At fictional Cedarwater Transit 161, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Which targeted remediation best fits the reported behavior?

  1. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions.
  2. Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches.
  3. Assign planned bridge priorities and verify root and alternate port roles.
  4. Apply the supported LDP and IGP synchronization design and verify staged activation.

Explanation

Correct Answer

A:

Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. RSTP can converge more quickly using its port-role handshake and state mechanisms. The alternate link takes the intended forwarding role within the accepted recovery target.

Incorrect Answers

B:

Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches. This relates to a case where two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior; the current situation is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

Assign planned bridge priorities and verify root and alternate port roles. It is useful for situations where a low-capacity access switch becomes STP root after a new bridge priority setting; the reported fault, though, is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

D:

Apply the supported LDP and IGP synchronization design and verify staged activation. That relates to circumstances in which a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Here the problem is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 642

At fictional Cedarwater Transit 161, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Why is this particular correction the best fit for the stated defect?

  1. RSTP can converge more quickly using its port-role handshake and state mechanisms.
  2. Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs.
  3. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports.
  4. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.

Explanation

Correct Answer

A:

RSTP can converge more quickly using its port-role handshake and state mechanisms. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. The alternate link takes the intended forwarding role within the accepted recovery target.

Incorrect Answers

B:

Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. This could help if a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge, but not when a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. This relates to a case where a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only; the current situation is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

D:

Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. It is useful for situations where monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; the reported fault, though, is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 643

At fictional Cedarwater Transit 161, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. What direct observation would prove the corrective action worked?

  1. The alternate link takes the intended forwarding role within the accepted recovery target.
  2. The affected switches show the same region digest and expected per-instance port roles.
  3. An injected test BPDU triggers the documented protection while legitimate access ports behave normally.
  4. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes.

Explanation

Correct Answer

A:

The alternate link takes the intended forwarding role within the accepted recovery target. RSTP can converge more quickly using its port-role handshake and state mechanisms. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions.

Incorrect Answers

B:

The affected switches show the same region digest and expected per-instance port roles. It is relevant if two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior, but the reported issue is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

An injected test BPDU triggers the documented protection while legitimate access ports behave normally. This could help if a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only, but not when a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

D:

The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. This relates to a case where an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; the current situation is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 644

At fictional Cedarwater Transit 161, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Which failure consequence follows most closely from ignoring this issue?

  1. Unnecessary physical changes introduce instability without fixing the actual topology constraint.
  2. Customer equipment captures the root role and disrupts forwarding.
  3. A premium customer service traverses a congested or disallowed link.
  4. Subscribers see extended connectivity interruptions after routine link changes.

Explanation

Correct Answer

D:

Subscribers see extended connectivity interruptions after routine link changes. RSTP can converge more quickly using its port-role handshake and state mechanisms. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions.

Incorrect Answers

A:

Unnecessary physical changes introduce instability without fixing the actual topology constraint. That could help when a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics; here, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

B:

Customer equipment captures the root role and disrupts forwarding. This is applicable when a customer-facing bridge advertises a superior root and takes over the provider STP topology; the present condition is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

A premium customer service traverses a congested or disallowed link. It is relevant if an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route, but the reported issue is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 645

In a separate fictional JNCIS-SP lab review for Riverstone Networks 162, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. What intervention most directly restores the intended routing or switching behavior?

  1. Configure supported loop protection where appropriate and test loss-of-BPDU behavior.
  2. Restore the documented protection features and run controlled BPDU and failover tests.
  3. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup.
  4. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions.

Explanation

Correct Answer

D:

Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. The alternate link takes the intended forwarding role within the accepted recovery target. RSTP can converge more quickly using its port-role handshake and state mechanisms.

Incorrect Answers

A:

Configure supported loop protection where appropriate and test loss-of-BPDU behavior. This could matter when a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge. In this case, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

B:

Restore the documented protection features and run controlled BPDU and failover tests. That could help when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards; here, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. This is applicable when an operator changes route preference to make a broader prefix override a healthy more-specific prefix; the present condition is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 646

In a separate fictional JNCIS-SP lab review for Riverstone Networks 162, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Which networking principle explains why the proposed correction is appropriate?

  1. VSTP maintains spanning-tree behavior separately for participating VLANs.
  2. RSTP edge-port behavior is intended for ports without downstream bridge participation.
  3. RSTP can converge more quickly using its port-role handshake and state mechanisms.
  4. IS-IS levels separate routing scope and require a deliberate interlevel reachability design.

Explanation

Correct Answer

C:

RSTP can converge more quickly using its port-role handshake and state mechanisms. The alternate link takes the intended forwarding role within the accepted recovery target. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions.

Incorrect Answers

A:

VSTP maintains spanning-tree behavior separately for participating VLANs. It addresses a different problem: One VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs. Here, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

B:

RSTP edge-port behavior is intended for ports without downstream bridge participation. This could matter when a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. In this case, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

D:

IS-IS levels separate routing scope and require a deliberate interlevel reachability design. This is applicable when an L1-only site lacks an approved route to reach destinations in the backbone after a level-transition change; the present condition is that a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 647

In a separate fictional JNCIS-SP lab review for Riverstone Networks 162, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Which validation result would confirm the design is now functioning?

  1. Protection triggers on test violations and normal subscriber frames still forward.
  2. The affected VLAN has the desired root and its forwarding path recovers.
  3. The inet6 route is active and a controlled IPv6 probe reaches the prefix.
  4. The alternate link takes the intended forwarding role within the accepted recovery target.

Explanation

Correct Answer

D:

The alternate link takes the intended forwarding role within the accepted recovery target. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. RSTP can converge more quickly using its port-role handshake and state mechanisms.

Incorrect Answers

A:

Protection triggers on test violations and normal subscriber frames still forward. That option concerns a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. The problem here is different: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

B:

The affected VLAN has the desired root and its forwarding path recovers. It addresses a different problem: One VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs. Here, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

The inet6 route is active and a controlled IPv6 probe reaches the prefix. This could matter when an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface. In this case, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 648

In a separate fictional JNCIS-SP lab review for Riverstone Networks 162, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. What likely service impact does this condition create?

  1. Customer equipment captures the root role and disrupts forwarding.
  2. Subscribers see extended connectivity interruptions after routine link changes.
  3. A redundant Layer 2 link becomes a forwarding loop and floods the provider network.
  4. Traffic unexpectedly overloads a low-capacity link.

Explanation

Correct Answer

B:

Subscribers see extended connectivity interruptions after routine link changes. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. RSTP can converge more quickly using its port-role handshake and state mechanisms.

Incorrect Answers

A:

Customer equipment captures the root role and disrupts forwarding. The choice would be appropriate if a customer-facing bridge advertises a superior root and takes over the provider STP topology. Here, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

C:

A redundant Layer 2 link becomes a forwarding loop and floods the provider network. It addresses a different problem: A blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge. Here, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

D:

Traffic unexpectedly overloads a low-capacity link. This could matter when an intended core link metric is truncated by a mismatched metric-style design and fails to shift paths as expected. In this case, a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior.

Question 649

At fictional Windmere Fiber 163, a regional service-provider network, during a two-site transit migration, operations observes: Two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior. Which configuration or operational correction most directly addresses this failure?

  1. Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches.
  2. Configure supported loop protection where appropriate and test loss-of-BPDU behavior.
  3. Remove inappropriate edge-port assumptions and verify RSTP role transitions.
  4. Inspect LSDB entries, SPF route selection, and forwarding next hops instead of relying on neighbor state alone.

Explanation

Correct Answer

A:

Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches. MSTP topology calculations depend on compatible region identity and instance membership. The affected switches show the same region digest and expected per-instance port roles.

Incorrect Answers

B:

Configure supported loop protection where appropriate and test loss-of-BPDU behavior. The choice would be appropriate if a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge. Here, two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior.

C:

Remove inappropriate edge-port assumptions and verify RSTP role transitions. That option concerns a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. The problem here is different: Two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior.

D:

Inspect LSDB entries, SPF route selection, and forwarding next hops instead of relying on neighbor state alone. It addresses a different problem: The IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. Here, two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior.

Question 650

At fictional Windmere Fiber 163, a regional service-provider network, during a two-site transit migration, operations observes: Two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior. Which Junos forwarding or control-plane rule applies to this case?

  1. Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation.
  2. Physical link-up does not imply permission to forward under spanning-tree loop prevention.
  3. MSTP topology calculations depend on compatible region identity and instance membership.
  4. A configured static route forwards only after Junos can resolve its forwarding next hop.

Explanation

Correct Answer

C:

MSTP topology calculations depend on compatible region identity and instance membership. Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches. The affected switches show the same region digest and expected per-instance port roles.

Incorrect Answers

A:

Spanning-tree security should preserve legitimate forwarding while resisting topology manipulation. That relates to circumstances in which a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards. Here the problem is that two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior.

B:

Physical link-up does not imply permission to forward under spanning-tree loop prevention. This addresses a situation in which a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics; however, two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior.

D:

A configured static route forwards only after Junos can resolve its forwarding next hop. That option concerns a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. The problem here is different: Two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior.

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