In a VRRP hot backup scenario, which of the following situations will trigger a master-slave switch? (Multiple choice)

Question

Options

• AThe active WAC itself fails, such as a sudden power outage or hardware failure.
• BThe uplink of the active WAC fails. Based on the VRRP linkage function, the VRRP backup group
• CThe HSB master-slave channel between the master and backup WAC is suddenly disconnected
• DThe downlink link of the active WAC fails, causing the VLANIF interface bound to the HSB backup

• A
  75% (39)
• C
  25% (13)

Explanation

In VRRP hot backup, a master-slave switch only occurs when the active WAC can no longer adequately serve traffic - A (complete hardware/power failure), B (uplink failure detected via VRRP interface tracking, which lowers the active WAC's priority below the backup's), and D (downlink failure brings down the bound VLANIF interface, similarly triggering a VRRP priority change) all represent conditions where the active WAC is impaired or unreachable, so the backup legitimately takes over.

Option C is wrong because the HSB (Hot Standby Backup) channel is only a state-synchronization link between master and backup - losing it stops data syncing but leaves the active WAC fully operational, so VRRP has no reason to trigger a failover.

Memory tip: Ask yourself, "Is the active WAC still able to forward traffic?" If yes (like in C, where only the sync channel broke), no switch occurs. If no - due to a dead device (A), a dead uplink (B), or a dead downlink interface (D) - the switch fires. The HSB channel is "behind the scenes" bookkeeping, not a traffic path.

No community discussion yet for this question.