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 61

Question 600

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 150, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. What likely service impact does this condition create?

  1. Customer broadcasts and potentially sensitive frames cross service boundaries.
  2. Traffic follows an obsolete service path or reaches the wrong customer site.
  3. Repeated flooding and customer frame loss continue despite healthy routes.
  4. Remote sites lose the service route or excessive routes leak into the IGP.

Explanation

Correct Answer

C:

Repeated flooding and customer frame loss continue despite healthy routes. Investigate Layer 2 topology, bridge membership and possible loop before route-policy changes. Unexpected MAC movement often points to changing Layer 2 forwarding topology.

Incorrect Answers

A:

Customer broadcasts and potentially sensitive frames cross service boundaries. The choice would be appropriate if two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Here, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

B:

Traffic follows an obsolete service path or reaches the wrong customer site. That option concerns a MAC is learned on an unexpected aggregation interface following a customer circuit move. The problem here is different: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

D:

Remote sites lose the service route or excessive routes leak into the IGP. This could matter when a static service prefix is missing from OSPF because the export policy was attached but does not match it. In this case, a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables.

Question 601

At fictional Hillside Transit 151, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A low-capacity access switch becomes STP root after a new bridge priority setting. Which configuration or operational correction most directly addresses this failure?

  1. Inspect spanning-tree port role, state, and received BPDU information before changing hardware.
  2. Configure supported loop protection where appropriate and test loss-of-BPDU behavior.
  3. Assign planned bridge priorities and verify root and alternate port roles.
  4. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup.

Explanation

Correct Answer

C:

Assign planned bridge priorities and verify root and alternate port roles. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. The intended distribution bridge is root and access ports show expected roles.

Incorrect Answers

A:

Inspect spanning-tree port role, state, and received BPDU information before changing hardware. 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, a low-capacity access switch becomes STP root after a new bridge priority setting.

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, a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. It addresses a different problem: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. Here, a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 602

At fictional Hillside Transit 151, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A low-capacity access switch becomes STP root after a new bridge priority setting. Which Junos forwarding or control-plane rule applies to this case?

  1. Physical link-up does not imply permission to forward under spanning-tree loop prevention.
  2. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports.
  3. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology.
  4. GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint.

Explanation

Correct Answer

C:

Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. Assign planned bridge priorities and verify root and alternate port roles. The intended distribution bridge is root and access ports show expected roles.

Incorrect Answers

A:

Physical link-up does not imply permission to forward under spanning-tree loop prevention. 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 low-capacity access switch becomes STP root after a new bridge priority setting.

B:

BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. This addresses a situation in which a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only; however, a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. That option concerns a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. The problem here is different: A low-capacity access switch becomes STP root after a new bridge priority setting.

Question 603

At fictional Hillside Transit 151, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A low-capacity access switch becomes STP root after a new bridge priority setting. What operational evidence best establishes successful remediation?

  1. The interswitch link uses normal RSTP role and state handling during topology tests.
  2. The intended distribution bridge is root and access ports show expected roles.
  3. The suspect port remains in the protected state until valid BPDU information returns.
  4. The suspect path is explained and only eligible loop-free routes are selected.

Explanation

Correct Answer

B:

The intended distribution bridge is root and access ports show expected roles. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. Assign planned bridge priorities and verify root and alternate port roles.

Incorrect Answers

A:

The interswitch link uses normal RSTP role and state handling during topology tests. It is useful for situations where a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior; the reported fault, though, is that a low-capacity access switch becomes STP root after a new bridge priority setting.

C:

The suspect port remains in the protected state until valid BPDU information returns. This addresses a situation in which a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; however, a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

The suspect path is explained and only eligible loop-free routes are selected. The choice would be appropriate if an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Here, a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 604

At fictional Hillside Transit 151, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A low-capacity access switch becomes STP root after a new bridge priority setting. Which operational harm would persist without the intended correction?

  1. A redundant Layer 2 link becomes a forwarding loop and floods the provider network.
  2. Customer switching devices can influence provider spanning-tree topology.
  3. Customers can inject unapproved Layer 2 traffic into the provider bridge.
  4. Traffic traverses unsuitable links and topology changes become disruptive.

Explanation

Correct Answer

D:

Traffic traverses unsuitable links and topology changes become disruptive. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. Assign planned bridge priorities and verify root and alternate port roles.

Incorrect Answers

A:

A redundant Layer 2 link becomes a forwarding loop and floods the provider network. This relates to a case where a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the current situation is that a low-capacity access switch becomes STP root after a new bridge priority setting.

B:

Customer switching devices can influence provider spanning-tree topology. It is useful for situations where a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only; the reported fault, though, is that a low-capacity access switch becomes STP root after a new bridge priority setting.

C:

Customers can inject unapproved Layer 2 traffic into the provider bridge. That relates to circumstances in which an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Here the problem is that a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 605

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 152, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A low-capacity access switch becomes STP root after a new bridge priority setting. What should the Junos specialist change first to resolve this specific fault?

  1. Assign planned bridge priorities and verify root and alternate port roles.
  2. Inspect spanning-tree port role, state, and received BPDU information before changing hardware.
  3. Configure supported loop protection where appropriate and test loss-of-BPDU behavior.
  4. Fix the OSPF export policy's precise match and validate external route origination.

Explanation

Correct Answer

A:

Assign planned bridge priorities and verify root and alternate port roles. The intended distribution bridge is root and access ports show expected roles. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology.

Incorrect Answers

B:

Inspect spanning-tree port role, state, and received BPDU information before changing hardware. This relates to a case where a link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics; the current situation is that a low-capacity access switch becomes STP root after a new bridge priority setting.

C:

Configure supported loop protection where appropriate and test loss-of-BPDU behavior. It is useful for situations where a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the reported fault, though, is that a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

Fix the OSPF export policy's precise match and validate external route origination. That relates to circumstances in which a static service prefix is missing from OSPF because the export policy was attached but does not match it. Here the problem is that a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 606

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 152, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A low-capacity access switch becomes STP root after a new bridge priority setting. What technical principle underlies the right remedy?

  1. VSTP maintains spanning-tree behavior separately for participating VLANs.
  2. RSTP can converge more quickly using its port-role handshake and state mechanisms.
  3. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology.
  4. NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover.

Explanation

Correct Answer

C:

Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology. The intended distribution bridge is root and access ports show expected roles. Assign planned bridge priorities and verify root and alternate port roles.

Incorrect Answers

A:

VSTP maintains spanning-tree behavior separately for participating VLANs. It is relevant if one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs, but the reported issue is that a low-capacity access switch becomes STP root after a new bridge priority setting.

B:

RSTP can converge more quickly using its port-role handshake and state mechanisms. This could help if a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior, but not when a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover. It is useful for situations where a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets; the reported fault, though, is that a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 607

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 152, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A low-capacity access switch becomes STP root after a new bridge priority setting. Which acceptance finding demonstrates the affected service has recovered?

  1. The affected VLAN has the desired root and its forwarding path recovers.
  2. The alternate link takes the intended forwarding role within the accepted recovery target.
  3. The intended distribution bridge is root and access ports show expected roles.
  4. The selected service resolves over the intended RSVP LSP and follows engineered hops.

Explanation

Correct Answer

C:

The intended distribution bridge is root and access ports show expected roles. Assign planned bridge priorities and verify root and alternate port roles. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology.

Incorrect Answers

A:

The affected VLAN has the desired root and its forwarding path recovers. This is applicable when one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs; the present condition is that a low-capacity access switch becomes STP root after a new bridge priority setting.

B:

The alternate link takes the intended forwarding role within the accepted recovery target. It is relevant if a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior, but the reported issue is that a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

The selected service resolves over the intended RSVP LSP and follows engineered hops. This relates to a case where a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change; the current situation is that a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 608

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 152, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A low-capacity access switch becomes STP root after a new bridge priority setting. What is the direct residual network risk if the fault remains unresolved?

  1. A redundant Layer 2 link becomes a forwarding loop and floods the provider network.
  2. Traffic traverses unsuitable links and topology changes become disruptive.
  3. An unnoticed bridging loop can trigger widespread broadcast storms.
  4. Healthy MPLS transport is disrupted by a false fault diagnosis.

Explanation

Correct Answer

B:

Traffic traverses unsuitable links and topology changes become disruptive. Assign planned bridge priorities and verify root and alternate port roles. Spanning tree selects a root bridge to build a loop-free Layer 2 forwarding topology.

Incorrect Answers

A:

A redundant Layer 2 link becomes a forwarding loop and floods the provider network. That could help when a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; here, a low-capacity access switch becomes STP root after a new bridge priority setting.

C:

An unnoticed bridging loop can trigger widespread broadcast storms. It is relevant if a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior, but the reported issue is that a low-capacity access switch becomes STP root after a new bridge priority setting.

D:

Healthy MPLS transport is disrupted by a false fault diagnosis. This could help if an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP, but not when a low-capacity access switch becomes STP root after a new bridge priority setting.

Question 609

At fictional Crestland Networks 153, a regional service-provider network, during a two-site transit migration, operations observes: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Which targeted remediation best fits the reported behavior?

  1. Inspect the relevant VSTP instance and set its intended per-VLAN root and port roles.
  2. Remove inappropriate edge-port assumptions and verify RSTP role transitions.
  3. Restore the documented protection features and run controlled BPDU and failover tests.
  4. Check ABR area participation and intended interarea advertisement and restore correct connectivity.

Explanation

Correct Answer

B:

Remove inappropriate edge-port assumptions and verify RSTP role transitions. RSTP edge-port behavior is intended for ports without downstream bridge participation. The interswitch link uses normal RSTP role and state handling during topology tests.

Incorrect Answers

A:

Inspect the relevant VSTP instance and set its intended per-VLAN root and port roles. This could matter when one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs. In this case, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.

C:

Restore the documented protection features and run controlled BPDU and failover tests. This is applicable when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards; the present condition is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.

D:

Check ABR area participation and intended interarea advertisement and restore correct connectivity. It is relevant if a site advertises internal prefixes inside one area, but a remote OSPF area cannot learn them because the area border configuration is incomplete, but the reported issue is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.

Question 610

At fictional Crestland Networks 153, a regional service-provider network, during a two-site transit migration, operations observes: A switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Why is this particular correction the best fit for the stated defect?

  1. BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports.
  2. Root protection maintains root placement by preventing an untrusted port from becoming an upstream root path.
  3. RSTP edge-port behavior is intended for ports without downstream bridge participation.
  4. Filter-based forwarding selects a routing lookup context based on packet classification.

Explanation

Correct Answer

C:

RSTP edge-port behavior is intended for ports without downstream bridge participation. Remove inappropriate edge-port assumptions and verify RSTP role transitions. The interswitch link uses normal RSTP role and state handling during topology tests.

Incorrect Answers

A:

BPDU protection prevents inappropriate participation in spanning-tree control at protected edge ports. It addresses a different problem: A subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Here, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.

B:

Root protection maintains root placement by preventing an untrusted port from becoming an upstream root path. This could matter when a customer-facing bridge advertises a superior root and takes over the provider STP topology. In this case, a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.

D:

Filter-based forwarding selects a routing lookup context based on packet classification. This is applicable when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; the present condition is that a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior.

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