Quick Answer
The answer is that devices must be registered in Autopilot using their hardware hash. This prerequisite exists because Windows Autopilot relies on a unique hardware identifier—collected from the device’s firmware—to associate each machine with your Microsoft Entra ID tenant during the out-of-box experience. Without this registration, the Autopilot deployment service cannot recognize the device, so it cannot automatically enroll it into Entra ID or apply the correct deployment profile. On the MD-102 exam, this concept often appears in scenario-based questions about migrating from on-premises Active Directory to cloud-only identity, where a common trap is assuming that Entra ID connectivity alone is sufficient. Remember that the hardware hash is the device’s “birth certificate” for Autopilot—no hash, no automatic enrollment. A useful memory tip: think “Hash to Hash”—the hardware hash must be uploaded to the Autopilot service before the device can hash out its identity with Entra ID.
This MD-102 practice question tests your understanding of prepare infrastructure for devices. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
Devices must be registered in Autopilot using hardware hash
Prerequisite for Autopilot deployment.
Devices must be domain-joined to on-premises AD
Why wrong: Autopilot supports Entra ID join directly.
An Azure AD Premium P2 license must be assigned
Why wrong: P1 is sufficient for Autopilot.
Configuration Manager must be deployed for OS imaging
Why wrong: Autopilot is cloud-native, no ConfigMgr needed.
Answer choices
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
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
Prerequisite for Autopilot deployment.
Related concept
Read the scenario before looking for a memorised answer.
Devices must be domain-joined to on-premises AD
Why it's wrong here
Autopilot supports Entra ID join directly.
An Azure AD Premium 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 cloud-native, no ConfigMgr needed.
Common exam traps
The trap here is that candidates often assume Autopilot requires an on-premises domain join (option B) because they confuse Autopilot with traditional imaging or hybrid Azure AD join scenarios, but Autopilot's core value is cloud-native, domain-join-free provisioning.
Detailed technical explanation
The hardware hash is a 4K-byte Base64-encoded string generated by the device's TPM (Trusted Platform Module) or firmware, containing details like the device serial number, manufacturer, model, and SMBIOS UUID. This hash is uploaded to the Autopilot service via a CSV file or directly through Microsoft Store for Business/Intune. Once registered, the device is recognized during OOBE, and Autopilot applies the deployment profile (e.g., user-driven or self-deploying mode) to join the device to Entra ID without any manual intervention.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Prepare infrastructure for devices — study guide chapter
Learn the concepts, then practise the questions
Prepare infrastructure for devices practice questions
Targeted practice on this topic area only
All MD-102 questions
991 questions across all exam domains
Microsoft 365 Endpoint Administrator MD-102 study guide
Full concept coverage aligned to exam objectives
MD-102 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise MD-102 questions linked to Prepare infrastructure for devices.
Practise MD-102 questions linked to Manage and maintain devices.
Practise MD-102 questions linked to Manage applications.
Practise MD-102 questions linked to Protect devices.
Practise MD-102 questions linked to Deploy Windows client.
Practise MD-102 questions linked to Manage identity and compliance.
Practise MD-102 questions linked to Manage, maintain, and protect devices.
Practise MD-102 questions linked to MD-102 fundamentals.
Practise MD-102 questions linked to MD-102 scenario.
Practise MD-102 questions linked to MD-102 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Prepare infrastructure for devices — This question tests Prepare infrastructure for devices — Read the scenario before looking for a memorised answer..
The correct answer is: 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.