Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

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

Question 510

Before changing configuration at Harborline Transit, an engineer investigates: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. Which first diagnostic most directly tests the suspected cause?

  1. Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.
  2. Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
  3. Compare VSTP root and port states for the affected and unaffected VLANs on the same physical trunk.
  4. Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

Correct answer: A

Explanation of each choice

A.

Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior. RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

B.

This check may help with another root cause, for example: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. It does not test the first failed condition; start with: Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A team assumes a single spanning-tree state applies to all VLANs but Junos VSTP shows a blocked uplink for only one customer VLAN. Instead inspect: Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.

D.

The check diagnoses a different layer of service. Its source issue is: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. The relevant initial check is: Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.

Question 511

At Atlas Port Services, a service provider router shows this failure: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. What is the best targeted configuration or operations action?

  1. Align the MST region name, revision and VLAN-to-instance mapping across members, then verify inter-region boundaries where intentional.
  2. Enable appropriate BPDU protection on a confirmed edge/customer port and document recovery steps before returning it to service.
  3. Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state.
  4. Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

Correct answer: D

Explanation of each choice

A.

This action may apply to a different problem, for example: Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. It does not repair the stated failure boundary. The case-specific reason is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

B.

The other action is relevant when A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. The current case instead requires: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance. The distinction is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

C.

That would address a separate configuration fault: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. This stem identifies a different cause, corrected by: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

D.

Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance. The case-specific reason is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice. A direct acceptance test is: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

Question 512

A change auditor at Atlas Port Services must validate remediation of this finding: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. Which test outcome is the strongest acceptance evidence?

  1. A superior BPDU on a protected downstream role is prevented from taking over the root, or a lost-BPDU alternate path stays safely blocked per the chosen guard.
  2. The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
  3. The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.
  4. MST region members report compatible configuration identity and instance-specific root/port roles align with the VLAN design.

Correct answer: C

Explanation of each choice

A.

This would be valid for another situation: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. It does not establish that the failing boundary in this scenario works; verify: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

B.

The observation confirms a different component's behavior. Its source context is: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. In this case the success criterion is: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

C.

The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links. Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

D.

This would be valid for another situation: A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. It does not establish that the failing boundary in this scenario works; verify: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

Question 513

The operations training team at Atlas Port Services discusses this issue: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. Which technical explanation matches the intended correction?

  1. BPDU protection guards edge ports against unexpected bridge participation, unlike root protection which guards the root role in an existing spanning-tree topology.
  2. Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear.
  3. RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
  4. Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

Correct answer: D

Explanation of each choice

A.

That principle belongs to a different service stage: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. The directly relevant mechanism is: Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

B.

This explains a separate protocol behavior: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. In the current facts, the controlling mechanism is: Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

C.

The statement can be true when A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. But it does not explain the reported failure. Here: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

D.

Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths. The key distinction is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice. Accordingly the remedy is: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

Question 514

At Atlas Port Services, a service acceptance review considers the unresolved issue: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. Which operational exposure follows most directly?

  1. An unauthorized bridge can alter topology or create loops if BPDUs on an edge port are ignored.
  2. Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.
  3. An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.
  4. A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.

Correct answer: C

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. The described fault instead exposes: An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.

B.

It is a risk in another topology or protocol state: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. Here the most direct failure path is: An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.

C.

An unintended root can steer traffic across fragile customer links and cause avoidable topology churn. The direct mitigation is: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

D.

That consequence is more closely associated with another deficiency, such as: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. The described fault instead exposes: An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.

Question 515

Before changing configuration at Atlas Port Services, an engineer investigates: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. Which first diagnostic most directly tests the suspected cause?

  1. Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.
  2. Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface.
  3. Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.
  4. Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.

Correct answer: A

Explanation of each choice

A.

Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance. Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

B.

The check diagnoses a different layer of service. Its source issue is: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. The relevant initial check is: Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

C.

This check may help with another root cause, for example: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. It does not test the first failed condition; start with: Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

D.

That evidence could be normal while the reported defect persists. It is aimed at: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. Instead inspect: Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

Question 516

During a Junos network change at Clearwater Analytics, the engineer observes: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. Which remediation most directly fixes the described problem?

  1. Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state.
  2. Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.
  3. Align the MST region name, revision and VLAN-to-instance mapping across members, then verify inter-region boundaries where intentional.
  4. Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

Correct answer: D

Explanation of each choice

A.

That would address a separate configuration fault: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. This stem identifies a different cause, corrected by: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

B.

This action may apply to a different problem, for example: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. It does not repair the stated failure boundary. The case-specific reason is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

C.

The other action is relevant when A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. The current case instead requires: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance. The distinction is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

D.

Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance. The case-specific reason is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice. A direct acceptance test is: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

Question 517

The Junos team at Clearwater Analytics needs a success criterion for this defect: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. Which observed result most precisely confirms the intended repair?

  1. MST region members report compatible configuration identity and instance-specific root/port roles align with the VLAN design.
  2. The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.
  3. The edge port remains usable for ordinary hosts but an unexpected BPDU triggers the configured protective action and recorded alert.
  4. The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

Correct answer: B

Explanation of each choice

A.

That check proves something else, such as: A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. It could pass while the stated problem remains. The targeted evidence here is: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

B.

The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links. Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

C.

The observation confirms a different component's behavior. Its source context is: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. In this case the success criterion is: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

D.

That check proves something else, such as: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. It could pass while the stated problem remains. The targeted evidence here is: The intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.

Question 518

While analyzing a service failure at Clearwater Analytics, the following is observed: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. VSTP maintains spanning-tree calculations per VLAN, allowing different VLANs to use different root and forwarding paths.
  2. MSTP maps multiple VLANs to spanning-tree instances, and consistent region configuration is required for shared internal operation.
  3. RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.
  4. Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

Correct answer: D

Explanation of each choice

A.

That principle belongs to a different service stage: A team assumes a single spanning-tree state applies to all VLANs but Junos VSTP shows a blocked uplink for only one customer VLAN. The directly relevant mechanism is: Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

B.

That principle belongs to a different service stage: Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. The directly relevant mechanism is: Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

C.

This explains a separate protocol behavior: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. In the current facts, the controlling mechanism is: Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

D.

Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths. The key distinction is: Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice. Accordingly the remedy is: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

Question 519

The following provider defect remains uncorrected at Clearwater Analytics: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. What is the most direct service or security risk of leaving it unresolved?

  1. An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.
  2. A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
  3. Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
  4. Unexpected region boundaries can alter per-instance forwarding or block paths that the design expected to carry traffic.

Correct answer: A

Explanation of each choice

A.

An unintended root can steer traffic across fragile customer links and cause avoidable topology churn. The direct mitigation is: Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.

B.

That consequence is more closely associated with another deficiency, such as: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. The described fault instead exposes: An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.

C.

It is a risk in another topology or protocol state: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. Here the most direct failure path is: An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.

D.

The concern could occur elsewhere when Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. For the stated scenario, the immediate risk is: An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.

Question 520

A support escalation at Clearwater Analytics describes: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. Where should the Junos operator look first for decisive evidence?

  1. Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.
  2. Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
  3. Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
  4. Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface.

Correct answer: A

Explanation of each choice

A.

Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance. Root selection is based on bridge IDs, not the IP gateway's routing preference or BGP best-path choice.

B.

That evidence could be normal while the reported defect persists. It is aimed at: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. Instead inspect: Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

C.

The check diagnoses a different layer of service. Its source issue is: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. The relevant initial check is: Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

D.

This check may help with another root cause, for example: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. It does not test the first failed condition; start with: Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

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

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports