JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Keystone Industrial describes: A provider edge customer handoff occasionally introduces an unapproved switch and the operator wants the interface to fail safely if BPDUs appear. Where should the Junos operator look first for decisive evidence?
That evidence could be normal while the reported defect persists. It is aimed at: The provider expects a designated core switch to remain root but a customer's bridge ID and priority cause repeated unwanted root elections. Instead inspect: Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface.
Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface. BPDU guard checks for unexpected participation, whereas root guard checks whether a peer is attempting to claim superior root status.
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: Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface.
That evidence could be normal while the reported defect persists. It is aimed at: One VLAN blocks a provider trunk while another forwards correctly because the two VLANs have separate VSTP root and port decisions. Instead inspect: Inspect whether the port is a true edge, count inbound BPDUs and verify the intended BPDU-protection action on that interface.
During a Junos network change at Brookport Finance, the engineer observes: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. Which remediation most directly fixes the described problem?
This action may apply to a different problem, for example: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. It does not repair the stated failure boundary. The case-specific reason is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
The other action is relevant when One VLAN blocks a provider trunk while another forwards correctly because the two VLANs have separate VSTP root and port decisions. The current case instead requires: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state. The distinction is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state. The case-specific reason is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient. A direct acceptance test is: 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.
The Junos team at Brookport Finance needs a success criterion for this defect: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. Which observed result most precisely confirms the intended repair?
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. Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
The observation confirms a different component's behavior. Its source context is: A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. In this case the success criterion is: 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.
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: 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.
That check proves something else, such as: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. It could pass while the stated problem remains. The targeted evidence here is: 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.
While analyzing a service failure at Brookport Finance, the following is observed: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. Which mechanism best explains the underlying control-plane or forwarding behavior?
That principle belongs to a different service stage: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. The directly relevant mechanism is: Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear.
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: Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear.
Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear. The key distinction is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient. Accordingly the remedy is: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state.
The statement can be true 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. But it does not explain the reported failure. Here: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
The following provider defect remains uncorrected at Brookport Finance: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. What is the most direct service or security risk of leaving it unresolved?
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: A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
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: A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
It is a risk in another topology or protocol state: Two neighboring switches intended to share one MSTP region have different VLAN-to-instance mappings and behave as boundary devices. Here the most direct failure path is: A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure. The direct mitigation is: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state.
A support escalation at Brookport Finance describes: A network uplink receives superior BPDUs from an unexpected downstream customer bridge and the primary spanning-tree root changes. Where should the Junos operator look first for decisive evidence?
That evidence could be normal while the reported defect persists. It is aimed at: A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. Instead inspect: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
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: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
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 the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard. Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
The provider operations team at Seawood Media reports: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. Which implementation decision best corrects the cause?
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: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state. The distinction is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state. The case-specific reason is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient. A direct acceptance test is: 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.
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: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
The other action is relevant when 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 current case instead requires: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state. The distinction is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
During a post-change check at Seawood Media, the original condition was: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. What evidence would validate the corrected behavior?
The observation confirms a different component's behavior. Its source context is: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. In this case the success criterion is: 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.
That check proves something else, such as: A user access port suddenly receives bridge protocol data units from an unmanaged switch and risks forming an unauthorized transit path. It could pass while the stated problem remains. The targeted evidence here is: 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.
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. Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
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: 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.
At Seawood Media, an engineer is asked to explain this case: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. Which underlying routing or switching principle accounts for the appropriate solution?
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: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
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 protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear. The key distinction is: Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient. Accordingly the remedy is: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state.
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: Root protection prevents unexpected downstream superior root claims; loop protection keeps a port from wrongly forwarding when expected BPDUs disappear.
A risk assessment at Seawood Media identifies: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. Which practical consequence is most specifically tied to this failure?
A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure. The direct mitigation is: Select the correct root-protection or loop-protection mechanism for the actual superior-BPDU or lost-BPDU threat and validate its triggered state.
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: A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
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: A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
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: A lost or spoofed spanning-tree control message can open a Layer 2 forwarding loop or shift the root outside trusted infrastructure.
The on-call engineer at Seawood Media receives this fault report: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. What initial check best isolates the actual failing protocol stage?
Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard. Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.
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: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
That evidence could be normal while the reported defect persists. It is aimed at: A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. Instead inspect: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
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: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
Please check your mailbox for a message from support@examlabs.com and follow the directions.