A network administrator attempts to configure Core-Switch-01 to serve as the Spanning Tree Protocol (STP) root bridge for VLAN 50. The administrator executes the command to set the bridge priority for VLAN 50 to 61440. Shortly after, a newly provisioned access switch with factory default settings is connected to the network and unexpectedly assumes the root bridge role for VLAN 50. Which of the following best explains why the access switch became the root bridge instead of Core-Switch-01?
- The bridge priority assigned to Core-Switch-01 is numerically higher than the default priority of 32768 on the access switch, and STP prefers the lowest numerical priority value.Answer
- BA native VLAN mismatch on the trunk link caused BPDU frames to be dropped, forcing an automatic reelection that defaulted to the access switch.
- CA duplex mismatch on the inter-switch link corrupted BPDU transmissions, preventing Core-Switch-01 from advertising its bridge priority.
- DSwitches operating on VLAN 50 require an active Layer 3 routing protocol interface to exchange root bridge priority election messages across broadcast domains.
Answer
The bridge priority assigned to Core-Switch-01 is numerically higher than the default priority of 32768 on the access switch, and STP prefers the lowest numerical priority value.
In Spanning Tree Protocol (802.1D / 802.1w), the root bridge election is determined by the lowest Bridge ID (BID). The default bridge priority for switches is 32768 (plus the VLAN ID extension). When the administrator set the core switch priority to 61440, the numerical value was increased instead of decreased. As a result, the newly attached switch with its default priority of 32768 had a lower numerical BID and won the root bridge election.
Step-by-Step Solution
Key Concept
Spanning Tree Protocol (STP) Root Bridge Election and Priority Mechanics