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 51

Question 500

During provider troubleshooting at Briarfield Healthcare, this symptom is observed: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. Which targeted inspection should precede remediation?

  1. Compare tagged frame captures with both sides' trunk mode and allowed VLAN list, and inspect per-VLAN MAC tables.
  2. Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
  3. Capture the actual Ethernet header tags on both sides and inspect ingress VLAN classification and allowed tag configuration.
  4. Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.

Correct answer: D

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: A campus-to-provider trunk passes several tagged customer services while a newly provisioned tag fails because the far-end trunk has not allowed it. Instead inspect: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.

B.

The check diagnoses a different layer of service. Its source issue is: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. The relevant initial check is: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.

C.

This check may help with another root cause, for example: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. It does not test the first failed condition; start with: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.

D.

Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN. The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.

Question 501

A production change request at Maple Coast Retail includes this finding: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. What should the engineer change to address it?

  1. Enable appropriate BPDU protection on a confirmed edge/customer port and document recovery steps before returning it to service.
  2. Set explicit appropriate bridge priority for the intended root and verify root/port roles across the affected spanning-tree instance.
  3. Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.
  4. Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.

Correct answer: C

Explanation of each choice

A.

That would address a separate configuration fault: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. This stem identifies a different cause, corrected by: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

B.

This action may apply to a different problem, for example: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. It does not repair the stated failure boundary. The case-specific reason is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

C.

Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs. The case-specific reason is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles. A direct acceptance test is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

D.

That would address a separate configuration fault: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. This stem identifies a different cause, corrected by: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

Question 502

After Maple Coast Retail applies its proposed fix to this problem — A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. — which observation best proves the specific failure has been resolved?

  1. The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.
  2. The target VLAN has the intended loop-free forwarding tree while unaffected VLANs retain their existing paths.
  3. MST region members report compatible configuration identity and instance-specific root/port roles align with the VLAN design.
  4. 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.

Correct answer: A

Explanation of each choice

A.

The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy. RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

B.

This would be valid for another situation: A team assumes a single spanning-tree state applies to all VLANs but Junos VSTP shows a blocked uplink for only one customer VLAN. It does not establish that the failing boundary in this scenario works; verify: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

C.

The observation confirms a different component's behavior. Its source context is: Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. In this case the success criterion is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

D.

That check proves something else, such as: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. It could pass while the stated problem remains. The targeted evidence here is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

Question 503

An architecture review at Maple Coast Retail examines the following symptom: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. What Junos or protocol mechanism is most directly responsible?

  1. RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.
  2. BPDU protection guards edge ports against unexpected bridge participation, unlike root protection which guards the root role in an existing spanning-tree topology.
  3. Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear.
  4. Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.

Correct answer: A

Explanation of each choice

A.

RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge. The key distinction is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles. Accordingly the remedy is: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

B.

That principle belongs to a different service stage: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. The directly relevant mechanism is: RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.

C.

This explains a separate protocol behavior: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. In the current facts, the controlling mechanism is: RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.

D.

The statement can be true when The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. But it does not explain the reported failure. Here: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

Question 504

The team at Maple Coast Retail defers a fix for this condition: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. What failure is most likely if no targeted control is applied?

  1. A single VLAN can blackhole or loop while other VLANs appear healthy, masking a per-VLAN control-plane fault.
  2. An unintended root can steer traffic across fragile customer links and cause avoidable topology churn.
  3. Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.
  4. An unauthorized bridge can alter topology or create loops if BPDUs on an edge port are ignored.

Correct answer: C

Explanation of each choice

A.

The concern could occur elsewhere when One VLAN blocks a provider trunk while another forwards correctly because the two VLANs have separate VSTP root and port decisions. For the stated scenario, the immediate risk is: Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.

B.

That consequence is more closely associated with another deficiency, such as: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. The described fault instead exposes: Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.

C.

Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay. The direct mitigation is: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

D.

The concern could occur elsewhere when A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. For the stated scenario, the immediate risk is: Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.

Question 505

During provider troubleshooting at Maple Coast Retail, this symptom is observed: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. Which targeted inspection should precede remediation?

  1. Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.
  2. Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface.
  3. Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
  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.

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.

That evidence could be normal while the reported defect persists. It is aimed at: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. Instead inspect: Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.

C.

The check diagnoses a different layer of service. Its source issue is: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. The relevant initial check is: Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.

D.

This check may help with another root cause, for example: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. 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.

Question 506

At Harborline Transit, a service provider router shows this failure: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. What is the best targeted configuration or operations action?

  1. Inspect and correct the VSTP instance and root/port priorities for the affected VLAN without needlessly changing other VLAN instances.
  2. Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
  3. Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.
  4. Align the MST region name, revision and VLAN-to-instance mapping across members, then verify inter-region boundaries where intentional.

Correct answer: C

Explanation of each choice

A.

The other action is relevant when 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 current case instead requires: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs. The distinction is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

B.

That would address a separate configuration fault: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. This stem identifies a different cause, corrected by: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

C.

Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs. The case-specific reason is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles. A direct acceptance test is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

D.

The other action is relevant when Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. The current case instead requires: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs. The distinction is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

Question 507

A change auditor at Harborline Transit must validate remediation of this finding: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. 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 intended bridge is elected root and all other bridges show a coherent root path and alternate/discarding links.
  3. The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.
  4. The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.

Correct answer: C

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. In this case the success criterion is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

B.

That check proves something else, such as: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. It could pass while the stated problem remains. The targeted evidence here is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

C.

The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy. RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

D.

The observation confirms a different component's behavior. Its source context is: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. In this case the success criterion is: The host port forwards promptly while an unexpected BPDU is detected and handled by the configured protection policy.

Question 508

The operations training team at Harborline Transit discusses this issue: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. Which technical explanation matches the intended correction?

  1. RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.
  2. RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
  3. Spanning tree selects a root bridge based on bridge identifier priority and MAC address, then computes loop-free forwarding paths.
  4. MSTP maps multiple VLANs to spanning-tree instances, and consistent region configuration is required for shared internal operation.

Correct answer: A

Explanation of each choice

A.

RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge. The key distinction is: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles. Accordingly the remedy is: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

B.

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: RSTP edge designation is conditional on the absence of a downstream bridge and must be distinguished from root/alternate port roles.

C.

That principle belongs to a different service stage: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. The directly relevant mechanism is: RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.

D.

This explains a separate protocol behavior: Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. In the current facts, the controlling mechanism is: RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.

Question 509

At Harborline Transit, a service acceptance review considers the unresolved issue: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. 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. A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
  4. Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. Here the most direct failure path is: Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.

B.

Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay. The direct mitigation is: Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.

C.

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: Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.

D.

It is a risk in another topology or protocol state: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. Here the most direct failure path is: Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.

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.

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