Configuring Security Patch for Active-Passive Failover SQL Cluster | CompTIA Server+ Exam

Applying Security Patch to Active-Passive Failover SQL Cluster

Prev Question Next Question

Question

A server technician is applying a security patch to an active-passive failover SQL cluster.

However, the cluster must continue to service clients during the process with limited outages.

Given this scenario, which of the following should the technician do to adhere to these maintenance requirements?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D.

In an active-passive failover SQL cluster, one node is active and actively servicing clients, while the other node is passive and standing by in case of a failure. When performing maintenance tasks, such as applying a security patch, it is important to ensure that the cluster continues to service clients with minimal outages.

Option A suggests failing over back to the original active node once the patching is complete. This approach is not ideal because it would result in a brief outage when failing back to the original node. Additionally, it would be necessary to fail over to the passive node again when patching that node, resulting in additional outages.

Option B suggests keeping services failed over to the passive node once patching is complete. This approach is more feasible than option A because it eliminates the need for a failover back to the original active node. However, it would require patching the active node while clients are still connected to it, which could result in service disruptions.

Option C suggests moving services to the active node and repeating the process for the passive node. This approach is more feasible than option B because it eliminates the need for patching an active node while clients are still connected to it. However, it would require additional failovers, which could result in additional outages.

Option D suggests patching the passive node, failing over to it, and then patching the other node. This approach is the most feasible because it eliminates the need for patching an active node while clients are still connected to it and eliminates the need for additional failovers. The downside is that it requires failing over twice, which could result in additional outages.

Overall, the best approach would be option D: patch the passive node, fail over, and patch the other node. This approach would minimize the impact on clients and ensure that the cluster remains operational throughout the maintenance process.