Cisco 200-301 Exam Dumps, Practice Test Questions

Root Guard reacts to superior BPDUs arriving, not to an alternate port unexpectedly losing its expected BPDUs.

BPDU Guard is intended for edge ports that must not receive switch BPDUs, not for a legitimate redundant switch uplink.

PortFast would bypass some edge convergence behavior and could increase loop risk if applied to a redundant switch uplink.

The bridge ID compares priority first, then MAC address; B loses on priority even though its MAC is smaller.

Root election does not require a separate device, and the elected root has designated ports rather than a root port.

Each spanning-tree instance has a single elected root bridge; differing priorities do not produce two roots for one VLAN.

STP seeks the least-cost path to the root, so cost 19 loses to an otherwise eligible path with cost 8.

A non-root bridge selects a single root port per spanning-tree instance, although other paths may be alternate or designated.

Port ID is used only after earlier comparison criteria tie; an explicit path-cost difference decides this case.

A cost of 12 is worse than the neighbor’s advertised cost 4 for reaching the same root on a shared segment.

A shared segment elects one designated port for an STP instance; simultaneous designated forwarding would defeat loop prevention.

PortFast is an edge-transition feature, not a substitute for the designated bridge selection criteria in competing BPDUs.

A non-root switch normally selects one root port for each spanning-tree instance; the backup cannot simultaneously become the same switch's second forwarding root port.

A designated forwarding port wins on its segment; placing this nonpreferred redundant path into forwarding would risk creating the Layer 2 loop the scenario excludes.

A redundancy alternate can remain physically up and participate in BPDU processing while not forwarding user frames; it need not be administratively shut down.

Discarding neither forwards user frames nor learns destination-MAC information; the stem explicitly says source-MAC learning occurs.

A forwarding state sends normal user data traffic, which the transitioning port has not yet begun doing.

Alternate is a topology role that normally remains discarding, not the learning state defined by MAC-table learning without data forwarding.

32769 is not a valid 4096-multiple bridge priority value on the specified Cisco extended-system-ID model.

A numerically higher priority is less preferred than the competitors at 32768 and would not win root election.

MAC address aging does not lower the bridge ID or win the STP root election.

This lists VLAN presence and access-port membership but does not expose the STP root bridge ID or per-port spanning-tree roles.

This shows VLAN tag transport and active trunk VLANs, not the full per-VLAN STP path-cost and root/role data.

A summary can show broad STP mode and counts, but the requested detailed topology is specifically for VLAN 10.

A numerically lower priority would make B more preferred than A, violating the desired primary-root election.

A common priority leaves root preference to bridge-ID MAC tie-break, not the explicit deterministic primary/backup requirement.

Then a third switch with a lower priority could win when A disappears, so B would not be the intended backup.

Allowing every edge to forward without loop control risks a Layer 2 bridging loop in the triangle.

A shutdown removes the candidate failover path rather than retaining it as an available STP-controlled alternate.

Root bridge ports normally provide forwarding paths; administrative shutdown is not spanning-tree’s selective nonpreferred blocking behavior.

Administrative status cannot distinguish RSTP discarding, learning and forwarding on an otherwise up Ethernet interface.

Layer 3 path costs do not identify a specific RSTP port role and port state transition.

Aging timer values do not show the negotiated RSTP role/state transitions of the port.