Endpoint Administrator MD-102 Practice Test 13
Question 120
A pilot user signs into the configured JIT-capable app after iOS ADE Setup Assistant. What is the strongest end-to-end acceptance criterion?
- The iPhone is supervised and appears in Intune but has not completed its Entra registration
- An SSO extension configuration exists but the designated app has never been signed into
- The iPhone completes Microsoft Entra device registration and the intended compliance evaluation, and its protected managed app can satisfy Conditional Access
- The user completed Setup Assistant only and Conditional Access still rejects the managed app
Explanation
Correct Answer
C:This tests the desired identity, compliance, and application access consequences, rather than inferring them from Setup Assistant alone.
Incorrect Answers
A:This proves MDM enrollment, not the required JIT identity and compliant protected access outcome.
B:A deployed configuration is not evidence that JIT device registration actually executed.
D:Enrollment home-screen completion alone does not verify Entra registration or CA evaluation.
Question 121
An institution changes the automated device enrollment profile assigned to 40 already activated, supervised iPads. The new Setup Assistant restriction must apply during onboarding and users consent to a scheduled wipe. Which deployment plan matches ADE lifecycle behavior?
- Assign the new ADE profile and ask active devices to check in, without a wipe or re-enrollment
- Retire the iPad inventory entry but leave the physical device activated and unmanaged
- Assign the updated ADE profile and re-enroll pilot iPads by resetting them and completing Setup Assistant before widening the rollout
- Deliver a normal device configuration profile and assume it retroactively changes the old Setup Assistant screens
Explanation
Correct Answer
C:ADE enrollment-profile changes take effect during a new enrollment; merely editing the profile does not replay Setup Assistant on activated devices.
Incorrect Answers
A:MDM check-in does not re-run Apple Setup Assistant enrollment-only choices.
B:Record cleanup alone does not execute a new ADE onboarding workflow.
D:Post-enrollment settings and enrollment-time Setup Assistant configuration are different controls.
Question 122
After changing an Apple ADE enrollment profile, staff report old Setup Assistant behavior on iPads already enrolled months ago. The new profile is correctly assigned in Intune. What is the best diagnosis?
- The new profile has not propagated through an ordinary Intune check-in
- The users have not accepted an app protection policy
- Those devices are already activated; the updated ADE setup experience requires a new managed enrollment through reset and Setup Assistant
- The Apple token is necessarily expired whenever an active device retains old onboarding behavior
Explanation
Correct Answer
C:The mismatch is an enrollment lifecycle issue, not evidence that a live device should receive retroactive Setup Assistant changes.
Incorrect Answers
A:A live-device sync does not replay the initial Setup Assistant enrollment policy.
B:MAM acceptance does not control which ADE Setup Assistant screens ran months earlier.
D:Enrollment-time settings can remain fixed on already activated devices even with valid trust credentials.
Question 123
A single pilot iPad is wiped and enrolled again after an ADE profile update. What concrete observations confirm the enrollment-time change?
- The new profile is visible in Intune but the same iPad has not re-enrolled
- An already active iPad checks in and retains the old onboarding behavior
- An administrator confirms the profile edit was saved but cannot show the pilot’s new enrollment record
- During the new Setup Assistant flow the iPad receives the updated organizational management experience, then appears under the intended Intune ADE profile after enrollment
Explanation
Correct Answer
D:The device must actually repeat the Apple enrollment path and show the updated profile, not only have a policy assignment in the console.
Incorrect Answers
A:Profile assignment alone cannot validate that an existing activated iPad ran the new setup sequence.
B:A check-in is not a controlled trial of the new Setup Assistant enrollment settings.
C:Successful metadata editing does not establish applied ADE onboarding behavior.
Question 124
A regional distributor changes the visible name of an assigned Android enrollment profile after several corporate scanners have already been provisioned. Which procedure prevents breaking later enrollments when the profile needs a new descriptive name?
- Edit the existing profile name in place after enrollment tokens are distributed
- Add the new descriptive name to a dynamic-device group but continue using the original assigned enrollment profile.
- Create and assign a replacement enrollment profile with the desired name before retiring the old one
- Delete the current profile before any replacement is assigned
Explanation
Correct Answer
C:Microsoft warns that renaming assigned enrollment profiles can prevent future enrollment
Incorrect Answers
A:Changing the name of an assigned enrollment profile is the documented risk
B:A device-group display name is not the enrollment-profile identifier; it cannot safely rename an already assigned profile.
D:A gap with no assigned profile can strand incoming devices
Question 125
A regional distributor changes the visible name of an assigned Android enrollment profile after several corporate scanners have already been provisioned. Already enrolled scanners keep reporting, but new devices cannot finish enrollment after a profile was renamed. What is the most direct cause?
- The assigned enrollment profile was renamed after deployment, interfering with future enrollment
- A second managed application failed installation after Android enrollment completed on the same new scanners.
- A configuration profile for the already-enrolled scanners changed the warehouse home-screen layout.
- An Entra group display name has an extra space but its ID is unchanged
Explanation
Correct Answer
A:The documented enrollment-profile rename limitation affects later devices
Incorrect Answers
B:A post-enrollment application-install failure occurs after the enrollment step and would not explain new devices failing enrollment immediately after the assigned profile was renamed.
C:A post-enrollment layout-policy change does not explain why previously registered scanners continue checking in but new devices fail at enrollment after a profile rename.
D:The documented action that coincides with failure is the enrollment profile rename
Question 126
A regional distributor changes the visible name of an assigned Android enrollment profile after several corporate scanners have already been provisioned. Which test establishes that a safe replacement profile has restored provisioning?
- A newly named profile is visible to admins in the portal
- New factory-reset test hardware completes enrollment using the replacement profile while previously enrolled scanners continue normal check-in
- The old token PDF remains accessible to the reseller
- The replacement enrollment profile and token are listed as Assigned in the admin center, but no factory-reset scanner has enrolled with them.
Explanation
Correct Answer
B:Both new provisioning and legacy-device continuity are demonstrated
Incorrect Answers
A:Visibility does not prove new devices can enroll
C:Legacy-token availability is not successful replacement enrollment
D:Portal assignment alone does not demonstrate successful new provisioning or continuity of existing device check-in.
Question 127
A university IT team is implementing an endpoint standard; administrators must avoid affecting the excluded faculty cohort. The requirement is that a service desk must view selected devices but may not create compliance policies or remotely wipe endpoints. Which Intune/Microsoft endpoint management decision BEST meets this requirement?
- Assign least-privilege Intune RBAC permissions aligned with read-only support tasks
- Grant the full Intune Administrator role for occasional device viewing
- Use a scope tag alone to grant the ability to view devices
- Add the desk to a local administrators group on endpoints
Explanation
Correct Answer
A:Assign least-privilege Intune RBAC permissions aligned with read-only support tasks. This directly selects the appropriate endpoint-management control for the stated device and user boundary. The decisive distinction is whether the chosen management mechanism actually enforces the requirement in a service desk must view selected devices but may not create compliance policies or remotely wipe endpoints. Confirm on targeted and excluded devices; validate licensing, platform, identity, and policy evaluation rather than assuming that portal assignment alone proves enforcement.
Incorrect Answers
B:Grant the full Intune Administrator role for occasional device viewing. The tenant-wide role includes capabilities outside read-only support.
C:Use a scope tag alone to grant the ability to view devices. Scope tags scope visibility but do not independently grant RBAC permissions.
D:Add the desk to a local administrators group on endpoints. Local Windows privileges do not establish Intune admin portal permissions.
Question 128
A university IT team is implementing an endpoint standard; administrators must avoid affecting the excluded faculty cohort. During a pilot, the team finds that a service desk must view selected devices but may not create compliance policies or remotely wipe endpoints, but the intended control is not reliably in effect. Which troubleshooting action should be performed FIRST to isolate the relevant management boundary?
- Grant the full Intune Administrator role for occasional device viewing
- Use a scope tag alone to grant the ability to view devices
- Add the desk to a local administrators group on endpoints
- Inspect the effective assignment and applicable runtime state, then assign least-privilege Intune RBAC permissions aligned with read-only support tasks
Explanation
Correct Answer
D:Inspect the effective assignment and applicable runtime state, then assign least-privilege Intune RBAC permissions aligned with read-only support tasks. Begin by confirming the effective assigned policy and device identity before changing unrelated settings. The substantive remediation is: Assign least-privilege Intune RBAC permissions aligned with read-only support tasks. When the configured control, its target scope, and the runtime state agree, the investigated failure mode can be isolated without a broad destructive reset.
Incorrect Answers
A:Grant the full Intune Administrator role for occasional device viewing. The tenant-wide role includes capabilities outside read-only support.
B:Use a scope tag alone to grant the ability to view devices. Scope tags scope visibility but do not independently grant RBAC permissions.
C:Add the desk to a local administrators group on endpoints. Local Windows privileges do not establish Intune admin portal permissions.
Question 129
A university IT team is implementing an endpoint standard; administrators must avoid affecting the excluded faculty cohort. For the scenario in which a service desk must view selected devices but may not create compliance policies or remotely wipe endpoints, the administrator needs evidence that the requirement is actually enforced. Which verification provides the MOST DIRECT evidence?
- Test portal read access and denial of policy or wipe actions using a desk account
- On a pilot device, verify that this configuration is deployed and record its runtime result: grant the full Intune Administrator role for occasional device viewing
- On a pilot device, verify that this configuration is deployed and record its runtime result: use a scope tag alone to grant the ability to view devices
- On a pilot device, verify that this configuration is deployed and record its runtime result: add the desk to a local administrators group on endpoints
Explanation
Correct Answer
A:Test portal read access and denial of policy or wipe actions using a desk account. This discriminates true enforcement from a policy that is merely listed or assigned. Use an authorized pilot device and compare the observed result with the expected control: Assign least-privilege Intune RBAC permissions aligned with read-only support tasks. Check platform and identity requirements and preserve the published test outcome as evidence.
Incorrect Answers
B:On a pilot device, verify that this configuration is deployed and record its runtime result: grant the full Intune Administrator role for occasional device viewing. The tenant-wide role includes capabilities outside read-only support.
C:On a pilot device, verify that this configuration is deployed and record its runtime result: use a scope tag alone to grant the ability to view devices. Scope tags scope visibility but do not independently grant RBAC permissions.
D:On a pilot device, verify that this configuration is deployed and record its runtime result: add the desk to a local administrators group on endpoints. Local Windows privileges do not establish Intune admin portal permissions.
Question 130
A regulated insurance provider is implementing an endpoint standard; change control requires auditable deployment evidence. The requirement is that regional admins must see and manage only devices and policy objects tagged for their region. Which Intune/Microsoft endpoint management decision BEST meets this requirement?
- Create scope tags but leave all regional admins assigned tenant-wide unrestricted RBAC scope
- Use dynamic Entra groups but omit scoped administration roles
- Filter the device list in the UI and assume it is an authorization boundary
- Combine RBAC assignments, scope groups and scope tags appropriate to the region
Explanation
Correct Answer
D:Combine RBAC assignments, scope groups and scope tags appropriate to the region. This directly selects the appropriate endpoint-management control for the stated device and user boundary. The decisive distinction is whether the chosen management mechanism actually enforces the requirement in regional admins must see and manage only devices and policy objects tagged for their region. Confirm on targeted and excluded devices; validate licensing, platform, identity, and policy evaluation rather than assuming that portal assignment alone proves enforcement.
Incorrect Answers
A:Create scope tags but leave all regional admins assigned tenant-wide unrestricted RBAC scope. A tag alone cannot neutralize an overly broad role assignment.
B:Use dynamic Entra groups but omit scoped administration roles. Group selection does not constrain all Intune administrative privileges by itself.
C:Filter the device list in the UI and assume it is an authorization boundary. A display filter is not an enforcement of scoped administrative permissions.