A failover mechanism is a fundamental component of a high-availability (HA) cluster. Its primary function is to automatically detect the failure of a primary node and redirect its workload to a pre-configured standby or secondary node. This process ensures that the service or application experiences minimal to no downtime, maintaining operational continuity. The scenario described, where an application remains available after a node failure, is the direct result of a successful, automated failover operation.

A. Load balancing across all nodes in the cluster.

Load balancing distributes incoming requests among healthy nodes but does not manage the stateful transfer of a running workload from a failed node.

B. Manual intervention by the system administrator to restart services.

This contradicts the principle of automated high availability. Manual intervention would result in service interruption until the administrator takes action.

D. Data replication between nodes to ensure data integrity.

Data replication is a critical prerequisite for failover, ensuring the standby node has current data, but it is not the mechanism that executes the switchover.

1. Official Vendor Documentation: NVIDIA Cumulus Linux User Guide, Chapter: High Availability and Redundancy. This chapter details mechanisms like Virtual Router Redundancy (VRR) and Multi-Chassis Link Aggregation (MLAG), which are failover technologies designed to provide network service continuity by switching to redundant hardware in the event of a failure. This exemplifies the principle of automated failover in a production environment.

2. University Courseware: Patterson, D. A., & Hennessy, J. L. (2017). Computer Organization and Design RISC-V Edition: The Hardware Software Interface. Morgan Kaufmann. In Chapter 6, "Parallel Processors from Client to Cloud," the text discusses dependability via redundancy, explaining that a key technique for high availability is to use redundant nodes and "when one fails, the other can take over" (Section 6.8, p. 552). This process is defined as failover.

3. Peer-reviewed Academic Publication: A. Avizienis, J.-C. Laprie, B. Randell, and C. Landwehr, "Basic Concepts and Taxonomy of Dependable and Secure Computing," IEEE Transactions on Dependable and Secure Computing, vol. 1, no. 1, pp. 11-33, Jan.-Mar. 2004, doi: 10.1109/TDSC.2004.2. The paper defines fault tolerance as the ability to provide service continuity despite faults, which is achieved through error processing and fault treatment, the automated form of which is a failover mechanism.