Pass Your Cisco 350-401 Exam Easy!

Setting an appropriate lower bridge priority on the intended root switch for that STP instance/VLAN would not align MST region name, revision and VLAN-to-instance mapping on the intended region members.

Mapping the VLAN groups into separate MST instances and tune root priorities per instance would not align MST region name, revision and VLAN-to-instance mapping on the intended region members.

Interpreting per-instance RSTP/MST port roles and forwarding states would not align MST region name, revision and VLAN-to-instance mapping on the intended region members.

This test measures a different behavior: Check each instance root and link roles against the intended uplink path. It does not establish the target outcome. For the documented fault, the direct acceptance test is: inspect MST configuration digests and boundary-port behavior on both peers.

This test measures a different behavior: Compare port state for each VLAN/MST instance with physical interface status. It does not establish the target outcome. For the documented fault, the direct acceptance test is: inspect MST configuration digests and boundary-port behavior on both peers.

This test measures a different behavior: Check `show spanning-tree vlan 100` root bridge ID and root port choices across the topology. It does not establish the target outcome. For the documented fault, the direct acceptance test is: inspect MST configuration digests and boundary-port behavior on both peers.

That diagnosis is supported by a different symptom: The interface is physically up but carries some VLANs and blocks others as designed. Here the recorded observation is: an intra-region link acts as an MST boundary and yields unexpected instance topology. The applicable cause is: the MST region configuration digest differs because VLAN-to-instance mapping is inconsistent.

That diagnosis is supported by a different symptom: A small access switch becomes VLAN100's spanning-tree root after a new switch is connected. Here the recorded observation is: an intra-region link acts as an MST boundary and yields unexpected instance topology. The applicable cause is: the MST region configuration digest differs because VLAN-to-instance mapping is inconsistent.

That diagnosis is supported by a different symptom: Both VLAN groups follow one uplink because all VLANs were left in the same MST instance. Here the recorded observation is: an intra-region link acts as an MST boundary and yields unexpected instance topology. The applicable cause is: the MST region configuration digest differs because VLAN-to-instance mapping is inconsistent.

Selecting root priorities for MST instances does not correct a disagreement in VLAN-to-instance mappings between switches claiming one region.

That control reduces a separate risk: Per-instance STP forwarding state was confused with physical-link operability. For the described design, the recurring risk arises from: the MST region configuration digest differs because VLAN-to-instance mapping is inconsistent. The specific required safeguard is: treat MST revision, name and VLAN maps as one controlled configuration unit.

Bridge priority affects root election; it does not make two different MST region mappings consistent.

Interpreting per-instance RSTP/MST port roles and forwarding states would not map the VLAN groups into separate MST instances and tune root priorities per instance.

Configuring an appropriate secondary root priority higher than primary but below ordinary access switches would not map the VLAN groups into separate MST instances and tune root priorities per instance.

Aligning MST region name, revision and VLAN-to-instance mapping on the intended region members would not map the VLAN groups into separate MST instances and tune root priorities per instance.

This test measures a different behavior: Disable primary in a lab and inspect the next-lowest bridge ID selection. It does not establish the target outcome. For the documented fault, the direct acceptance test is: check each instance root and link roles against the intended uplink path.

This test measures a different behavior: Inspect MST configuration digests and boundary-port behavior on both peers. It does not establish the target outcome. For the documented fault, the direct acceptance test is: check each instance root and link roles against the intended uplink path.

This test measures a different behavior: Compare port state for each VLAN/MST instance with physical interface status. It does not establish the target outcome. For the documented fault, the direct acceptance test is: check each instance root and link roles against the intended uplink path.

That diagnosis is supported by a different symptom: The interface is physically up but carries some VLANs and blocks others as designed. Here the recorded observation is: both VLAN groups follow one uplink because all VLANs were left in the same MST instance. The applicable cause is: there is no distinct per-group spanning-tree instance topology.

That diagnosis is supported by a different symptom: An unintended access switch becomes root after the designed primary goes offline. Here the recorded observation is: both VLAN groups follow one uplink because all VLANs were left in the same MST instance. The applicable cause is: there is no distinct per-group spanning-tree instance topology.

That diagnosis is supported by a different symptom: An intra-region link acts as an MST boundary and yields unexpected instance topology. Here the recorded observation is: both VLAN groups follow one uplink because all VLANs were left in the same MST instance. The applicable cause is: there is no distinct per-group spanning-tree instance topology.

That control reduces a separate risk: Per-instance STP forwarding state was confused with physical-link operability. For the described design, the recurring risk arises from: there is no distinct per-group spanning-tree instance topology. The specific required safeguard is: audit instance-to-VLAN mapping whenever VLANs are added or removed.

That control reduces a separate risk: Root priority policy was not established, so the lowest bridge ID won unexpectedly. For the described design, the recurring risk arises from: there is no distinct per-group spanning-tree instance topology. The specific required safeguard is: audit instance-to-VLAN mapping whenever VLANs are added or removed.

That control reduces a separate risk: The MST region configuration digest differs because VLAN-to-instance mapping is inconsistent. For the described design, the recurring risk arises from: there is no distinct per-group spanning-tree instance topology. The specific required safeguard is: audit instance-to-VLAN mapping whenever VLANs are added or removed.

Interpreting per-instance RSTP/MST port roles and forwarding states would not meet the need for rSTP proposal/agreement behavior on suitable point-to-point links rather than legacy 802.1D timer-only expectations.

Enabling supported loop guard on eligible non-designated point-to-point spanning-tree ports would not meet the need for rSTP proposal/agreement behavior on suitable point-to-point links rather than legacy 802.1D timer-only expectations.

Setting an appropriate lower bridge priority on the intended root switch for that STP instance/VLAN would not meet the need for rSTP proposal/agreement behavior on suitable point-to-point links rather than legacy 802.1D timer-only expectations.

This test measures a different behavior: Check `show spanning-tree vlan 100` root bridge ID and root port choices across the topology. It does not establish the target outcome. For the documented fault, the direct acceptance test is: watch port state changes during controlled re-convergence and verify synchronization completes without a prolonged listening stage.

This test measures a different behavior: Suppress BPDUs in a lab and confirm the port enters loop-inconsistent rather than transitioning to designated forwarding. It does not establish the target outcome. For the documented fault, the direct acceptance test is: watch port state changes during controlled re-convergence and verify synchronization completes without a prolonged listening stage.

This test measures a different behavior: Compare port state for each VLAN/MST instance with physical interface status. It does not establish the target outcome. For the documented fault, the direct acceptance test is: watch port state changes during controlled re-convergence and verify synchronization completes without a prolonged listening stage.

That diagnosis is supported by a different symptom: A blocked alternate port starts forwarding after BPDUs cease, creating a loop. Here the recorded observation is: a peer connected through a legacy shared segment converges slowly despite local RSTP configuration. The applicable cause is: rapid proposal/agreement handshakes are not available across that legacy/boundary link.

That diagnosis is supported by a different symptom: A small access switch becomes VLAN100's spanning-tree root after a new switch is connected. Here the recorded observation is: a peer connected through a legacy shared segment converges slowly despite local RSTP configuration. The applicable cause is: rapid proposal/agreement handshakes are not available across that legacy/boundary link.

That diagnosis is supported by a different symptom: The interface is physically up but carries some VLANs and blocks others as designed. Here the recorded observation is: a peer connected through a legacy shared segment converges slowly despite local RSTP configuration. The applicable cause is: rapid proposal/agreement handshakes are not available across that legacy/boundary link.