Question 680
At fictional Pinewell Electronics, a network engineer supporting engineering labs is reviewing RSTP, MSTP and switching interconnects during a controlled failover exercise (HCIP-H12-821-SWITCH-170). The observed network issue is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Align region name, revision level and VLAN-instance mappings across the intended domain. The specific reported fault is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. Confirmation should show: MST configuration digests agree and switches join the intended common region. The supporting technical principle is: MST region membership depends on a consistent configuration digest, not merely a label.
Incorrect Answers
“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: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. The more direct action is “Align region name, revision level and VLAN-instance mappings across the intended domain” because MST region membership depends on a consistent configuration digest, not merely a label.
“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: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. The more direct action is “Align region name, revision level and VLAN-instance mappings across the intended domain” because MST region membership depends on a consistent configuration digest, not merely a label.
“Correct interface PVID or VLAN membership and validate separation with source MAC observations” responds to another technical or business failure: Users from two access VLANs unexpectedly communicate at layer 2 because the same port VLAN was configured on both groups. That source case depends on: A switch forwarding domain is determined by VLAN tagging and port membership. The present issue is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. The more direct action is “Align region name, revision level and VLAN-instance mappings across the intended domain” because MST region membership depends on a consistent configuration digest, not merely a label.