You already covered this in CCNA.
Quick recap before ENCOR pushes into MST.The Redundant Path
SW1 connects to both SW2 and SW3, and SW2 and SW3 also connect directly to each other.

Figure 1 – Redundant topology: two physical paths from PC1 to the server
That gives PC1 more than one path to the server.
The Broadcast Spreads
Watch what happens when PC1 needs the server's MAC address: it sends an ARP broadcast.

Figure 2 – PC1 sends an ARP broadcast
SW1 floods it out every other port, duplicating the frame toward both SW2 and SW3.

Figure 3 – SW1 floods the broadcast toward SW2 and SW3
Answer the question below
What type of frame does SW1 flood toward SW2 and SW3?
The Loop Forms
SW2 and SW3 flood it again, and the same frame starts circulating back and forth between all three switches: a switching loop.

Figure 4 – SW2 and SW3 flood it again, the loop begins
Each pass through the loop duplicates the frame again. CPU usage spikes, MAC address tables flap between interfaces, and the network eventually stops responding under a broadcast storm.

Figure 5 – CPU spikes as the loop multiplies frames
Answer the question below
What does the network turn into when frames circulate endlessly?
STP solves the loop problem by picking one active path between any two switches and putting every redundant port into a blocking state. The port stays physically up but forwards no user traffic.
Blocking the Redundant Port
One port on SW3 gets picked to sit in blocking state while every other port keeps forwarding.

Figure 6 – STP blocks the redundant path
Verifying the Block
Verify it on SW3:
SW3# show spanning-tree vlan 1 VLAN0001 Spanning tree enabled protocol ieee Root ID Priority 32769 Address AABB.CCDD.EE01 Cost 4 Port 3 (Gi0/2) Bridge ID Priority 32769 (priority 32768 sys-id-ext 1) Address AABB.CCDD.EE03 Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- ----------------------------- Gi0/0 Altn BLK 4 128.1 P2p Gi0/2 Root FWD 4 128.3 P2pYou can see Gi0/0 sits in
Altn BLK: the link to SW2 is up, but STP refuses to forward on it.
That single blocked port is what keeps this topology loop-free.With STP active, that same ARP broadcast from earlier never makes it back around the loop.

Figure 7 – The broadcast stops at the blocked port instead of looping back
Answer the question below
Which interface does STP block on SW3?
You've just seen one path stay blocked. But how do the switches agree on which one blocks?
It starts with how each one identifies itself.The Example Topology
Every STP decision you've seen so far comes back to one root cause: which switch holds the lowest Bridge ID.

Figure 8 – Three-switch topology used in this example
What Is a Bridge ID
A Bridge ID (BID), defined in IEEE 802.1D, combines a configurable priority (default
32768plus the VLAN ID) with the switch's MAC address.
Figure 9 – Bridge ID structure: priority, VLAN, and MAC address
Every switch in the topology ends up with its own unique BID this way, so you can tell them apart at a glance.
Answer the question below
What is the default STP bridge priority value?
What BPDUs Contain
Switches exchange this identity inside BPDUs, which carry three fields that matter for the election:
Root Bridge ID: identifies the switch the sender currently believes is Root.
Sender's Bridge ID: the BID of the switch that sent the BPDU.
Path Cost: the cumulative cost from the sender back to the Root.
Here is what that exchange looks like between neighboring switches.

Figure 10 – A BPDU exchange between neighboring switches
Answer the question below
Which BPDU field identifies the switch that sent the BPDU?
Answer the question below
If SW3's Gi0/2 link to SW1 fails, all links costing 4, what Root ID Cost does SW3 show?
With BPDUs flowing between all three switches, here is how the actual election plays out.
Every Switch Claims Root
Every switch starts by advertising its own BID as if it were already Root.
As BPDUs cross the network, each switch keeps only the lowest BID it has seen and drops its own claim once a better one shows up.
Figure 11 – Every switch initially claims to be Root
At this stage, every switch still treats its own BID as the best claim to be Root, until the comparison plays out.
Answer the question below
What does every switch initially believe about itself?
SW1 Wins the Comparison
Three Bridge IDs, one winner: the lowest value takes the role.

Figure 12 – SW1 wins this election with the lowest Bridge ID
Here, SW1, SW2, and SW3 all share the same priority, so the comparison falls to the MAC address.
SW1'sAABB.CCDD.EE01is the lowest, so SW1 becomes Root.The Topology Converges
From that point on, only SW1 originates BPDUs.
Every other switch forwards them downstream, carrying SW1's Root BID alongside its own Sender BID.
Figure 13 – Every switch now recognizes SW1 as Root
You know how the election works. The Root Bridge Configuration Lab puts you back on the SW1, SW2, SW3 topology to force that outcome yourself and verify it end to end.
Answer the question below
What breaks the tie when two switches share the same priority?