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