Affected device
codeAzureAdJoined : YES
DomainJoined : NO
TenantName : northwind-labs.example
MdmUrl : [blank]
DeviceAuthStatus : SUCCESS
Interpret join and enrollment evidence, repair the enrollment scope, and stage a safe retry.
Your answers and simulator work were saved for this version of the scenario.
Mapped to Microsoft MD-102 objectives · Internal validation 2026-10-06 · Original ITForMe practice mapped to published objectives; not an official exam question. A named independent subject-matter expert has not yet verified the question and answer key.
Method: Mapped to MD-102 objectives 1.1, 1.2, and 2.1; scenario logic and answer feedback checked against current Microsoft Learn documentation.
Current-profile check: 2026-09-30 · Next review due 2026-10-26
Use only the information provided to complete the tasks.
AzureAdJoined : YES
DomainJoined : NO
TenantName : northwind-labs.example
MdmUrl : [blank]
DeviceAuthStatus : SUCCESS
| Setting | Value |
|---|---|
| Autopilot profile | Assigned to AP-Pilot |
| Device group membership | All 24 devices in AP-Pilot |
| MDM user scope | Some: Pilot-Users |
| Users of the 19 managed devices | Members of Pilot-Users |
| Users of the 5 affected devices | Members of Pilot-Contractors only |
| Intune and Microsoft Entra ID P1 licenses | Assigned to all 24 users |
| Enrollment restriction | Windows allowed |
Every submission is retained. Starting another attempt never replaces or unlocks the previous one.
Your first submitted score and detailed answer review will appear here.
Proposals and votes help staff prioritize review. They never change the scoring key automatically.
Be the first to flag unclear wording, an answer-key issue, or a source that needs another look.
Authenticated proposals and one-vote-per-account limits make the queue more resistant to spam.
Sign in to contribute