You have a failover cluster named Cluster1 with nodes Node1, Node2, and Node3, all configured as File Servers. A File Server for general use cluster role named HAFS is configured, with Node1 as the…

When you select "Move" and then "Best Possible Node" for a clustered role like HAFS, the Failover Cluster Manager performs an internal assessment of all available nodes (Node2 and Node3, since Node1 is the current owner). This assessment considers factors such as current node load, available resources, and potentially anti-affinity rules, to determine which node is currently best suited to host the role. It is entirely plausible and often the outcome that Node3 would be chosen as the "Best Possible Node" if Node2 has higher load or other factors make Node3 more optimal at that moment.

The "Best Possible Node" option does not guarantee a specific target node but evaluates all available nodes in the cluster based on various metrics to find the most suitable one for the clustered role at that moment.