Question 400
A server operations team encounters the following situation: An application cluster fails back immediately after a transient node recovery, causing repeated ownership oscillations during network instability. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Aggressive automatic failback can reduce service stability. It builds validation into the affected workflow and supports the expected recovery result: Repeated short outages do not produce unnecessary role flapping.
Incorrect Answers
This control addresses a different scenario: A load balancer blindly distributes HTTP traffic to a dead backend because no application health check has been defined. That event's root mechanism was round-robin scheduling does not substitute for backend health evaluation. The described incident instead arises from: Aggressive automatic failback can reduce service stability.
This control addresses a different scenario: A two-node active-passive database cluster uses an identical heartbeat path and client uplink; one switch fault isolates both without reliable failover. That event's root mechanism was shared network dependencies can prevent reliable cluster coordination during a failure. The described incident instead arises from: Aggressive automatic failback can reduce service stability.
This control addresses a different scenario: A two-node cluster has no quorum witness and both isolated hosts attempt ownership of a shared writable volume after heartbeat loss. That event's root mechanism was heartbeat loss without split-brain controls can create conflicting cluster owners. The described incident instead arises from: Aggressive automatic failback can reduce service stability.