In complex network designs involving different administrative domains (like a Campus and a Data Center), it is often desirable to prevent Spanning Tree Protocol (STP) from merging the two environments into a single, massive logical tree.
The Goal of Isolation: " Isolated spanning tree topology " means that the Campus and the Data Center should each have their own independent Root Bridge and calculate their own loop-free paths without being influenced by one another.
BPDU Filter (The Solution): When you apply BPDU Filter to an interface, the switch stops sending BPDUs out of that port and, more importantly, ignores any incoming BPDUs. Because the Campus switch no longer " sees " the BPDUs coming from the Data Center core, it will stop recognizing the DC as the Root Bridge and will instead elect a local Root Bridge (or remain as the Root itself). This effectively breaks the STP connection between the two domains while still allowing Layer 2 data traffic to flow.
Evaluating Other Options:
Option A (Root Guard): This is used to prevent a specific port from becoming a Root Port. If a superior BPDU is received, the port is placed into a " root-inconsistent " state (blocked). While this protects the local Root role, it does not " isolate " the topology; the switches still participate in the same overall STP domain.
Option C (BPDU Guard): This is intended for edge ports (connected to PCs/Printers). If it receives a BPDU, it shuts down the port entirely (rxtx-disable). Applying this to a core-to-core link would cause a total loss of connectivity as soon as the DC core sends a BPDU.
Option D (Admin Edge): This simply tells the switch to skip the Listening/Learning states and go straight to Forwarding. It does not provide topology isolation.
