MD-102 Prepare infrastructure for devices Practice Question
You need to ensure that Windows 10 devices automatically enroll in Intune when they join Microsoft Entra ID. Which setting should you configure?
⚠ Common exam trap
Watch out — candidates often confuse the MDM user scope (which controls the automatic enrollment trigger) with enrollment restrictions or compliance policies, which only apply after the enrollment process has already started.
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
✓
MDM user scope in Microsoft Entra ID
The MDM user scope setting in Microsoft Entra ID (formerly Azure AD) controls which users can automatically enroll their Windows 10 devices into Intune when they join Entra ID. When set to 'All' or 'Some', the device triggers automatic MDM enrollment during the Entra ID join process using the MDM enrollment protocol (MS-MDE), eliminating the need for manual enrollment steps.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Compliance policies in Intune
Why it's wrong here
Compliance policies evaluate and remediate device settings after enrolment; they do not trigger enrolment itself. They are the right choice for enforcing configuration baselines, but automatic Intune enrolment on Microsoft Entra ID join is controlled by the MDM user scope setting.
- ✓
MDM user scope in Microsoft Entra ID
Why this is correct
MDM user scope in Microsoft Entra ID determines which users' devices are automatically enrolled into Intune when they join Microsoft Entra ID. Configuring it to All or a selected group satisfies the stem's requirement for automatic enrolment triggered by the join itself.
- ✗
Co-management slider in Configuration Manager
Why it's wrong here
The co-management slider moves existing Configuration Manager workloads to Intune; it does not enrol Microsoft Entra ID-joined devices. It is correct when transitioning Configuration Manager-managed clients, but here devices join Microsoft Entra ID directly, requiring the MDM user scope instead.
- ✗
Enrollment device platform restrictions in Intune
Why it's wrong here
Platform restrictions filter which operating systems or versions may enrol; they never initiate enrolment. They suit blocking personally owned or unsupported devices, whereas automatic enrolment on Microsoft Entra ID join depends on the MDM user scope configuration.
Go deeper
Related to this question
Learn chapter
Troubleshooting Device Enrollment and Management
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
Intune
Microsoft Intune is a cloud-based service that helps organizations manage their users' devices and applications, ensuring security and compliance without needing to own or control the physical hardware.
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.