352-001 · Question #701
Which design benefit of Bridge Assurance is true?
The correct answer is A. It prevents switch loops caused by unidirectional point-to-point link condition on Rapid PVST+ and. Bridge Assurance prevents switch loops caused by unidirectional link failures by requiring continuous BPDU exchange on all point-to-point ports in Rapid PVST+ and MST.
Question
Which design benefit of Bridge Assurance is true?
Options
- AIt prevents switch loops caused by unidirectional point-to-point link condition on Rapid PVST+ and
- BIt allows small, unmanaged switches to be plugged into ports of access switches without the risk
- CIt prevents switched traffic from traversing suboptimal paths on the network
- DIt suppresses a spanning-tree topology change upon connecting and disconnecting a station on a
How the community answered
(49 responses)- A90% (44)
- B6% (3)
- C2% (1)
- D2% (1)
Why each option
Bridge Assurance prevents switch loops caused by unidirectional link failures by requiring continuous BPDU exchange on all point-to-point ports in Rapid PVST+ and MST.
Bridge Assurance sends BPDUs out of every network port including ports in a blocking state, and if a port stops receiving BPDUs it enters a Bridge Assurance Inconsistent blocking state, stopping traffic forwarding. This directly addresses unidirectional link conditions on Rapid PVST+ and MST topologies where a one-way failure would otherwise allow a port to incorrectly transition to forwarding and create a loop.
Safely allowing unmanaged switches to connect without loop risk describes BPDU Guard paired with PortFast, not Bridge Assurance.
Preventing traffic from traversing suboptimal paths is a function of correct root bridge placement and STP load balancing, not Bridge Assurance.
Suppressing topology change notifications when end stations connect or disconnect is the behavior of PortFast, not Bridge Assurance.
Concept tested: Bridge Assurance unidirectional link loop prevention
Source: https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24062-146.html
Topics
Community Discussion
No community discussion yet for this question.