Valid Windows Autopilot Deployment Scenarios
Which THREE are valid Windows Autopilot deployment scenarios?
Quick Answer
The answer is White Glove, alongside User-Driven and Self-Deploying, as the three valid Windows Autopilot deployment scenarios. White Glove, now known as Windows Autopilot for pre-provisioned deployment, is correct because it allows an IT administrator or partner to pre-configure a device at the factory or in a staging environment, reaching a ready-to-use state before the end user ever touches it. This scenario leverages the hardware hash for initial enrollment into Azure AD and Intune, then applies all policies and apps, so the user only needs to complete a minimal setup. On the MD-102 exam, this question tests your ability to distinguish between the three core scenarios—User-Driven, Self-Deploying, and Pre-Provisioned—and to avoid traps like confusing White Glove with the deprecated Self-Deploying mode for kiosks. A common memory tip is to think of White Glove as “concierge service” for devices: the IT team does the heavy lifting upfront, leaving the user with a polished, ready-to-go machine.
⚠ Common exam trap
Watch out — candidates often confuse deployment phases or management concepts (like app or policy deployment) with the three official Autopilot deployment scenarios, which are strictly self-deploying, user-driven, and white glove (pre-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
✓
Self-deploying
Self-deploying (A) is a valid Windows Autopilot scenario in which the device is provisioned with no user interaction, using a device-targeted profile and TPM attestation, ideal for kiosks and shared devices. User-driven (C) is valid because it lets the end user sign in with their Microsoft Entra ID credentials during OOBE, after which the Autopilot profile applies device and user settings. White glove (E) is valid as the pre-provisioning scenario where a partner or IT technician runs the provisioning process so the device reaches the user ready for a fast, final sign-in. App-driven (B) and Policy-driven (D) are not Autopilot deployment scenarios; Autopilot modes are defined by user interaction and pre-provisioning, not by app or policy triggers.
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
Why this is correct
Self-deploying mode provisions devices with no user interaction, using a device-based Microsoft Entra ID join and TPM attestation. This satisfies the scenario's requirement for kiosk and shared-device rollouts where no credentials can be entered, making it one of the three valid Windows Autopilot deployment scenarios.
- ✗
App-driven
Why it's wrong here
Windows Autopilot deployment modes are user-driven, pre-provisioning, and self-deploying; app-driven is not a valid scenario. It is tempting because applications are assigned during enrolment, and app-driven provisioning would be correct when describing application deployment via Intune rather than the Autopilot deployment mode.
- ✓
User-driven
Why this is correct
User-driven mode lets the end user complete OOBE themselves, signing in with their own Microsoft Entra ID credentials so the device joins and enrols automatically. This satisfies the scenario's requirement for a self-service deployment where IT pre-registers hardware but the user triggers provisioning.
- ✗
Policy-driven
Why it's wrong here
Windows Autopilot deployment modes are user-driven, pre-provisioning (white glove), and self-deploying; policy-driven is not one of them. It is tempting because Intune policy configures Autopilot profiles, and policy-driven enrolment would be correct when describing configuration management rather than the deployment scenario itself.
- ✓
White glove
Why this is correct
White glove (pre-provisioning) lets IT pre-stage the device so the time-consuming provisioning happens before the user receives it, then the user completes a short OOBE. This satisfies the scenario's requirement for a deployment mode that reduces end-user wait time.
Go deeper
Related to this question
Learn chapter
Planning Deployment and Architecture
Key term
TPM
TPM (Trusted Platform Module) is a dedicated hardware chip on a computer's motherboard that stores cryptographic keys, passwords, and certificates to secure the system against unauthorized access and tampering.
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.
About these practice questions
Courseiva writes every MD-102 question from scratch — 556 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on MD-102
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your organization wants to use Windows Autopilot for user-driven deployment. Users should be able to self-deploy their devices by signing in with their corporate credentials. Which Autopilot deployment mode should you use?
easy- A.Pre-provisioned deployment
- B.Hybrid Azure AD join
- ✓ C.User-driven (Azure AD join)
- D.Self-deploying (Azure AD join)
Why C: User-driven (Azure AD join) deployment mode is correct because it allows users to self-deploy their devices by signing in with their corporate credentials during the out-of-box experience (OOBE). This mode joins the device to Azure AD and enrolls it in Microsoft Intune, enabling the user to complete the setup without IT intervention.
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.