You have an Azure subscription that contains the virtual machines shown in the following table.You plan to use Azure Site Recovery to replicate supported virtual machines to a secondary Azure region.Which virtual machines can be replicated by using Azure Site Recovery?
Answer(s): E
* VM1, VM2 - Yes* VM3 - YesYou can replicate a Trusted Launch VM with Windows Server 2025 Datacenter to another Azure region using Azure Site Recovery, as this scenario is fully supported for Trusted Launch VMs across all Azure regions where ASR is available. You simply enable replication for the VM through the Azure portal, selecting your desired target region to configure global disaster recovery.Note: Azure Site Recovery support for Azure trusted launch virtual machines Trusted launch protects against advanced and persistent attack techniques. It is composed of several coordinated infrastructure technologies that can be enabled independently. Each technology provides another layer of defense against sophisticated threats.Support matrixFind the support matrix for Azure trusted launch virtual machines with Azure Site Recovery:* Operating system: Support for Windows and Linux OS is generally available* Region: Available in all Azure Site Recovery supported regions.* Etc.* VM4 - YesAzure Site Recovery (ASR) supports replicating confidential VMs with Windows Server 2025 Datacenter to another Azure region for disaster recovery.
https://learn.microsoft.com/en-us/azure/site-recovery/concepts-trusted-vm https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-support-matrix
You have an on-premises, two-node, hyperconverged Windows Server Failover Cluster (WSFC) named Cluster1.You have an Azure subscription.You need to configure a cloud witness for Cluster1.Which type of Azure Storage should you use?
Answer(s): D
Quorum witness typesFailover Clustering supports three types of Quorum Witnesses:*-> Cloud Witness - Blob storage in Azure accessible by all nodes of the cluster. It maintains clustering information in a witness.log file, but doesn't store a copy of the cluster database.* File Share Witness A SMB file share that is configured on a file server running Windows Server. It maintains clustering information in a witness.log file, but doesn't store a copy of the cluster database.* Disk Witness - A small clustered disk that is in the Cluster Available Storage group. This disk is highly available and can failover between nodes. It contains a copy of the cluster database. A Disk Witness isn't supported with Storage Spaces Direct.
https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/quorum
You have a server named Server1 that runs Windows Server 2022 and is part of a three-node failover cluster.You need to upgrade Server1 to Windows Server 2025. The solution must minimize downtime for the cluster.What should you do first?
Answer(s): C
For a graceful, rolling, in-place upgrade from Windows Server 2022 to Windows Server 2025 in a failover cluster, you must pause and drain the server node by placing it into maintenance mode to migrate its active clustered roles to other nodes before performing the operating system upgrade. You can perform this action using Failover Cluster Manager by right-clicking the server node and selecting Pause > Drain Roles, or by using the Suspend-ClusterNode -Name <NodeName> -Drain PowerShell cmdlet.Steps for a Rolling OS Upgrade1. Prepare the cluster: Ensure your cluster is healthy and all nodes are running the latest updates.*-> 2. Pause and Drain a Node: In Failover Cluster Manager, right-click the node you want to upgrade and select Pause > Drain Roles. Alternatively, use the PowerShell command: Suspend-ClusterNode -Name <NodeName> -Drain.3. Verify Role Migration4. Perform the Upgrade: Mount the Windows Server 2025 ISO image to the node and run the setup.exe file to begin the in-place upgrade.5. Resume the Node: Once the upgrade is complete and the node has rebooted, you can resume the node and allow roles to fail back to it.6. Repeat for Other Nodes: Repeat the process for each remaining node in the cluster, ensuring each upgrade is successful before moving on to the next.7. Post-Upgrade Tasks: After all nodes are upgraded, update the cluster functional level and, if using Storage Spaces Direct, the storage pool version and VM configuration versions.
https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade
DRAG DROP (Drag and Drop is not supported)Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains servers that run Windows Server 2022.You have a Storage Spaces Direct cluster named SSCluster1 that contains two physical nodes named Node1 and Node2. Node1 and Node2 host highly available virtual machines.You plan to perform an in-place upgrade to Windows Server 2025 on Node1.You need to ensure that the virtual machines remain running during the upgrade.Which four actions should you perform in sequence on Node1? 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:
Answer(s): A
To perform an in-place upgrade of a Storage Spaces Direct (S2D) cluster node, you must first drain the node using Suspend-ClusterNode -Drain, then place it into storage maintenance mode with Enable- StorageMaintenanceMode, perform the Windows Server upgrade, and finally, remove it from maintenance mode using Disable-StorageMaintenanceMode and resume the node with Resume-ClusterNode.Step 1: Run Suspend-Clusternode -Drain and the place the node in storage maintenance mode.Here is a step-by-step process for performing a rolling in-place OS upgrade for a Storage Spaces Direct cluster:1. Prepare the clusterEnsure the other nodes have enough resources to handle the workloads from the node being upgraded.Download the Windows Server ISO for the upgrade.Ensure the Cluster Witness is accessible for two-node clusters.2. Pause and Drain the NodeOpen an elevated PowerShell session on the node you intend to upgrade. Run the following command to drain the node, which migrates all VMs and roles to other active nodes in the cluster:Suspend-ClusterNode -Drain3. Enable Storage Maintenance Mode:Place the node in storage maintenance modeStep 2: Upgrade to Windows Server 20254. Perform the In-Place Upgrade:Run the setup.exe from your downloaded Windows Server ISO and select the option to keep your personal files and apps.The server will restart, and the cluster service will start automatically once the upgrade is complete.Step 3: Remove from storage maintenance mode.5. Resume and Verify:Disable storage maintenance mode on the upgraded node:Get-StorageFaultDomain -type StorageScaleUnit | Where-Object {$_.FriendlyName -eq "<NodeName>"} | Disable-StorageMaintenanceModeStep 4: Run Resume-ClusterNodeResume the cluster node.Resume-ClusterNode
https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/upgrade-storage-spaces-direct
HOTSPOT (Drag and Drop is not supported)Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains the servers shown in the following table.The Failover Clustering tools are NOT installed on the servers.You plan to enable Cluster-Aware Updating (CAU).On which servers should you install the Failover Clustering tools to implement CAU in self-updating mode, and on which servers should you install the Failover Clustering tools to implement remote-updating made? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Node1 and Node2 only.Self-updating modeTo enable the self-updating mode for Cluster-Aware Updating (CAU), you must install the Failover Clustering Tools, which include the CAU tools, on each cluster node. This installation adds the necessary components for CAU to function autonomously as a clustered role on the failover cluster itself.Note: The following table summarizes the CAU feature installation requirements for the two CAU updating modes.Box 2: Server1 onlyRemote-updating modeIn remote-updating mode, the CAU tools are installed on a separate, remote computer that acts as the Update Coordinator. This remote computer then coordinates the updates for the cluster.
https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-aware-updating-requirements
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.