Refer to the exhibit.

The correct remediation is to establish a VSX keepalive connection using the management interfaces between SW-A and SW-B . The two links on interfaces 1/1/53 and 1/1/54 form the VSX Inter-Switch Link (ISL). When that ISL fails, the VSX peers require an independent keepalive path to distinguish an ISL failure from a complete peer failure and prevent an uncontrolled split condition.

HPE Aruba Networking specifically recommends that keepalive communication use a path independent of the ISL and states that keepalive should not traverse VSX LAG uplinks . With keepalive operational, when the ISL becomes out-of-sync, the primary continues forwarding while the secondary can suppress its VSX LAG member ports, preventing both peers from independently forwarding traffic toward Router-A and SW-C. Aruba Networks

The management VRF is explicitly supported for VSX keepalive source and peer addresses, making the dedicated management interfaces an appropriate fault-independent path. Aruba Networks

vsx shutdown-on-split is intended primarily for non-VSX interfaces on the secondary ; it is not the appropriate protection for the dual-homed VSX LAG topology shown. HPE documentation also states that this command has no split-state effect on the primary, eliminating option C. Aruba Networks

Study Guide References: VSX Keepalive, ISL Failure Handling, Split-Brain Prevention, VSX LAG Failure Behavior, Management-VRF Keepalive.