Correct Answer:

Explanation:
DHCP1: Export-DhcpServer, Remove-DhcpServerInDC. DHCP2: Add-DhcpServerInDC, Import- DhcpServer.
Migrating a DHCP server ' s configuration together with its existing leases and reservations by PowerShell follows an export/unauthorize-then-authorize/import pattern across the two servers. On the source server, DHCP1, Export-DhcpServer captures the existing scopes, options, leases, and reservations into a migration file, which is what allows the existing leases and reservations to actually carry over to the replacement server.
Remove-DhcpServerInDC is then run on DHCP1 to unauthorize it in Active Directory, which is what prevents DHCP1 from continuing to service client requests once DHCP2 is brought online, satisfying that specific migration requirement. On the target server, DHCP2, Add-DhcpServerInDC authorizes the new server in AD DS so it is permitted to lease addresses on the network, and Import-DhcpServer then applies the configuration file exported from DHCP1, causing DHCP2 to hand out the same address ranges as DHCP1 along with the existing leases and reservations that were captured during export. Add-DhcpServerv4Scope and Remove-DhcpServerv4Scope only create or delete an individual scope ' s address range and do not export, import, or preserve any existing lease or reservation data, so neither is part of this migration sequence.
Therefore, DHCP1 requires Export-DhcpServer and Remove-DhcpServerInDC, while DHCP2 requires Add- DhcpServerInDC and Import-DhcpServer.

Correct Answer:

Explanation:
For a hyper-converged Storage Spaces Direct cluster, Microsoft ' s documented per-node in-place upgrade path begins by draining the node of its clustered roles with Suspend-ClusterNode -Drain, which live-migrates the running virtual machines off that node onto the remaining nodes before it pauses, keeping every VM online throughout the step. The node ' s drives are then placed into storage maintenance mode so the clustered storage subsystem stops routing I/O to them, which lets the disks be safely taken offline from the pool ' s perspective while the rest of the cluster continues serving storage requests. With the VMs relocated and the drives quiesced, an in-place upgrade to Windows Server 2025 is performed on the node directly, preserving its existing roles, cluster membership, and configuration rather than requiring a clean install or manual re- provisioning, which is what keeps administrative effort to a minimum compared with evicting and rejoining the node. Finally, storage maintenance mode is disabled and the node is resumed, allowing Storage Spaces Direct to bring its drives back into active service and repair mirror or parity copies before the same four-step sequence is repeated on the next node, one at a time, until the whole cluster is running Windows Server 2025.

Correct Answer: E  🗳️

Explanation: Only visible for Pass4guide members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
On Cluster1: Import the Azure Migrate appliance. In Azure: Create an Azure Migrate project.
APP3 and APP4 run as virtual machines on the on-premises Cluster1 Hyper-V failover cluster, so migrating them to Azure uses the Azure Migrate: Server Migration workflow for Hyper-V. That workflow requires an Azure Migrate project to first be created in Azure, since the project is the container that organizes the migration effort, tracks discovered and assessed machines, and holds the configuration for the subsequent discovery and replication work. On the Cluster1 side, the Azure Migrate appliance -- a purpose-built VM or OVA image supplied by Azure Migrate specifically for Hyper-V environments -- must be imported (deployed) onto the Hyper-V host or cluster, where it discovers the VMs running there and orchestrates their replication into Azure. Configuring an Azure Network Adapter, creating a Point-to-Site VPN connection to Vnet1, installing the Azure File Sync agent, and installing the Windows Server Migration Tools are all unrelated actions that do not perform Hyper-V VM discovery or replication for an Azure Migrate project.
Similarly, creating a premium block blob storage account, a private endpoint, or a VPN gateway in Azure are not the resource that Azure Migrate itself requires to begin a migration project -- an Azure Migrate project is.
Therefore, importing the Azure Migrate appliance onto Cluster1 and creating an Azure Migrate project in Azure are the two required preparatory actions.
Topic 5, Case Study 5: Contoso, Ltd. (New)This is a case study. Case
studies are not timed separately. You can use as much exam time as
you would like to complete each case. However, there may be
additional case studies and sections on this exam. You must manage
your time to ensure that you are able to complete all questions
included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
Overview: Contoso, Ltd. is a manufacturing company that has a main office in Seattle and branch offices in Los Angeles and Montreal.
Existing Environment -- Active Directory Environment: Contoso has an on-premises Active Directory Domain Services (AD DS) domain named contoso.com that syncs with a Microsoft Entra ID tenant. The AD DS domain contains the domain controllers shown in the following table.

Domain controllers
Contoso recently purchased an Azure subscription.
The functional level of the forest is Windows Server 2012 R2. The functional level of the domain is Windows Server 2012. The forest has the Active Directory Recycle Bin enabled.
The contoso.com domain contains the users shown in the following table.

Users
The contoso.com domain has the Group Policy Objects (GPOs) shown in the following table.

Group Policy Objects
The contoso.com domain has the Password Settings Objects (PSOs) shown in the following table.

Password Settings Objects
Server Infrastructure: The contoso.com domain contains servers that run Windows Server 2022 as shown in the following table.

Servers
By using Windows Firewall with Advanced Security, the servers have isolation connection security rules configured as shown in the following table.

Isolation connection security rules
Server4 has no connection security rules.
Server4 Configurations: Server4 has the effective Group Policy settings for user rights as shown in the following table.

Server4 effective user rights
Server4 has the disk configurations shown in the following exhibit.
-- Disk 0 (127.00 GB, Basic, Online): System Reserved (100 MB, NTFS, Healthy System partition); C:
(126.39 GB, NTFS, Healthy Boot/Page File/Crash Dump/Primary partition); a 523 MB Healthy Recovery partition.
-- Disk 1 (127.00 GB, Basic, Online): D: Data (127.00 GB, NTFS, Healthy Primary partition).
-- Disk 2 (127.00 GB, Basic, Online): E: Data (127.00 GB, ReFS, Healthy Primary partition).
-- Disk 3 (127.00 GB, Basic, Online): F: Data (127.00 GB, ReFS, Healthy Primary partition).
Virtualization Infrastructure: The contoso.com domain has the Hyper-V failover clusters shown in the following table.

Server4 disk configuration (Disk Management)

Hyper-V failover clusters

Correct Answer:

Explanation:
Confidential disk encryption is a platform feature available only on confidential VM sizes such as the DCasv5
/DCadsv5/DCesv6 (and equivalent ECasv5/ECesv6) series, so VM1 must be deployed on a DC-series confidential SKU rather than the NC (GPU) or HB (HPC) families. Confidential disk encryption itself binds the encryption key to the VM ' s own vTPM and, by design, protects the operating system disk; the temp disk can optionally be added through a separate confidential temp disk encryption extension, but data disks are not covered by this mechanism and instead rely on guest-level encryption such as BitLocker if extra protection is required. Consequently the disk scope for confidential disk encryption is the operating system disk only, not the OS disk together with data disks. The encryption keys can be customer-managed and held in a managed HSM or Key Vault with purge protection enabled, ensuring the platform itself cannot access the disk contents outside the attested confidential VM boundary, which is the core security guarantee this feature provides over standard Azure Disk Encryption.