Endpoint Administrator MD-102 Practice Test 6
Question 50
An operator repeatedly re-registers a corporate Windows laptop even though device state stays `AzureAdJoined : YES`. The user’s SSO section consistently has `AzureAdPrt : NO`. What is the troubleshooting mistake?
- Continue resetting the device registration to change the user’s PRT status
- Conflating device registration state with the separate signed-in user PRT/SSO state
- Conclude user SSO must be valid whenever AzureAdJoined is YES
- Look only at Entra device object inventory and ignore the SSO section
Explanation
Correct Answer
B:Rejoining a device needlessly does not target the demonstrated user-token acquisition failure.
Incorrect Answers
A:Repeated device registration is the misdirected action in the prompt.
C:A joined device can have an affected user session with no PRT.
D:Device inventory does not measure the user token state the error identifies.
Question 51
The identity team changes a user sign-in configuration to address a missing PRT on an Entra-joined Windows pilot. Which retest proves the intended improvement?
- `AzureAdJoined : YES` alone, without a user PRT or app sign-in
- In the affected logged-in user context, `AzureAdPrt : YES` appears and the original Microsoft 365 SSO access succeeds while `AzureAdJoined : YES` remains true
- `AzureAdPrt : YES` but the protected application still rejects the user
- An Intune enrollment record appears for the laptop with no user-context retest
Explanation
Correct Answer
B:A user PRT plus successful protected-app access demonstrates resolution without masking or changing the device join state.
Incorrect Answers
A:Device trust is present, but user SSO resolution has not been demonstrated.
C:Token availability without successful target app access is not the complete acceptance criterion.
D:MDM inventory is not a direct test of user PRT and single sign-on.
Question 52
New company Windows laptops successfully join Microsoft Entra but do not appear as Intune-managed. The affected onboarding users were excluded from a tenant-wide MDM user scope set to Some. The organization wants automatic Intune enrollment for these users. What is the targeted administrative change?
- Set the Entra join permission to All but leave automatic MDM scope excluding the users
- Raise the per-user Entra device join quota while leaving the MDM scope unchanged
- Configure an Enrollment Status Page without including users in automatic MDM scope
- Include the approved onboarding users in Intune automatic MDM enrollment user scope and verify eligible licensing and enrollment restrictions
Explanation
Correct Answer
D:Entra device join may complete without automatic Intune enrollment when the initiating user is outside the applicable MDM user scope.
Incorrect Answers
A:Join authorization does not enroll users excluded from automatic Intune management.
B:The affected PCs already joined; quota does not repair automatic MDM eligibility.
C:ESP can monitor provisioning after MDM eligibility but does not replace the enrollment user scope.
Question 53
A Windows endpoint shows the correct `AzureAdJoined : YES` state but has no Intune management record. The Entra join-permission setting allows the user; automatic MDM scope is set to None. Which conclusion best separates the two issues?
- Assume that Entra joined state guarantees Intune management even with MDM user scope None
- Conclude the initiating user cannot join Entra because no Intune record appears
- Attribute the missing Intune record to a Windows app install timeout before checking MDM user scope
- The Entra device identity join and automatic MDM enrollment are distinct; the disabled automatic MDM user scope explains why Intune management did not follow
Explanation
Correct Answer
D:The controlling gap is automatic MDM enrollment configuration, not absence of the already verified Entra device join.
Incorrect Answers
A:Identity join and automatic MDM enrollment are separate outcomes.
B:The specified local device flag already proves Entra join succeeded.
C:An application timeout is downstream; auto-enrollment is explicitly disabled for the scope.
Question 54
After an MDM user-scope adjustment for a Windows onboarding cohort, which pilot verifies the actual identity-to-management handoff?
- An in-scope laptop has Entra join but still no Intune managed-device record
- Intune shows a managed-device record but the local device has no verified Entra join identity
- A newly joining in-scope Windows test device has its corresponding Entra joined identity and a valid Intune managed-device enrollment, while an out-of-scope test follows the intended restriction
- The Windows MDM user scope reads Some but no newly joining in-scope pilot has been tested
Explanation
Correct Answer
C:Verifying both Entra identity and Intune management records tests the two successive lifecycle steps and the requested scope.
Incorrect Answers
A:Identity success alone fails the automatic MDM enrollment goal.
B:A management entry alone does not establish the intended join plus management handoff.
D:A portal setting without observed enrollment does not validate operational delivery.
Question 55
A logistics operator is implementing an endpoint standard; a pilot deployment must precede the wider rollout. The requirement is that personal Android phones need isolated work apps while retaining personal photos and consumer apps. Which Intune/Microsoft endpoint management decision BEST meets this requirement?
- Use Android Enterprise fully managed provisioning for the personally owned fleet
- Use dedicated-device enrollment for phones assigned to individual users
- Publish corporate apps outside the work profile as unmanaged personal apps
- Enroll Android Enterprise personally owned work-profile devices
Explanation
Correct Answer
D:Enroll Android Enterprise personally owned work-profile devices. 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 personal Android phones need isolated work apps while retaining personal photos and consumer apps. 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:Use Android Enterprise fully managed provisioning for the personally owned fleet. Fully managed enrollment targets organization-owned devices and alters the ownership boundary.
B:Use dedicated-device enrollment for phones assigned to individual users. Dedicated mode is for userless or single-purpose corporate devices.
C:Publish corporate apps outside the work profile as unmanaged personal apps. Unmanaged installation does not provide the requested managed work container.
Question 56
A logistics operator is implementing an endpoint standard; a pilot deployment must precede the wider rollout. During a pilot, the team finds that personal Android phones need isolated work apps while retaining personal photos and consumer apps, but the intended control is not reliably in effect. Which troubleshooting action should be performed FIRST to isolate the relevant management boundary?
- Use Android Enterprise fully managed provisioning for the personally owned fleet
- Use dedicated-device enrollment for phones assigned to individual users
- Publish corporate apps outside the work profile as unmanaged personal apps
- Inspect the effective assignment and applicable runtime state, then enroll Android Enterprise personally owned work-profile devices
Explanation
Correct Answer
D:Inspect the effective assignment and applicable runtime state, then enroll Android Enterprise personally owned work-profile devices. Begin by confirming the effective assigned policy and device identity before changing unrelated settings. The substantive remediation is: Enroll Android Enterprise personally owned work-profile devices. 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:Use Android Enterprise fully managed provisioning for the personally owned fleet. Fully managed enrollment targets organization-owned devices and alters the ownership boundary.
B:Use dedicated-device enrollment for phones assigned to individual users. Dedicated mode is for userless or single-purpose corporate devices.
C:Publish corporate apps outside the work profile as unmanaged personal apps. Unmanaged installation does not provide the requested managed work container.
Question 57
A logistics operator is implementing an endpoint standard; a pilot deployment must precede the wider rollout. For the scenario in which personal Android phones need isolated work apps while retaining personal photos and consumer apps, the administrator needs evidence that the requirement is actually enforced. Which verification provides the MOST DIRECT evidence?
- On a pilot device, verify that this configuration is deployed and record its runtime result: use Android Enterprise fully managed provisioning for the personally owned fleet
- On a pilot device, verify that this configuration is deployed and record its runtime result: use dedicated-device enrollment for phones assigned to individual users
- Inspect an enrolled phone for separate work profile and app policy delivery
- On a pilot device, verify that this configuration is deployed and record its runtime result: publish corporate apps outside the work profile as unmanaged personal apps
Explanation
Correct Answer
C:Inspect an enrolled phone for separate work profile and app policy delivery. 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: Enroll Android Enterprise personally owned work-profile devices. Check platform and identity requirements and preserve the published test outcome as evidence.
Incorrect Answers
A:On a pilot device, verify that this configuration is deployed and record its runtime result: use Android Enterprise fully managed provisioning for the personally owned fleet. Fully managed enrollment targets organization-owned devices and alters the ownership boundary.
B:On a pilot device, verify that this configuration is deployed and record its runtime result: use dedicated-device enrollment for phones assigned to individual users. Dedicated mode is for userless or single-purpose corporate devices.
D:On a pilot device, verify that this configuration is deployed and record its runtime result: publish corporate apps outside the work profile as unmanaged personal apps. Unmanaged installation does not provide the requested managed work container.
Question 58
A public-sector agency is implementing an endpoint standard; device actions require an auditable authorized scope. The requirement is that userless Android barcode scanners must boot directly into a managed warehouse application. Which Intune/Microsoft endpoint management decision BEST meets this requirement?
- Select personally owned work-profile enrollment for a shared scanner
- Choose corporate-owned work profile for devices with no assigned user
- Select Android Enterprise corporate-owned dedicated enrollment and a kiosk experience
- Deploy the scanner app as optional without device experience restrictions
Explanation
Correct Answer
C:Select Android Enterprise corporate-owned dedicated enrollment and a kiosk experience. 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 userless Android barcode scanners must boot directly into a managed warehouse application. 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:Select personally owned work-profile enrollment for a shared scanner. Work-profile enrollment assumes a personal user context absent on shared kiosks.
B:Choose corporate-owned work profile for devices with no assigned user. That mode is intended for organization-owned devices associated with a single user.
D:Deploy the scanner app as optional without device experience restrictions. Optional availability does not implement the required locked-down userless mode.
Question 59
A public-sector agency is implementing an endpoint standard; device actions require an auditable authorized scope. During a pilot, the team finds that userless Android barcode scanners must boot directly into a managed warehouse application, but the intended control is not reliably in effect. Which troubleshooting action should be performed FIRST to isolate the relevant management boundary?
- Select personally owned work-profile enrollment for a shared scanner
- Choose corporate-owned work profile for devices with no assigned user
- Inspect the effective assignment and applicable runtime state, then select Android Enterprise corporate-owned dedicated enrollment and a kiosk experience
- Deploy the scanner app as optional without device experience restrictions
Explanation
Correct Answer
C:Inspect the effective assignment and applicable runtime state, then select Android Enterprise corporate-owned dedicated enrollment and a kiosk experience. Begin by confirming the effective assigned policy and device identity before changing unrelated settings. The substantive remediation is: Select Android Enterprise corporate-owned dedicated enrollment and a kiosk experience. 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:Select personally owned work-profile enrollment for a shared scanner. Work-profile enrollment assumes a personal user context absent on shared kiosks.
B:Choose corporate-owned work profile for devices with no assigned user. That mode is intended for organization-owned devices associated with a single user.
D:Deploy the scanner app as optional without device experience restrictions. Optional availability does not implement the required locked-down userless mode.
Question 60
A public-sector agency is implementing an endpoint standard; device actions require an auditable authorized scope. For the scenario in which userless Android barcode scanners must boot directly into a managed warehouse application, the administrator needs evidence that the requirement is actually enforced. Which verification provides the MOST DIRECT evidence?
- Validate device owner enrollment and kiosk launch without a personal sign-in
- On a pilot device, verify that this configuration is deployed and record its runtime result: select personally owned work-profile enrollment for a shared scanner
- On a pilot device, verify that this configuration is deployed and record its runtime result: choose corporate-owned work profile for devices with no assigned user
- On a pilot device, verify that this configuration is deployed and record its runtime result: deploy the scanner app as optional without device experience restrictions
Explanation
Correct Answer
A:Validate device owner enrollment and kiosk launch without a personal sign-in. 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: Select Android Enterprise corporate-owned dedicated enrollment and a kiosk experience. 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: select personally owned work-profile enrollment for a shared scanner. Work-profile enrollment assumes a personal user context absent on shared kiosks.
C:On a pilot device, verify that this configuration is deployed and record its runtime result: choose corporate-owned work profile for devices with no assigned user. That mode is intended for organization-owned devices associated with a single user.
D:On a pilot device, verify that this configuration is deployed and record its runtime result: deploy the scanner app as optional without device experience restrictions. Optional availability does not implement the required locked-down userless mode.