MD-102 Deploy Windows client Practice Test 2 — 15 Questions

Question 1

You are designing a Windows Autopilot deployment for a global organization. Devices are purchased from multiple OEMs and shipped directly to users. Some users report that their devices do not register in Autopilot automatically. You confirm the devices have Windows 11 Pro preinstalled and meet hardware requirements. What is the most likely reason for the registration failure, and what should you do to resolve it?

Accepted Answer

The devices are not registered in Autopilot by the OEM; collect the hardware hash using a script. The most likely reason is that the OEM did not register the devices in Windows Autopilot by uploading their hardware hashes to the Microsoft Partner Center. Without this registration, the devices will not be recognized during OOBE and will not automatically receive the Autopilot deployment profile. To resolve this, you must collect the hardware hash from each device using a PowerShell script (e.g., Get-WindowsAutopilotInfo.ps1) and manually upload it to Intune or the Partner Center.

Answer

The devices have a TPM chip that is not compliant with Autopilot requirements

Answer

The Autopilot deployment profile is assigned to a dynamic device group that excludes these devices

Answer

The devices are not connected to the internet during OOBE

Question 2

A company uses Configuration Manager to deploy Windows 11. During the deployment, the task sequence fails at the 'Apply Operating System' step. The error log shows 'Failed to find a valid operating system image package'. You verify that the operating system image package exists and is distributed to the distribution point. What is the most likely cause?

Accepted Answer

The operating system image package is not enabled for use with task sequences. Option C is correct because when an operating system image package exists and is distributed to distribution points but the task sequence fails with 'Failed to find a valid operating system image package', the most common cause is that the image package is not enabled for use with task sequences. In Configuration Manager, each OS image package has a property 'Enable this operating system image for use in task sequences' that must be checked; if unchecked, the task sequence engine cannot reference the package during the Apply Operating System step, even though the package is present and distributed.

Answer

The client computer does not have enough disk space

Answer

The task sequence is not associated with the correct boot image

Answer

The distribution point is not configured to support PXE boot

Question 3

A company is deploying Windows 11 using a task sequence in Configuration Manager. They encounter an issue where the task sequence fails on devices that have BitLocker enabled. Which TWO actions should you take to ensure the task sequence completes successfully on BitLocker-enabled devices?

Accepted Answer

Add a 'Suspend BitLocker' step before the 'Format and Partition Disk' step. Option C is correct because suspending BitLocker before the 'Format and Partition Disk' step prevents the task sequence from failing due to BitLocker-protected volumes. When BitLocker is active, the disk cannot be repartitioned or formatted without first suspending protection, as the Trusted Platform Module (TPM) validation and encryption keys would be invalidated. Option D is correct because the boot image must include the BitLocker optional component in WinPE to enable BitLocker-related operations (e.g., suspend, resume, preprovision) during the task sequence execution.

Answer

Add a 'Preprovision BitLocker' step before the 'Apply Operating System' step

Answer

Ensure the boot image includes the Microsoft BitLocker Administration and Monitoring (MBAM) optional component

Answer

Disable Secure Boot in the device BIOS

Question 4

You are configuring Windows Autopilot for a customer who has a hybrid Azure AD join deployment. The devices are self-deploying using a self-deploying profile. Which THREE prerequisites must be met for the self-deploying mode to work?

Accepted Answer

The device must be registered in Windows Autopilot. Option A is correct because a device must be registered in Windows Autopilot to associate it with a self-deploying profile. Registration is done by uploading the device's hardware hash to the Autopilot service, which then links the device to the profile and enables automatic provisioning without user interaction.

Answer

The local administrator account must be enabled

Answer

The user must be assigned a Windows Autopilot license

Question 5

You are a Microsoft 365 Endpoint Administrator for a mid-sized company with 5,000 Windows 10 devices. The company is planning to migrate to Windows 11. You are tasked with deploying Windows 11 using a phased approach with Windows Autopilot. You have configured an Autopilot deployment profile for self-deploying mode targeting all Windows 10 devices in a dynamic device group. However, during the first wave of deployment, you notice that devices that have been upgraded to Windows 11 via an in-place upgrade are not automatically transitioning to the Autopilot experience. Instead, they boot directly to the existing Windows 10 desktop without any Autopilot enrollment. You verify that the devices are registered in Autopilot and that the deployment profile is assigned correctly. What is the most likely cause of this issue?

Accepted Answer

The devices have not been reset to OOBE state after the in-place upgrade. Windows Autopilot requires the device to be in an Out-of-Box Experience (OOBE) state to trigger the enrollment process. An in-place upgrade to Windows 11 preserves the existing user state and settings, so the device boots directly to the desktop without entering OOBE. Even though the device is registered in Autopilot and the profile is assigned, the Autopilot experience only initiates when the device is reset to OOBE (e.g., via a Windows reset or a fresh start). Therefore, the most likely cause is that the devices have not been reset to OOBE state after the in-place upgrade.

Answer

The Autopilot profile has a pre-provisioning policy that blocks self-deploying mode

Answer

The Autopilot profile is configured for user-driven mode instead of self-deploying mode

Answer

The devices are not connected to the internet during the first boot after upgrade

Question 6

A company is using Microsoft Deployment Toolkit (MDT) to deploy Windows 11 to 200 new laptops. The deployment includes applications such as Microsoft 365 Apps for enterprise and a line-of-business (LOB) application. The LOB application requires a specific registry key to be set before installation. You have added a 'Set Registry' step in the task sequence before the application installation step. During a test deployment, the LOB application fails to install. The MDT logs show that the registry key is set correctly, but the application installer still fails. You suspect the application requires a reboot after setting the registry key. The task sequence does not have a reboot step after the registry change. Which step should you add to the task sequence?

Accepted Answer

Add a 'Restart Computer' step immediately after the 'Set Registry' step. Option C is correct because the LOB application requires a reboot after the registry key is set to make the change effective. In MDT, a 'Restart Computer' step forces a system restart, ensuring the registry modification is recognized by the application installer. Without this reboot, the installer may read stale registry data and fail, even though the key is correctly written.

Answer

Add a 'Wait' step for 60 seconds

Answer

Add a 'Set Task Sequence Variable' step to set a reboot variable

Answer

Add a 'Run Command Line' step to run gpupdate /force

Question 7

A company manages 500 Windows 10 devices using Microsoft Intune. They plan to upgrade to Windows 11. The IT team wants to ensure that only devices meeting the Windows 11 hardware requirements are allowed to upgrade. They need to block the upgrade on devices that do not meet the requirements, and provide a clear error message to users. What should the IT team configure?

Accepted Answer

Configure a Windows 11 readiness policy in Intune and assign it to all devices.. Option A is correct because a Windows 11 readiness policy in Intune is specifically designed to evaluate device hardware compatibility against Windows 11 requirements and block the upgrade on non-compliant devices while displaying a custom error message to users. This policy uses the Windows Health Monitoring and the TPM 2.0 attestation checks to enforce the hardware requirements before the upgrade can proceed.

Answer

Configure a feature update policy for Windows 10 and Windows 11 in Intune.

Answer

Create a compliance policy with Windows 11 requirements and assign it to all devices.

Answer

Use a device configuration profile to set the 'TargetReleaseVersion' policy for Windows 11.

Question 8

You are deploying a custom Windows 10 image to 200 new laptops using MDT. The deployment fails on several devices at the 'Apply Operating System' step with error 0x80070070. The laptops have 60 GB SSDs and 4 GB RAM. What is the most likely cause?

Accepted Answer

The custom image is too large for the 60 GB SSD.. Error 0x80070070 translates to 'insufficient disk space' (ERROR_DISK_FULL). During the 'Apply Operating System' step, MDT decompresses the custom WIM image and applies it to the local disk. With a 60 GB SSD, if the custom image (including drivers, updates, and applications) exceeds the available free space after partitioning, the deployment fails. This is the most direct cause given the error code and hardware constraints.

Answer

The laptops have insufficient RAM (4 GB) to run the deployment.

Answer

The deployment share is not accessible over the network.

Answer

The custom image is missing critical drivers.

Question 9

A company uses Windows Autopilot for user-driven deployments. They want to ensure that during the out-of-box experience (OOBE), users are required to sign in with their Azure AD credentials and the device is automatically enrolled in Intune. Which Autopilot deployment profile setting should be configured?

Accepted Answer

Set 'Deployment mode' to 'User-Driven' and 'Join to Azure AD as' to 'Azure AD joined'.. Option D is correct because the scenario requires a user-driven deployment where the user signs in with Azure AD credentials during OOBE, and the device is automatically enrolled in Intune. Setting 'Deployment mode' to 'User-Driven' ensures the user authenticates during OOBE, and 'Join to Azure AD as' to 'Azure AD joined' makes the device Azure AD-joined, which triggers automatic Intune enrollment via the MDM enrollment authority configured in Azure AD.

Answer

Set 'Deployment mode' to 'Self-Deploying' and 'Join to Azure AD as' to 'Azure AD joined'.

Answer

Set 'Deployment mode' to 'User-Driven' and 'Join to Azure AD as' to 'Hybrid Azure AD joined'.

Answer

Set 'Deployment mode' to 'White Glove' and 'Join to Azure AD as' to 'Azure AD joined'.

Question 10

Arrange the steps to deploy Windows 10 using Microsoft Deployment Toolkit (MDT) in the correct order.

Question 11

Arrange the steps to perform a Windows 10 feature update using Windows Update for Business in Intune.

Question 12

Arrange the steps to configure Conditional Access for Microsoft 365 in Azure AD.

Question 13

Match each Microsoft 365 Defender feature to its description.

Question 14

Match each Co-management workload to its management authority when co-managed.

Question 15

Match each PowerShell cmdlet to its function in Microsoft 365 management.