Question 300
At fictional Willow Transportation, a network engineer supporting fleet operations is reviewing RSTP, MSTP and switching interconnects during a production cutover (HCIP-H12-821-SWITCH-075). The observed network issue is: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. Which routing, switching, or network principle best explains the appropriate solution?
Explanation
Correct Answer
The governing principle is: Stack resiliency requires deliberate master election and partition handling. In this scenario, the appropriate action is: Check split-brain prevention mechanisms and stack topology supported by the platform. Valid evidence would show: The remaining stack behaves predictably and avoids simultaneous unauthorized active masters.
Incorrect Answers
“MSTP permits multiple VLANs to share explicitly defined spanning-tree instances” responds to another technical or business failure: A network requires multiple spanning-tree topologies but maps all VLANs into one MST instance. That source case depends on: MSTP permits multiple VLANs to share explicitly defined spanning-tree instances. The present issue is: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. The more direct action is “Stack resiliency requires deliberate master election and partition handling” because Stack resiliency requires deliberate master election and partition handling.
“Spanning-tree selected paths depend on cumulative root cost and bridge identifiers” responds to another technical or business failure: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. That source case depends on: Spanning-tree selected paths depend on cumulative root cost and bridge identifiers. The present issue is: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. The more direct action is “Stack resiliency requires deliberate master election and partition handling” because Stack resiliency requires deliberate master election and partition handling.
“VLAN trunking requires explicit compatible tagging and allowed membership” responds to another technical or business failure: A technician adds a new VLAN but leaves it out of the allowed trunk list between access and aggregation switches. That source case depends on: VLAN trunking requires explicit compatible tagging and allowed membership. The present issue is: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. The more direct action is “Stack resiliency requires deliberate master election and partition handling” because Stack resiliency requires deliberate master election and partition handling.