In an HA pair, which outcome occurs when neither node is configured to stay primary or stay secondary and a failover happens?

In an HA pair, which outcome occurs when neither node is configured to stay primary or stay secondary and a failover happens?

• A. The system selects a primary automatically based on a built-in algorithm.
• B. The admin must reconfigure after the failover.
• C. The HA pair becomes unavailable.
• D. The primary always stays the same.

Answer: (A)

In an HA pair, when neither node is configured to stay primary or stay secondary, the system relies on an automatic failover mechanism to decide which unit becomes primary. This built-in algorithm examines the nodes’ configured priorities and, if needed, uses a deterministic tie-breaker to select the primary. This means that during a failover, there’s no need for admin reconfiguration—the system automatically assigns the primary to keep services available. The outcome is that the pair remains operational, with one node serving as primary after failover. If both nodes have different priorities, the higher-priority node will become primary; if priorities are equal, the system uses its internal tie-breaker to choose.

In an HA pair, when neither node is configured to stay primary or stay secondary, the system relies on an automatic failover mechanism to decide which unit becomes primary. This built-in algorithm examines the nodes’ configured priorities and, if needed, uses a deterministic tie-breaker to select the primary. This means that during a failover, there’s no need for admin reconfiguration—the system automatically assigns the primary to keep services available. The outcome is that the pair remains operational, with one node serving as primary after failover. If both nodes have different priorities, the higher-priority node will become primary; if priorities are equal, the system uses its internal tie-breaker to choose.