JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.