Question 440
At fictional Zenith Cloudworks, a network engineer supporting data center interconnects is reviewing VRRP, BFD and redundancy design during a controlled failover exercise (HCIP-H12-821-RELIABILITY-110). The observed network issue is: A switch stack offers redundant members but its sole uplink attaches to one device and remains a failure point. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Distribute or aggregate uplinks across supported stack members with correct failure design. The specific reported fault is: A switch stack offers redundant members but its sole uplink attaches to one device and remains a failure point. Confirmation should show: A member failure retains approved northbound connectivity through the surviving stack. The supporting technical principle is: Hardware redundancy only improves availability when dependent paths are also redundant.
Incorrect Answers
“Verify routing protocol and FIB state separately from the BFD liveliness signal” responds to another technical or business failure: A BFD session is Up but a technician assumes that means every destination route through the neighbor is installed. That source case depends on: BFD monitors a forwarding path but does not by itself create routing advertisements. The present issue is: A switch stack offers redundant members but its sole uplink attaches to one device and remains a failure point. The more direct action is “Distribute or aggregate uplinks across supported stack members with correct failure design” because Hardware redundancy only improves availability when dependent paths are also redundant.
“Align supported VRRP version and security or compatibility parameters for the segment” responds to another technical or business failure: Two VRRP routers advertise the same group but use mismatched authentication or version support settings. That source case depends on: VRRP members must process compatible advertisements to coordinate gateway state. The present issue is: A switch stack offers redundant members but its sole uplink attaches to one device and remains a failure point. The more direct action is “Distribute or aggregate uplinks across supported stack members with correct failure design” because Hardware redundancy only improves availability when dependent paths are also redundant.
“Adjust appropriate tracking conditions, hysteresis or delay settings and repair unstable uplink state” responds to another technical or business failure: A VRRP group flaps repeatedly because upstream connectivity causes tracked priority to alternate around the peer threshold. That source case depends on: Unstable track state can cause repeated virtual-gateway ownership changes. The present issue is: A switch stack offers redundant members but its sole uplink attaches to one device and remains a failure point. The more direct action is “Distribute or aggregate uplinks across supported stack members with correct failure design” because Hardware redundancy only improves availability when dependent paths are also redundant.