MD-102 Prepare infrastructure for devices Practice Question
Your organization plans to deploy Windows Autopilot for new devices. You need to ensure that the hardware hashes are uploaded to Microsoft Intune before the devices are shipped to users. What is the recommended approach?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Obtain the hardware hash from the device manufacturer or reseller.
The hardware hash can be obtained from the device manufacturer or reseller (OEM) before the device is shipped. This is the recommended approach for new devices as it allows the hardware hash to be uploaded to Intune without needing to power on the device. Option A is wrong because adding the device to Microsoft Entra ID does not upload the hardware hash. Option C is wrong because Configuration Manager can collect hashes but requires the device to be on the network and is typically used for existing devices. Option D is wrong because running a PowerShell script on each device requires the device to be powered on and manually executed, which is less efficient for new devices.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add the device to Microsoft Entra ID before shipping.
Why it's wrong here
Adding a device to Microsoft Entra ID registers an identity object and does not upload a hardware hash, so Autopilot deployment profiles cannot target it. It is tempting because Entra ID join is required for Autopilot, and would be correct when assigning the device to a user for conditional access.
- ✓
Obtain the hardware hash from the device manufacturer or reseller.
Why this is correct
Capturing the hardware hash at the manufacturer or reseller lets it be uploaded to Microsoft Intune before shipping, so devices enrol automatically on first boot. Manual hash collection after delivery would delay provisioning and break the pre-shipment requirement.
- ✗
Use Microsoft Configuration Manager to collect the hardware hash.
Why it's wrong here
Configuration Manager collects hardware hashes only for devices it already manages, requiring an existing OS and client agent before shipping. It is tempting because co-management integrates with Intune, and would be correct for existing managed devices being re-provisioned via Autopilot.
- ✗
Run a PowerShell script on each device to capture the hardware hash.
Why it's wrong here
Running PowerShell on each device requires booting into an existing OS and manual per-device execution, which is impractical before shipping at scale. It is tempting because Get-WindowsAutoPilotInfo is the documented capture method, and would be correct for registering a single existing device.
Go deeper
Related to this question
Learn chapter
Managing Microsoft 365 Apps and Office Updates
Key term
Windows Autopilot
Windows Autopilot is a cloud-based deployment technology that automates the setup and configuration of new Windows devices, reducing the need for IT staff to manually image or touch each machine.
Key term
Autopilot
Autopilot is a Microsoft cloud-based deployment technology that automates the setup and configuration of new Windows devices, reducing manual IT effort and enabling users to be productive from the first boot.
About these practice questions
One of 556 original MD-102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MD-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MD-102 exam.