Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.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. (Click the General tab.)The Failover tab in App1 Properties is shown in the Failover exhibit. (Click the Failover tab.)Server2 shuts down unexpectedly.You need to ensure that when you start Server2, App1 continues to run on Server2.Solution: From the General settings, you increase the priority of Server2 in the Preferred Owners list.Does this meet the goal?
Answer(s): B
Solution: From the Failover settings, you select Prevent failback.The Prevent failback setting will prevent the cluster failing back to Server2.Note: Preventing failback.A third potential setting is used after a resource's cluster node comes back online after a failover. Under the Failover tab is the Failback setting with the default setting "prevent failback." When failback is configured, the virtual machine will return back to its original host when that host is again available. If you want virtual machines to return to your known configuration after a host problem, this can be a good thing.
https://www.computerweekly.com/tip/Configuring-cluster-failover-settings-for-Hyper-V-virtual- machines
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.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. (Click the General tab.)The Failover tab in App1 Properties is shown in the Failover exhibit. (Click the Failover tab.)Server2 shuts down unexpectedly.You need to ensure that when you start Server2, App1 continues to run on Server2.Solution: From the Failover settings, you select Prevent failback.Does this meet the goal?
Answer(s): A
The Prevent failback setting will prevent the cluster failing back to Server2.Note: Preventing failback.A third potential setting is used after a resource's cluster node comes back online after a failover. Under the Failover tab is the Failback setting with the default setting "prevent failback." When failback is configured, the virtual machine will return back to its original host when that host is again available. If you want virtual machines to return to your known configuration after a host problem, this can be a good thing.
HOTSPOT (Drag and Drop is not supported)You have an on-premises Active Directory Domain Services (AD DS) domain that contains the resources shown in the following table.The domain contains the domain controllers shown in the following table.You configure a site link between Site1 and Site2 and set the replication interval to 20 minutes.At 10:00 AM, connectivity between Site1 and Site2 fails.Administrators perform the actions shown in the following table.At 10:30 AM, connectivity between Site1 and Site2 is restored.For each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Box 1: NoNo - At 11.30 AM, User1 and User3 are members of Group1.User1 is removed from Group1 at 10.07.This change will be replicated before 11.30 AM.Box 2: NoNo - At 11.30 AM, the phone number of User2 is 333-333.At 10.11: Change the phone of User2 to 222-222.At 10.12: Change the phone of User2 to 333-333.At 10.25: Change the phone of User2 to 444-444.The last change will be replicated before 11.30 AM.Box 3: YesYes- At 11.30 AM, User3 is deleted.At 10.05: Move User3 to OU1.At 10.20. Delete OU1.User3 will be deleted when OU1 is deleted.
HOTSPOT (Drag and Drop is not supported)You have a Windows Server failover cluster named Cluster1 that has a cloud witness and the nodes shown in the following table.Cluster1 has the roles shown in the following table.Cluster1 has the following configuration.For each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Box 1: YesWe see: Site1 {Node1, Node2} and Site1 {Node3, Node4}Yes, Node3 and Node4 are in the same site.Note: Use Get-ClusterFaultDomain to see the current fault domain topology. This lists all nodes in the cluster, plus any chassis, racks, or sites you have created.Box 2: NoNo, Node2 and Node3 are in different sites.Box 3: YesNote: A failover cluster is a group of independent computers that work together to increase the availability and scalability of clustered roles (formerly called clustered applications and services). The clustered servers (called nodes) are connected by physical cables and by software. If one or more of the cluster nodes fail, other nodes begin to provide service (a process known as failover). In addition, the clustered roles are proactively monitored to verify that they are working properly. If they are not working, they are restarted or moved to another node.
https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains
HOTSPOT (Drag and Drop is not supported)You have a Windows Server Failover Cluster (WSFQ) that has the following configurations:Name: App1Owner node: Node3Type: Generic ApplicationThe General settings for App1 are shown in the General exhibit. (Click the General tab.)The Failover settings for App1 are shown in the Failover exhibit. (Click the Failover tab.)The Advanced Policies settings for App1 are shown in the Advanced Policies exhibit. (Click the Advanced Policies tab.)For each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Box 1: NoNo - You can move App1 to Node4 manually.In the General settings for App1 we see only Node1 and Node2 listed as Preferred Owners.Note: DescriptionThe Set-ClusterOwnerNode cmdlet specifies which nodes can own a resource in a failover cluster or specifies the order of preference among owner nodes for a clustered role, or resource group. The settings that control the possible or preferred owners affect the way the cluster responds to the failure of a resource or a clustered role.ExampleGet-ClusterResource -Name "Cluster Disk 3" | Set-ClusterOwnerNode -Owners node1,node2 This example sets the possible owners for cluster named Cluster Disk 3 on the local cluster to the nodes named node1 and node2.Box 2: NoNo - If Node3 fails, App1 will fail over to Node2 automatically.In the Advanced Policies settings for App1 we the three Possible Owners: Node2, Node3, and Node4.The cluster would fail over to Node4, the next node.Note: Windows Server, Failover behavior on clusters of three or more nodesSummaryThe movement of a group can be caused by an administrator who manually moves a group or by a node or resource failure. Where the group moves depends on how the move is initiated and whether the Preferred Owner list is set.Four possible scenarios:*-> 1. There's a node or resource failure and the Preferred Owner List is set.2. There's a node or resource failure and the Preferred Owner List isn't set.3. Administrator manually moves group to "Best Possible" and the Preferred Owner List is set.4. Administrator manually moves group to "Best Possible" and the Preferred Owner List isn't set.Scenario 1If a node or resource fails and the Preferred Owner List has been defined, the Cluster Service fails the Group to the next available node in the Node List. The Node List is composed of the Preferred Owners List followed by the remaining nodes arranged by their Node ID. The Node ID is defined when a node is joined to a cluster or if a node is evicted or and re-added.Box 3: NoThe Preferred Owners are Node1 and Node2.The failback will be to one of the Preferred Owners, not to Node3.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/groups-fail-logic-three-more- cluster-node-members
Post your Comments and Discuss Microsoft AZ-801 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-801 content, but please register or login to continue.