Free AZ-802 Practice Test Questions and Answers (2026)

Azure Site Recovery replication for Azure-to-Azure scenarios supports standard-security VMs (VM1, VM2) as well

as trusted launch virtual machines running Windows Server, a capability that is generally available and

documented specifically for Azure-to-Azure replication, which covers VM3. Confidential VMs such as VM4,

however, rely on hardware-bound (vTPM/attestation-tied) OS disk encryption keys that are not part of Azure

Site Recovery's supported replication scenarios, so a VM configured with the Confidential security type cannot

currently be replicated using Azure Site Recovery. The Windows Server 2025 Datacenter: Azure Edition

operating system itself is fully supported and is not the limiting factor for any of the four VMs; the security type

of VM4 is what excludes it. If VM4 must still be protected for disaster recovery, an alternative such as Azure

Backup for VM-level snapshots, or a guest-level replication tool that operates independently of the confidential

computing attestation boundary, would need to be considered instead of Azure Site Recovery.

The objective is to ensure App1 remains on Server2 when Server1 restarts. In the General tab, the Preferred Owners list determines the priority of nodes for hosting the role. However, both Server1 and Server2 are currently unchecked, meaning neither is an active preferred owner. Because they are unchecked, the Up/Down reordering controls are disabled, making it impossible to move Server2 up. Even if you could reorder them, simply moving an unchecked node up does not make it a preferred owner or explicitly prevent failback. To meet the goal, you would need to either check Server2 to make it the primary preferred owner or explicitly configure the failover settings to "Prevent failback."

A: This is incorrect because you cannot reorder unchecked nodes, and reordering them without selecting them as preferred owners does not influence failback behavior to meet the goal.

1. Microsoft Corporation. (2023). "Configure failover and failback settings for a clustered role." Microsoft Learn. Section: Preferred owners and failback.

2. Microsoft Official Courseware (MOC) AZ-800/AZ-802: Administering Windows Server Hybrid Core Infrastructure. Module: Failover Clustering.

To configure Hyper-V Replica between hosts that are not part of the same Active Directory domain (or trusting domains), you must use Certificate-based authentication. Hyper-V Replica supports two primary authentication mechanisms: Kerberos (which transmits data over HTTP) and Certificate-based authentication (which transmits data securely over HTTPS). Because Server2 is a non-domain joined server in a remote location, Kerberos authentication will fail as it strictly requires a functional Active Directory trust boundary. Therefore, you must deploy and select X.509 certificates on both Server1 and Server2 to establish mutual authentication and encrypt the replication traffic over HTTPS.

A. NTLM: Hyper-V Replica does not support NTLM for replication authentication; it only supports Kerberos or Certificates.

B. Kerberos: Requires both Hyper-V hosts to be members of the same Active Directory domain or domains with a two-way trust, which is not the case here.

C. preshared secret: Hyper-V Replica does not support preshared secrets for authentication; this is typically used for IPsec or VPNs.

1. Microsoft Learn. "Set up Hyper-V Replica". Windows Server Virtualization Documentation. Section: Authentication types.

2. Microsoft Learn. "Deploy Hyper-V Replica using certificates". Windows Server 2022 Documentation.