MD-102 Deploying Windows 2 — Questions and Answers

Question 1: Which Windows Autopilot deployment mode allows a technician to pre-configure a device before handing it to the end user?

Self-deploying mode
User-driven mode
Pre-provisioning (white glove) mode (Correct answer)
Reset mode

Correct answer: Pre-provisioning (white glove) mode

Pre-provisioning (white glove) mode allows IT staff or partners to complete the Autopilot provisioning process on behalf of the user so the device is fully configured before reaching the end user.

In Windows Autopilot pre-provisioning mode (formerly called white glove), a technician or OEM partner runs through the device provisioning phase, installing apps and applying policies, before shipping the device to the end user. When the user receives it, they only complete the user-specific setup portion. This reduces the time users spend waiting for apps to install on first sign-in and is ideal for complex enterprise deployments.

Question 2: What is the minimum requirement for a device to be eligible for Windows Autopilot deployment?

The device must be domain-joined
The device hardware hash must be registered in Intune or Autopilot (Correct answer)
The device must have Windows 10 Pro or higher installed
The device must have a TPM 2.0 chip

Correct answer: The device hardware hash must be registered in Intune or Autopilot

For Autopilot to recognise and configure a device automatically, its hardware hash must be registered in Microsoft Intune or the Autopilot deployment service.

Windows Autopilot identifies devices by their hardware hash (a unique identifier derived from hardware components). This hash must be uploaded to Intune's Autopilot devices list, either by the OEM, a Microsoft Cloud Solution Provider, or by running a PowerShell script on the device. Once registered, when the device connects to the internet during OOBE, Autopilot retrieves the correct deployment profile and begins automatic configuration.

Question 3: An organisation wants to deploy Windows to new devices without physical media, ensuring Azure AD join and Intune enrollment automatically. Which solution is best?

Windows Deployment Services (WDS)
MDT with PXE boot
Windows Autopilot (Correct answer)
SCCM OSD Task Sequence

Correct answer: Windows Autopilot

Windows Autopilot enables zero-touch deployment where devices are automatically configured, Azure AD-joined, and Intune-enrolled out of the box without physical media or on-premises infrastructure.

Windows Autopilot is Microsoft's cloud-based zero-touch deployment solution. When a registered device goes through OOBE, it automatically downloads and applies an Autopilot profile, joins Azure AD, enrolls in Intune, and installs required apps without IT staff physically touching the device. WDS and MDT require on-premises servers and PXE infrastructure, while SCCM OSD requires a complex task sequence and domain infrastructure.

Question 4: Which tool is used to capture a Windows image (.wim file) for deployment using Microsoft Deployment Toolkit (MDT)?

DISM (Deployment Image Servicing and Management) (Correct answer)
Windows SIM (System Image Manager)
Sysprep
WinPE Boot Media Creator

Correct answer: DISM (Deployment Image Servicing and Management)

DISM is the command-line tool used to capture, service, and apply Windows image files (.wim), making it the primary tool for creating deployment images.

DISM (Deployment Image Servicing and Management) is used to capture a reference Windows installation as a .wim file using the /capture-image command, and to apply images to target devices using /apply-image. It can also add or remove Windows features, drivers, and updates from offline images. Sysprep prepares a system for imaging by removing machine-specific information and must be run before DISM captures the image.

Question 5: During Windows Autopilot self-deploying mode, which authentication type is used since no user credentials are entered?

Azure AD user password
Device certificate with TPM attestation (Correct answer)
FIDO2 security key
Windows Hello for Business PIN

Correct answer: Device certificate with TPM attestation

Autopilot self-deploying mode uses the device TPM chip for attestation and a device certificate to authenticate to Azure AD without requiring user credentials.

In self-deploying mode, Windows Autopilot authenticates the device using the Trusted Platform Module (TPM) for device attestation combined with a device identity certificate. This enables the device to join Azure AD and enroll in Intune completely without user interaction. This mode requires a device with TPM 2.0 that supports device attestation, which is why it cannot be used on devices without a TPM.

Question 6: Which file contains the configuration settings for an unattended Windows installation, allowing administrators to automate responses to setup prompts?

autounattend.xml (Correct answer)
setup.ini
winpeshl.ini
bootstrap.cmd

Correct answer: autounattend.xml

The autounattend.xml file contains pre-defined answers to Windows setup prompts, enabling fully automated unattended installations when placed at the root of installation media.

Windows Setup automatically detects autounattend.xml when placed at the root of the boot media or a removable drive, using it to answer setup prompts without user interaction. This file is created using Windows System Image Manager (Windows SIM), part of the Windows Assessment and Deployment Kit (ADK). It can specify partition layouts, regional settings, product keys, user accounts, and post-installation scripts.

MD-102 Deploying Windows 2

Which Windows Autopilot deployment mode allows a technician to pre-configure a device before handing it to the end user?