HOTSPOT (Drag and Drop is not supported)You have a failover cluster named Cluster1 that contains the nodes shown in the following table.A File Server for general use cluster role named HAFS is configured as shown in the General exhibit. (Click the General tab.)The Advanced Policies settings for HAFS are configured as 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:
Answer(s): A
Box 1: YesHAFS will move from Node1 to Node3 if we test failover for the cluster.Note: Test failover.Test failover of the clustered resource to validate cluster functionality.Take the following steps:1. Connect to one of the SQL Server cluster nodes by using RDP.2. Open Failover Cluster Manager. Select Roles. Notice which node owns the SQL Server FCI role.3. Right-click the SQL Server FCI role.4. Select Move, and then select Best Possible Node.5. Failover Cluster Manager shows the role, and its resources go offline. The resources then move and come back online in the other node.Box 2: YesNode1 is the preferred owner.Box 3: NoNode2 is not a possible owner of the cluster.
https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/failover-cluster- instance-vnn-azure-load-balancer-configure
You have two Azure virtual machines that run Windows Server.You plan to create a failover cluster that will host the virtual machines.You need to configure an Azure Storage account that will be used by the cluster as a cloud witness. The solution must maximize resiliency.Which type of redundancy should you configure for the storage account?
Answer(s): C
For Replication, you can select Locally-redundant storage (LRS) or Zone-redundant storage (ZRS) as applicable. ZRS offers more redundancy.
https://docs.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness
DRAG DROP (Drag and Drop is not supported)Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains a failover cluster named Cluster1.You need to configure Cluster-Aware Updating (CAU) on the cluster by using Windows Admin Center (WAC).Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Select and Place:
Step 1: Enable CredSSPSome tasks that require CredSSP to be enabled include:Create Cluster wizard workflowActive Directory queries or updatesSQL Server queries or updatesLocating accounts or computers on a different domain or non-domain joined environmentThe Credential Security Support Provider protocol (CredSSP) is a Security Support Provider that is implemented by using the Security Support Provider Interface (SSPI). CredSSP lets an application delegate the user's credentials from the client to the target server for remote authentication.Step 2: Add Cluster1 to WACAdd the failover cluster to Windows Admin CenterStep 3: Add the Cluster-Aware Updating role.Enabling self-updating mode.To enable the self-updating mode, you must add the Cluster-Aware Updating clustered role to the failover cluster.Incorrect:* Failover clusters do not support gMSAs. However, services that run on top of the Cluster service can use a gMSA or a sMSA if they are a Windows service, an App pool, a scheduled task, or natively support gMSA or sMSA.* The Windows Admin Center gateway, when published to DNS and given access through corresponding corporate firewalls, lets you securely connect to, and manage, your servers from anywhere with Microsoft Edge or Google Chrome.
https://docs.microsoft.com/en-us/azure-stack/hci/manage/troubleshoot-credssp https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/manage-failover-clusters https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-aware-updating
You have a three-node failover cluster.You need to run pre-scripts and post-scripts when Cluster-Aware Updating (CAU) runs. The solution must minimize administrative effort.What should you use?
Answer(s): B
Cluster-Aware Updating advanced options and updating run profiles.You can set the PreUpdateScript or PostUpdateScript the option.
https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-aware-updating-options
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.)Server1 shuts down unexpectedly.You need to ensure that when you start Server1, App1 continues to run on Server2.Solution: You pause the Server1 node in Cluster1 and then start Server1.Does this meet the goal?
Instead, from the Failover settings, you select Prevent failback Note: The Prevent failback setting will prevent the cluster failing back to Server1.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
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.