Endpoint Administrator MD-102 Practice Test 4
Question 30
After deploying the purchase-order-based dynamic rule, what enrollment-time evidence demonstrates correct group targeting before applying a high-risk policy?
- The dynamic group contains every Autopilot device regardless of purchase order
- Matching devices are included but a different purchase-order device is also included
- The rule text is present, but there are no devices or evaluated memberships
- Test serials with matching `[PurchaseOrderId]` populate the dynamic group while comparable Autopilot serials from a different purchase order are excluded
Explanation
Correct Answer
D:A positive and negative hardware sample verifies the intended procurement segmentation rather than mere group existence.
Incorrect Answers
A:That verifies a generic ZTD grouping but fails required procurement isolation.
B:Positive-only selection is insufficient; the rule leaks unrelated procurement hardware.
C:Saving a dynamic expression does not show its effective membership logic.
Question 31
An incident analyst sees `AzureAdJoined : YES`, `DomainJoined : YES` in Windows device-state output. The task is to classify the machine’s identity trust, not its MDM enrollment. Which classification is correct?
- Microsoft Entra joined, without hybrid join
- Microsoft Entra registered, not joined
- Only on-premises AD domain joined
- Microsoft Entra hybrid joined
Explanation
Correct Answer
D:Hybrid join is exactly the simultaneous Entra and on-premises Active Directory domain join state.
Incorrect Answers
A:Cloud-only Entra join has DomainJoined NO; the prompt explicitly shows DomainJoined YES.
B:A workplace registration does not have the dual device join flags shown.
C:A pure domain joined system has AzureAdJoined NO in the documented device-state table.
Question 32
A Windows help-desk technician runs `dsregcmd /status` elevated and sees an ambiguous `WamDefaultSet` error. The user can reproduce a sign-in issue but the analyst needs the actual user-context token information. What is the best next diagnostic?
- Run `dsregcmd /status` in the affected signed-in user context and inspect user and SSO state separately from device join state
- Treat the elevated WAM field error as proof `AzureAdJoined` must be NO
- Rerun only the device-state section while ignoring the affected employee’s user/SSO state
- Assume an Intune management record fully establishes the Windows WAM default account status
Explanation
Correct Answer
A:Microsoft documents WAM user-state details can be misleading in an elevated context; collecting the proper user context avoids a false device-state diagnosis.
Incorrect Answers
B:WAM user-state status and Entra device join are distinct, and elevated context can alter WAM diagnostics.
C:A user authentication symptom requires collecting user-context evidence, not only device join flags.
D:MDM inventory does not directly validate the current user’s WAM context.
Question 33
An administrator must establish a Windows computer is hybrid joined and the logged-in employee also has a usable Entra SSO token. Which combined evidence is the most complete?
- In the proper contexts, device flags show `DomainJoined : YES` plus `AzureAdJoined : YES`, and the user’s SSO section reports `AzureAdPrt : YES`
- Only `DomainJoined : YES` in Device State
- Both device join flags YES with `AzureAdPrt : NO` in the affected user session
- `AzureAdPrt : YES` with `AzureAdJoined : NO`
Explanation
Correct Answer
A:Device hybrid trust and user Primary Refresh Token are distinct states; both are needed to support the requested combined claim.
Incorrect Answers
B:AD domain membership does not prove Entra hybrid registration or a user PRT.
C:Hybrid identity is present, but the required working user SSO token is missing.
D:A PRT does not establish this computer has the requested hybrid device join state.
Question 34
A security team disabled a lost Windows device object in Microsoft Entra. Months later it is recovered, its identity is confirmed, and it is cleared for managed reuse. Which action addresses the specific identity-control state now blocking device authentication?
- Change the Intune device compliance policy while keeping the verified Entra object Disabled
- Create an additional dynamic device group for the recovered endpoint without enabling its identity
- After verifying authorization and the correct device object, re-enable that device identity in Microsoft Entra, then test sign-in and applicable access controls
- Recreate a new Entra device registration immediately without validating the recovered existing identity
Explanation
Correct Answer
C:Disabling an Entra device prevents its device-based authentication; enabling the validated original device object is the targeted identity restoration.
Incorrect Answers
A:A compliant management policy cannot reverse the explicit disabled identity state.
B:Group assignment cannot cause a disabled object to authenticate.
D:Replacing identities unnecessarily can cause trust and policy disruption; the approved original object needs targeted verification.
Question 35
A recovered Windows endpoint reports an Entra sign-in restriction. The device is otherwise healthy, but its verified object is listed as Disabled in Entra ID. What is the direct security-state diagnosis?
- A device-based Conditional Access policy alone is misconfigured
- The disabled Entra device identity cannot authenticate normally to the protected Microsoft Entra resource path
- The Intune compliance evaluation must be Not evaluated before sign-in
- The device group assignment has not synchronized yet
Explanation
Correct Answer
B:Device disablement is an explicit control state, distinct from a missing application or a Wi-Fi fault.
Incorrect Answers
A:A Disabled Entra identity itself prevents authenticating; CA is not the only barrier.
C:The visible cause is the disabled identity, regardless of a separate compliance state.
D:A group timing issue does not turn the selected Entra record from Disabled to Enabled.
Question 36
After a disabled corporate Windows device is authorized for reuse, what is the minimum defensible acceptance test of its identity restoration?
- The Entra object is Enabled, but no attempt to sign in has been made
- A different device with the same display name successfully authenticates
- The same authenticated device ID is Enabled in Entra and successfully signs in to a device-protected test resource under the intended Conditional Access requirements
- Access succeeds only after all device-based Conditional Access requirements are removed
Explanation
Correct Answer
C:This pairs the correct device-object state with actual identity enforcement, without broadly weakening access controls.
Incorrect Answers
A:Object state alone does not show authentication or Conditional Access completion.
B:A matching name does not test the restored device identity.
D:Bypassing controls does not verify safe restoration under the intended policy.
Question 37
A subsidiary permits only an authorized onboarding team to join company Windows laptops to Microsoft Entra. Device quotas are sufficient, but all ordinary employees are currently allowed to perform joins. Which tenant policy directly restricts who may initiate device join?
- Set “Users may join devices to Microsoft Entra” to Selected and include only the approved onboarding users or user groups
- Restrict the Entra per-user device count to one while leaving join enabled for All
- Set Intune MDM user scope to Some for onboarding staff but leave Entra join permission at All
- Make a dynamic device group named Onboarding and assume only members may initiate join
Explanation
Correct Answer
A:The Entra join-permission setting determines eligible join actors; a device count limit only constrains quantity after a user has permission.
Incorrect Answers
B:Any unapproved employee could still join a first device; authorization was not restricted.
C:MDM auto-enrollment scope and the right to join a device are different policy boundaries.
D:Device group targeting does not authorize user principals who perform device join.
Question 38
After administrators set the Entra device join option to Selected, an authorized technician still cannot join a new PC. The device limit is not reached. The technician is absent from the selected user-group membership. What is the specific blocker?
- The configured maximum devices per user is already high enough
- The user initiating the join is outside the Selected users or groups authorized for Microsoft Entra join
- The Windows Autopilot profile assignment has completed
- The MDM automatic enrollment scope includes the technician
Explanation
Correct Answer
B:Selected join permissions evaluate the initiating user, independent of available per-user device quota.
Incorrect Answers
A:Capacity is not the failing condition when the initiating user is absent from the Selected join permission population.
C:An assigned provisioning profile does not automatically authorize this user under Selected join permissions.
D:MDM eligibility does not override a separate Entra permission to join devices.
Question 39
The approved onboarding team was added to Selected Entra join permissions. Which controlled trial demonstrates the intended permission boundary?
- An approved onboarding user joins a test Windows PC successfully while an ordinary out-of-scope user is denied device join under equivalent conditions
- An in-scope user can join, but no excluded user has been tried
- An excluded user’s already joined PC can still sign in
- The Selected membership appears correct in the admin center but no join attempt is executed
Explanation
Correct Answer
A:Both positive and negative tests are needed to prove the security boundary is the initiating user, not just a usable join service.
Incorrect Answers
B:A positive test alone does not confirm out-of-scope join attempts are denied.
C:Sign-in to an existing device is not a test of permission to join a new device.
D:A policy display cannot establish effective authorization boundaries.
Question 40
An access-policy pilot must target only Entra-joined Windows computers while excluding workplace-registered personal laptops. Devices are already present in the Entra directory. Which dynamic device membership condition tests the trust distinction?
- `device.deviceOSType -eq "Windows"`
- `(device.deviceOSType -eq "Windows") -and (device.deviceTrustType -eq "AzureAD")`
- `device.deviceTrustType -eq "AzureAD"`
- `(device.deviceOSType -eq "Windows") -and (device.deviceTrustType -eq "Workplace")`
Explanation
Correct Answer
B:Combining OS and trust type is necessary: the user needs Windows devices and must exclude workplace registration; either condition alone is insufficient.
Incorrect Answers
A:OS filtering alone includes workplace-registered personal Windows devices.
C:A trust-only rule can target additional joined platforms and does not independently enforce the explicit Windows scope.
D:The Workplace value selects registered Windows devices that the pilot must exclude.