Endpoint Administrator MD-102 Practice Test 18
Question 170
A hybrid-joined Windows 11 fleet needs Windows Hello for Business sign-in to on-premises file shares, but operations will not deploy user authentication certificates. Hello biometric sign-in succeeds for cloud services but Kerberos access to on-premises shares fails for the cloud-trust pilot. What should be checked?
- The Windows Hello credential has not been provisioned on the affected device, even though biometric sign-in already succeeds
- Cloud Kerberos trust prerequisites such as the Entra Kerberos object, supported OS and available read-write domain controllers
- Inspect only the SMB share ACL and skip checking whether the Windows Hello client can obtain an on-premises Kerberos ticket
- Cloud Kerberos trust cannot work unless AD CS issues a user-authentication certificate to each Hello user
Explanation
Correct Answer
B:Cloud sign-in alone does not prove the hybrid Kerberos path is operational
Incorrect Answers
A:The stem confirms that Hello biometric cloud sign-in succeeds; missing Hello provisioning would contradict that observation rather than isolate why on-premises Kerberos authentication fails.
C:Share permissions are relevant after authentication, but this scenario reports failure to obtain on-premises Kerberos authentication; first verify cloud Kerberos trust prerequisites, not just ACLs.
D:Cloud Kerberos trust does not require user authentication certificates; validate the Entra Kerberos object and hybrid domain-controller prerequisites instead.
Question 171
A hybrid-joined Windows 11 fleet needs Windows Hello for Business sign-in to on-premises file shares, but operations will not deploy user authentication certificates. What observation confirms that cloud Kerberos trust works for this pilot?
- The test user completes Windows Hello provisioning and can obtain a cloud PRT, but SMB access to the domain share is not exercised
- The test user signs in with Hello and accesses the required on-premises SMB share using Kerberos without a user auth certificate
- The user opens a cloud-only SharePoint page after browser sign-in
- A certificate trust policy is created but not delivered
Explanation
Correct Answer
B:This verifies the specific hybrid resource-access outcome
Incorrect Answers
A:A primary refresh token or successful Hello enrollment verifies cloud sign-in, not the required on-premises Kerberos-authenticated file-share access.
C:Cloud service access can succeed while hybrid Kerberos is broken
D:A policy artifact does not validate the cloud Kerberos deployment
Question 172
A locked-down Windows endpoint must have one known local support group member added through Intune without overwriting the other legitimate administrators. Which account-protection membership update semantics preserve the existing local group members?
- Configure Replace with only the support principal in a shared local group
- Set a Windows desktop wallpaper configuration profile to the help desk name
- Use the appropriate local user-group membership policy with Add/Update semantics for the specified principal
- Replace the Administrators local-group membership list with only the new support account
Explanation
Correct Answer
C:Add/Update changes the membership without replacing every existing member
Incorrect Answers
A:Replace removes other members not specified in the policy
B:Cosmetic profiles do not manage local security group membership
D:Replace semantics would discard existing authorized members; Add/Update semantics introduces the specified principal while preserving the already approved membership.
Question 173
A locked-down Windows endpoint must have one known local support group member added through Intune without overwriting the other legitimate administrators. After a membership policy reaches pilot devices, a preexisting break-glass local administrator disappears. What is the likely mechanism?
- The support employee password was rotated in Entra
- The devices received an application configuration profile
- The policy used Replace membership instead of adding the intended principal while retaining existing members
- A compliance report refresh completed before device check-in
Explanation
Correct Answer
C:Replace semantics can remove accounts omitted from the resulting list
Incorrect Answers
A:Password rotation does not explain removal of another local group member
B:App settings do not define the local Administrators group
D:Report timing cannot remove a local group member
Question 174
A locked-down Windows endpoint must have one known local support group member added through Intune without overwriting the other legitimate administrators. Which evidence demonstrates that the intended change was additive and scoped?
- Read only the Intune policy name and creation date
- Check that the support principal has a Microsoft 365 license
- Compare effective Administrators memberships before and after on a target and an excluded device, showing support principal added with other approved members retained
- See the break-glass user in an unrelated Entra cloud group
Explanation
Correct Answer
C:Direct local membership comparison tests both preservation and scoping
Incorrect Answers
A:A policy display name does not show effective local group membership
B:Licensing does not prove a local Windows group update
D:Cloud group membership alone cannot establish target endpoint membership
Question 175
A service desk must rotate a local administrator password for a single managed Entra-joined Windows device while avoiding bulk password changes. What authorization set allows a narrowly scoped Intune rotation action?
- Give only Global Reader and assume all remote tasks are inherited
- Grant managed-device read, organization read and the remote-task Rotate Local Admin Password permission for the authorized device scope
- Grant the ability to create Win32 apps instead of remote action permission
- Assign only the managed-device Wipe and Restart remote-task permissions and assume password rotation is part of either action.
Explanation
Correct Answer
B:The Intune action needs visibility plus the specific remote-task permission
Incorrect Answers
A:Read-only directory access does not confer the required Intune action
C:App deployment authorization is unrelated to LAPS rotation
D:Wipe and Restart are separate remote task permissions and do not grant the least-privileged Rotate Local Admin Password operation.
Question 176
A service desk must rotate a local administrator password for a single managed Entra-joined Windows device while avoiding bulk password changes. The Rotate local admin password action is visible but the request fails for an Entra joined device that was offline at submission. Which condition explains it?
- LAPS can rotate only when an administrator changes an Office license
- Rotation is supported only through bulk device actions
- The help-desk operator has read access to LAPS metadata but lacks permission to retrieve the stored password
- For an Entra joined device the manual LAPS rotation action requires the device to be online when requested
Explanation
Correct Answer
D:Offline status is a documented failure condition for this remote action
Incorrect Answers
A:Microsoft 365 licensing does not replace device connectivity for rotation
B:LAPS rotation is not a supported bulk action
C:Password-reading permissions differ from the remote-rotation task, and this cannot explain a request that was already accepted but failed specifically while an Entra-joined device was offline.
Question 177
A service desk must rotate a local administrator password for a single managed Entra-joined Windows device while avoiding bulk password changes. Which evidence closes the single-device password rotation request?
- The help-desk operator can open the device overview page
- For the approved device, the action status becomes Complete and the recorded LAPS rotation metadata changes, while excluded devices are untouched
- The rotation action appears as Pending after initial submission
- A bulk-action selection shows several Windows devices
Explanation
Correct Answer
B:Completion plus targeted updated record distinguishes execution from queuing
Incorrect Answers
A:Device visibility does not prove the remote password changed
C:Pending is not a successful completion state
D:Bulk selection neither rotates LAPS nor establishes narrow authorization
Question 178
A regional support administrator must see devices tagged for one business unit but must not automatically gain all Intune change permissions. Which design separates resource visibility from permitted actions?
- Rely only on a scope tag as authorization for editing every visible device
- Combine an appropriate Intune RBAC role with role assignment scope groups and resource scope tags
- Grant an unrestricted Intune Administrator role and expect a tag to remove all permissions
- Assign devices to a configuration profile with no admin role assignment
Explanation
Correct Answer
B:Scope groups and tags delimit managed resource view, while role permissions delimit allowed actions
Incorrect Answers
A:Scope tags do not grant the underlying action permissions
C:A broad administrator role defeats the requested least privilege
D:Device settings assignment does not delegate operator authorization
Question 179
A regional support administrator must see devices tagged for one business unit but must not automatically gain all Intune change permissions. The operator can see a tagged laptop but the Restart remote action remains unavailable. What is the likely authorization distinction?
- A device tag automatically grants all remote tasks except restart
- Resource visibility is granted but the relevant remote-task permission was not included in the operator role
- The local BitLocker recovery key has not been opened recently
- The device primary user works in a different office timezone
Explanation
Correct Answer
B:Visibility and the ability to perform a device action are distinct controls
Incorrect Answers
A:Tags do not encode such a selective action license
C:Key retrieval history does not enable a device restart permission
D:User timezone does not determine Intune RBAC permissions
Question 180
A regional support administrator must see devices tagged for one business unit but must not automatically gain all Intune change permissions. How can the team prove both boundaries were applied?
- As the scoped operator, list visible tagged and excluded devices and attempt only explicitly authorized actions on a test device
- Verify only that the role assignment has a friendly descriptive name
- Open one permitted device and assume all tags are effective
- Test actions using an unrestricted tenant admin account
Explanation
Correct Answer
A:This tests resource scope and role permissions independently
Incorrect Answers
B:Role names do not establish effective visibility or actions
C:A positive-only view does not show excluded resources are hidden
D:Global admin execution cannot validate the delegated operator boundaries