Which feature is required to prevent a split-brain condition for a branch in an Enhanced HA?

Question

Options

• ASplit Brain Detection
• BSD-WAN Service Reachable on the private overlay
• CCloud VPN
• DVRRP

• A
  5% (1)
• B
  81% (17)
• C
  5% (1)
• D
  10% (2)

Explanation

In Enhanced HA, both HA peers must have a reliable way to communicate with each other to know who is active and who is standby. SD-WAN Service Reachable on the private overlay provides that dedicated inter-peer heartbeat channel - if this path is available, the standby device knows the active peer is alive and won't also declare itself active, which is the definition of split-brain prevention.

Why the distractors are wrong:

• A (Split Brain Detection): This sounds plausible, but it is not a configurable feature name in this context - the actual mechanism that prevents split-brain is the private overlay reachability check.
• C (Cloud VPN): Cloud VPN is a routing/segmentation construct, not an HA synchronization mechanism.
• D (VRRP): VRRP handles default gateway redundancy at Layer 3 but is not the feature that governs active/standby arbitration within Enhanced HA's split-brain logic.

Memory tip: Think "private = private line between partners." The two HA devices use the private overlay as their exclusive phone line - if that line is up, only one device stays active. No private line = no coordination = both go active = split-brain.

No community discussion yet for this question.