MD-102 Prepare infrastructure for devices Practice Question
Exhibit
Refer to the exhibit.
$autopilotDevices = Get-AutopilotDevice -GroupTag 'Sales'
$autopilotDevices | ForEach-Object {
Set-AutopilotDevice -Id $_.Id -GroupTag 'Marketing'
}You run the above PowerShell script to change the Windows Autopilot group tag for devices currently tagged as 'Sales' to 'Marketing'. You have assigned different deployment profiles to the 'Sales' and 'Marketing' group tags. After running the script, you check the Autopilot devices in Intune and see that the group tag for the devices has changed. However, the devices still apply the 'Sales' deployment profile during OOBE. What is the most likely reason?
⚠ Common exam trap
Many candidates assume updating the group tag in Intune will immediately change the deployment profile for already-enrolled devices, but Microsoft's Autopilot design evaluates the tag only at enrollment time, not retroactively.
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
✓
The deployment profile assignment is based on the group tag at the time of enrollment; existing devices retain the original profile.
The group tag is evaluated at the time of enrollment to determine which deployment profile to assign. Changing the group tag on an already-enrolled device does not retroactively change the profile assignment; the device retains the profile that was applied during its original OOBE. This is by design in Windows Autopilot, as the profile is bound to the device record at enrollment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The deployment profile is assigned to the device by device ID, not group tag.
Why it's wrong here
Profiles can be assigned by group tag or device ID, but tag-based assignment is common.
- ✓
The deployment profile assignment is based on the group tag at the time of enrollment; existing devices retain the original profile.
Why this is correct
Autopilot profiles are assigned at enrollment, and changing the tag does not reassign profiles for already-enrolled devices.
- ✗
The script needs to include a step to remove the device from Autopilot and re-import it.
Why it's wrong here
Re-importing is not necessary; the tag change should work for future enrollments.
- ✗
The script did not sync the device details to Intune after changing the group tag.
Why it's wrong here
The group tag change is synced, but the profile assignment may not update.
Go deeper
Related to this question
Learn chapter
Planning Deployment and Architecture
Key term
Deployment profile
A deployment profile is a set of configuration settings and policies that IT administrators apply to enroll and configure devices in an organization, automating the setup process.
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
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.