MD-102 Prepare infrastructure for devices Practice Question
Exhibit
{
"deviceEnrollmentConfiguration": {
"@odata.type": "#microsoft.graph.windows10EnrollmentProfile",
"displayName": "Autopilot Profile",
"description": "Standard user-driven Autopilot",
"enrollmentType": "azureAdJoined",
"language": "en-US",
"outOfBoxExperienceSettings": {
"hidePrivacySettings": false,
"hideEULA": false,
"userType": "standard",
"deviceUsageType": "singleUser"
}
}
}Refer to the exhibit. You are configuring a Windows Autopilot profile. The profile specifies enrollmentType as 'azureAdJoined'. Which scenario does this profile support?
⚠ Common exam trap
Many exam-takers confuse 'azureAdJoined' with self-deploying mode (option A) because both result in Microsoft Entra ID join, but the key differentiator is that self-deploying mode requires additional profile settings (like a device enrollment manager account) and is intended for kiosk or shared devices, not user-driven scenarios.
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
✓
User-driven deployment with Microsoft Entra ID join.
The enrollmentType 'azureAdJoined' in a Windows Autopilot profile specifically configures a user-driven deployment that joins the device to Microsoft Entra ID (formerly Azure AD). In this mode, the end user provides their Microsoft Entra ID credentials during the out-of-box experience (OOBE), and the device is registered as a Microsoft Entra ID joined device, enabling single sign-on and compliance policies without requiring on-premises infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Self-deploying mode where no user interaction is required.
Why it's wrong here
Self-deploying requires a different profile type.
- ✓
User-driven deployment with Microsoft Entra ID join.
Why this is correct
User-driven Entra ID join is the standard scenario.
- ✗
Hybrid Microsoft Entra ID join with on-premises domain controller.
Why it's wrong here
Hybrid join requires enrollmentType 'azureAdHybridJoined'.
- ✗
On-premises Active Directory domain join only.
Why it's wrong here
Autopilot does not support pure on-premises join.
Go deeper
Related to this question
Learn chapter
Introduction to Endpoint Management in Microsoft 365
Key term
Single sign-on
Single sign-on (SSO) is an authentication method that allows a user to log in once and gain access to multiple applications or systems without re-entering credentials.
Key term
Autopilot profile
An Autopilot profile is a collection of configuration settings that dictates how a new Windows device will be set up and delivered to an end user with minimal IT intervention.
About these practice questions
One of 942 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.