Question 380
At fictional Summit Agriculture, a network engineer supporting remote rural branches is reviewing RSTP, MSTP and switching interconnects during a baseline compliance test (HCIP-H12-821-SWITCH-095). The observed network issue is: Two switches are configured for stacking but fail to form one logical unit due to incompatible member identifiers. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Align stack member identities, link topology and compatible software and hardware requirements. The specific reported fault is: Two switches are configured for stacking but fail to form one logical unit due to incompatible member identifiers. Confirmation should show: Both members appear in one stable logical stack with correct master and standby roles. The supporting technical principle is: Switch stacking creates a logical control relationship from compatible physical members.
Incorrect Answers
“Check split-brain prevention mechanisms and stack topology supported by the platform” responds to another technical or business failure: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. That source case depends on: Stack resiliency requires deliberate master election and partition handling. The present issue is: Two switches are configured for stacking but fail to form one logical unit due to incompatible member identifiers. The more direct action is “Align stack member identities, link topology and compatible software and hardware requirements” because Switch stacking creates a logical control relationship from compatible physical members.
“Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy” responds to another technical or business failure: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. That source case depends on: Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks. The present issue is: Two switches are configured for stacking but fail to form one logical unit due to incompatible member identifiers. The more direct action is “Align stack member identities, link topology and compatible software and hardware requirements” because Switch stacking creates a logical control relationship from compatible physical members.
“Permit the intended tagged VLAN on both sides of the trunk without broadening unrelated VLAN access” 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: Two switches are configured for stacking but fail to form one logical unit due to incompatible member identifiers. The more direct action is “Align stack member identities, link topology and compatible software and hardware requirements” because Switch stacking creates a logical control relationship from compatible physical members.