JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
During a Junos network change at Crestpoint Research, the engineer observes: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. Which remediation most directly fixes the described problem?
The other action is relevant when A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. The current case instead requires: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path. The distinction is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
That would address a separate configuration fault: A team assumes a single spanning-tree state applies to all VLANs but Junos VSTP shows a blocked uplink for only one customer VLAN. This stem identifies a different cause, corrected by: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path. The case-specific reason is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure. A direct acceptance test is: The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
The Junos team at Crestpoint Research needs a success criterion for this defect: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. Which observed result most precisely confirms the intended repair?
The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails. A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
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 redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
This would be valid for another situation: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. It does not establish that the failing boundary in this scenario works; verify: The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
The observation confirms a different component's behavior. Its source context is: A team assumes a single spanning-tree state applies to all VLANs but Junos VSTP shows a blocked uplink for only one customer VLAN. In this case the success criterion is: The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
While analyzing a service failure at Crestpoint Research, the following is observed: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. Which mechanism best explains the underlying control-plane or forwarding behavior?
This explains a separate protocol behavior: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. In the current facts, the controlling mechanism is: RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure. The key distinction is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure. Accordingly the remedy is: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
That principle belongs to a different service stage: One VLAN blocks a provider trunk while another forwards correctly because the two VLANs have separate VSTP root and port decisions. The directly relevant mechanism is: RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
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: RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
The following provider defect remains uncorrected at Crestpoint Research: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. What is the most direct service or security risk of leaving it unresolved?
It is a risk in another topology or protocol state: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. Here the most direct failure path is: Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
The concern could occur elsewhere when A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. For the stated scenario, the immediate risk is: Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover. The direct mitigation is: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
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: Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
A support escalation at Crestpoint Research describes: A backup link remains discarding in a redundant topology and an operator assumes that discarding always means the link failed. Where should the Junos operator look first for decisive evidence?
The check diagnoses a different layer of service. Its source issue is: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. The relevant initial check is: Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
This check may help with another root cause, for example: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. It does not test the first failed condition; start with: Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
The check diagnoses a different layer of service. Its source issue is: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. The relevant initial check is: Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests. A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
The provider operations team at Atlas Port Services reports: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. Which implementation decision best corrects the cause?
This action may apply to a different problem, for example: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. It does not repair the stated failure boundary. The case-specific reason is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path. The case-specific reason is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure. A direct acceptance test is: The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
That would address a separate configuration fault: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. This stem identifies a different cause, corrected by: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
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: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
During a post-change check at Atlas Port Services, the original condition was: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. What evidence would validate the corrected behavior?
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 redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails. A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
That check proves something else, such as: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. It could pass while the stated problem remains. The targeted evidence here is: The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The redundant link remains nonforwarding during normal operation and transitions to the appropriate forwarding role after the primary path fails.
At Atlas Port Services, an engineer is asked to explain this case: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. Which underlying routing or switching principle accounts for the appropriate solution?
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: RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
This explains a separate protocol behavior: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. In the current facts, the controlling mechanism is: RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure.
The statement can be true when A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. But it does not explain the reported failure. Here: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
RSTP assigns forwarding and discarding roles to maintain loop-free topology while allowing an alternate path to converge on failure. The key distinction is: A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure. Accordingly the remedy is: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
A risk assessment at Atlas Port Services identifies: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. Which practical consequence is most specifically tied to this failure?
That consequence is more closely associated with another deficiency, such as: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. The described fault instead exposes: Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
It is a risk in another topology or protocol state: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. Here the most direct failure path is: Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover. The direct mitigation is: Validate alternate and root port roles and correct the path-cost or topology configuration required for a usable backup path.
That consequence is more closely associated with another deficiency, such as: One VLAN blocks a provider trunk while another forwards correctly because the two VLANs have separate VSTP root and port decisions. The described fault instead exposes: Forcing every redundant link to forward creates loops; an invalid alternate can instead leave the site disconnected on failover.
The on-call engineer at Atlas Port Services receives this fault report: During a primary uplink outage, a standby port does not take over and bridge role data indicate it was not a valid alternate. What initial check best isolates the actual failing protocol stage?
Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests. A designated alternate port can be intentionally discarding and still serve as a valid backup; oper-state alone does not prove failure.
The check diagnoses a different layer of service. Its source issue is: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. The relevant initial check is: Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
This check may help with another root cause, 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 test the first failed condition; start with: Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
That evidence could be normal while the reported defect persists. It is aimed at: Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. Instead inspect: Inspect STP/RSTP role, state, path cost and BPDU information on both uplinks during normal and failure tests.
Please check your mailbox for a message from support@examlabs.com and follow the directions.