You have a failover cluster named Cluster1 that hosts an application named App1. The General tab in App1 Properties is shown in the General exhibit. The Failover tab in App1 Properties is shown in…

Question

Options

• AYes
• BNo
• C
• D

• A
  79% (50)
• B
  6% (4)
• C
  3% (2)
• D
  11% (7)

Explanation

In Windows Server Failover Clustering, when a clustered resource (App1) fails over from Server1 to Server2 due to an unexpected shutdown, the cluster may automatically move the application back to Server1 once it comes back online. This automatic return is called 'fallback' (or 'failback').

The 'Prevent fallback' option in the Failover tab settings disables this automatic migration back to the original node. When 'Prevent fallback' is selected, App1 will remain running on Server2 even after Server1 is restarted and rejoins the cluster. The resource will only move back to Server1 through manual administrator intervention.

Since the goal is to ensure App1 continues running on Server2 when Server1 comes back online, selecting 'Prevent fallback' directly achieves this objective. Without this setting, the cluster could automatically migrate App1 back to Server1 based on the preferred owner configuration, potentially causing another brief service interruption.

Therefore, the answer is Yes - selecting 'Prevent fallback' meets the goal.

No community discussion yet for this question.