MD-102 Prepare infrastructure for devices Practice Question
Your organization is migrating from on-premises Active Directory to Microsoft Entra ID. You plan to use Windows Autopilot for new devices. Which prerequisite must be met for Autopilot to work with Entra ID?
⚠ Common exam trap
Watch out — candidates often assume Autopilot requires an on-premises domain join (option B) because they confuse Autopilot with traditional imaging or hybrid Microsoft Entra ID join scenarios, but Autopilot's core value is cloud-native, domain-join-free provisioning.
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
✓
Devices must be registered in Autopilot using hardware hash
Windows Autopilot requires that each device be registered in the Autopilot service using its unique hardware hash (also known as a hardware ID). This hash is collected from the device's firmware and uploaded to the Autopilot deployment service, which then associates the device with the target tenant. Without this registration, Autopilot cannot identify the device during the out-of-box experience (OOBE) and cannot automatically enroll it into Microsoft Entra ID.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Devices must be registered in Autopilot using hardware hash
Why this is correct
Autopilot requires each device's hardware hash uploaded to the Autopilot device store, creating the Autopilot device identity that binds hardware to a Microsoft Entra ID tenant. Without this registration, the device cannot receive an Autopilot profile during OOBE.
- ✗
Devices must be domain-joined to on-premises AD
Why it's wrong here
Autopilot devices join Microsoft Entra ID or stay hybrid-joined; on-premises domain join is not required and contradicts the migration scenario. It is tempting because hybrid Entra join does involve AD, but that is an optional coexistence state, not a prerequisite for cloud-native Autopilot deployment.
- ✗
An Microsoft Entra ID P2 license must be assigned
Why it's wrong here
P1 is sufficient for Autopilot.
- ✗
Configuration Manager must be deployed for OS imaging
Why it's wrong here
Autopilot is a cloud-native provisioning service that needs no Configuration Manager; Intune alone delivers the Autopilot profile and enrolment. It is tempting because ConfigMgr co-management handles existing imaging workflows, but that is the on-premises MDT-style path Autopilot replaces, not a prerequisite.
Go deeper
Related to this question
Learn chapter
Implementing Windows Autopilot
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
Microsoft Entra ID
Microsoft Entra ID is a cloud-based identity and access management service that lets employees sign in and access resources both inside and outside of your organization.
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.