MD-102 Prepare infrastructure for devices Practice Question
Which TWO components are required for a successful Windows Autopilot deployment with user-driven Microsoft Entra ID join? (Select two.)
⚠ Common exam trap
It's easy for candidates to confuse the optional Enrollment Status Page with a mandatory component, or they mistakenly believe on-premises Active Directory join is required for user-driven Autopilot, when in fact Microsoft Entra ID join is a separate, cloud-native identity option.
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
✓
Device registration in the Autopilot service using hardware hash.
Option B is correct because a device must first be registered in the Windows Autopilot service by uploading its hardware hash (collected via Get-WindowsAutopilotInfo or the OEM) so that the Autopilot service can recognize the device and associate it with the tenant during OOBE. Option D is correct because a Windows Autopilot deployment profile in Intune defines the critical settings for the user-driven Entra ID join scenario, including the deployment mode (User-Driven), the join type (Microsoft Entra joined), and the out-of-box experience options that drive the enrollment. Option A is not required: the Enrollment Status Page is an optional configuration that only controls what the user sees during device setup and does not enable the Autopilot deployment itself. Option C is incorrect because user-driven Autopilot with Microsoft Entra ID join does not require on-premises Active Directory domain join; that would be a hybrid Entra join scenario. Option E is incorrect because Microsoft Configuration Manager co-management is not a prerequisite for Autopilot; Intune alone is sufficient to deliver the deployment profile and manage the device.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enrollment Status Page (ESP) configuration.
Why it's wrong here
The Enrollment Status Page is optional; it only controls what users see during provisioning and can block device use until apps install. It is tempting because it appears integral to the out-of-box experience, but user-driven Microsoft Entra join succeeds with just Autopilot registration and a Deployment Profile.
- ✓
Device registration in the Autopilot service using hardware hash.
Why this is correct
Registering the device's hardware hash in the Windows Autopilot service creates the Autopilot device identity, which is mandatory for user-driven Microsoft Entra ID join. Without this record, the device cannot be matched to a deployment profile during OOBE, so the profile's join settings never apply.
- ✗
On-premises Active Directory domain join.
Why it's wrong here
On-premises Active Directory domain join contradicts the Microsoft Entra ID join requirement; Autopilot supports either, not both simultaneously. Hybrid Microsoft Entra ID join is tempting because many organisations retain on-premises identities, but that scenario requires the Hybrid Microsoft Entra ID Join deployment mode, not user-driven Entra join.
- ✓
Windows Autopilot deployment profile in Intune.
Why this is correct
A Windows Autopilot deployment profile in Intune defines the join type, naming and out-of-box experience settings. Without it assigned to the registered device, user-driven Microsoft Entra ID join cannot proceed, making it a required component.
- ✗
Microsoft Configuration Manager co-management.
Why it's wrong here
Configuration Manager co-management is optional for Autopilot; user-driven Microsoft Entra join needs only Intune enrolment, Autopilot device registration and the Deployment Profile. Co-management suits organisations managing existing Windows devices with both Configuration Manager and Intune, not this scenario.
Go deeper
Related to this question
Learn chapter
Enrolling Devices with Microsoft Intune
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.
Key term
Configuration Manager
Configuration Manager is a systems management tool by Microsoft that helps IT administrators deploy software, enforce security policies, and manage devices across an organization.
About these practice questions
This MD-102 question is part of Courseiva's 556-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.