Endpoint Administrator MD-102 Practice Test 11
Question 100
A Samsung distributor uses Knox Mobile Enrollment for single-user corporate Android devices. A previously exported fully managed enrollment token was accidentally disclosed. How can IT block its use for future provisioning without implying already enrolled phones are removed?
- Factory reset all previously enrolled phones before disabling the token.
- Revoke the exposed fully managed enrollment token and issue a replacement token/profile export for the Knox provisioning flow.
- Remove Microsoft Authenticator from the fleet to invalidate provisioning.
- Change a dynamic user group instead of revoking the token.
Explanation
Correct Answer
B:Intune documents token revocation for leaked tokens, and token replacement or revocation does not alter devices that are already enrolled.
Incorrect Answers
A:The token action does not require wiping existing devices to protect subsequent enrollments.
C:Authenticator is required in fully managed enrollment and its removal is not a token revocation control.
D:Group targeting does not make a compromised enrollment token unusable.
Question 101
The distributor reports that an old Knox JSON enrollment token no longer provisions new phones after IT revoked the leaked token. Existing enrolled phones are still reporting. What explains the differing outcomes?
- The tenant’s Intune MDM authority automatically switched to a different provider.
- The old phones are not really enrolled because their QR code is now inactive.
- Knox requires a new Apple Business Manager server token each time.
- The revoked token is invalid for new enrollment; already enrolled phones retain their Intune enrollment.
Explanation
Correct Answer
D:Revocation affects enrollment-token reuse, not the management relationship on previously enrolled devices.
Incorrect Answers
A:Token revocation does not move MDM authority.
B:Earlier valid enrollments remain enrolled when a token is revoked.
C:Apple ABM tokens do not provision Android Knox devices.
Question 102
Following token replacement, what evidence best proves that the compromised provisioning path is closed while normal management continues?
- The exported JSON is saved to the reseller’s folder.
- Every existing corporate device is deleted from Intune.
- A fresh phone enrolled with the replacement Knox token reaches Intune, the revoked token cannot enroll a reset test phone, and existing managed phones still check in.
- A new static employee group is visible in Entra.
Explanation
Correct Answer
C:Positive and negative enrollment trials plus existing-device continuity isolate the token-revocation effect.
Incorrect Answers
A:Saving a file does not prove the revoked token is unusable or that the new one works.
B:Removing managed devices is not required and would contradict continuity of service.
D:Group visibility does not test token revocation or provisioning.
Question 103
Corporate Android Enterprise fully managed devices must enroll via Chrome-based work-account authentication. A Conditional Access policy for all cloud apps demands an already compliant device from Android browser sessions, blocking setup. Which narrowly scoped exception addresses the bootstrap problem?
- Require the device to be compliant before it can authenticate to Intune.
- Exclude the Microsoft Intune cloud app from that specific compliant-device Conditional Access policy while retaining controls on business apps.
- Exclude all cloud applications from the compliant-device Conditional Access grant for the onboarding user group for its entire lifetime.
- Replace the compliance grant with a requirement for every new phone to complete Intune enrollment before any authentication can occur.
Explanation
Correct Answer
B:The enrollment bootstrap cannot satisfy a compliance grant before enrollment; Microsoft documents this Intune cloud-app exception for this policy pattern.
Incorrect Answers
A:That reproduces the circular requirement preventing the device from becoming compliant.
C:A broad user-wide exclusion removes protection from business applications after enrollment; the narrowly scoped Intune cloud-app exclusion addresses only the bootstrap dependency.
D:A requirement to enroll before the authentication needed to begin enrollment recreates the circular setup dependency rather than resolving it.
Question 104
During fully managed Android setup, work-account sign-in fails under a policy targeting All cloud apps, Android and Browsers with Require compliant device. What is the first policy condition to examine?
- Whether the Google Play listing has a five-star app rating.
- Whether the Microsoft Intune cloud app is included in the compliant-device grant during the initial enrollment authentication.
- Whether the device serial matches the Windows Autopilot hash record.
- Whether a configuration profile sent after enrollment is Succeeded.
Explanation
Correct Answer
B:The newly enrolling device cannot report compliance before it is successfully enrolled.
Incorrect Answers
A:Store reputation does not evaluate Conditional Access compliance grants.
C:Autopilot hardware records are not Android CA bootstrap prerequisites.
D:A post-enrollment policy cannot explain a pre-enrollment sign-in block as directly as the stated grant.
Question 105
After scoping the exception, what acceptance test shows that enrollment works without bypassing application access controls?
- Record that the all-cloud-app policy was disabled for all users.
- Enroll a factory-reset test phone through the Intune sign-in and verify a noncompliant device still cannot access the protected business app.
- Confirm only that Google Play can be browsed anonymously.
- Verify a compliant already-enrolled Android phone can sign in.
Explanation
Correct Answer
B:A successful enrollment sign-in plus a denied resource session differentiates a narrow bootstrap exception from broad CA disabling.
Incorrect Answers
A:That loses the organization’s stated post-enrollment access control.
C:Store connectivity cannot prove Intune enrollment or the business-app grant.
D:An already compliant device avoids the bootstrap scenario under test.
Question 106
A shipping center issues personally owned Android devices to a pilot, while a restriction blocks the older Android device-administrator method. Which enrollment restriction configuration prevents fallback into device administrator without blocking allowed Android Enterprise personal work profiles?
- Block Android Enterprise personally owned work profiles and leave device administrator allowed
- Block Android device administrator in device-platform restrictions while allowing the intended Android Enterprise personal work profile
- Limit enrollment to manufacturer Samsung without selecting a platform
- Require a user to manually remove Company Portal before sign-in
Explanation
Correct Answer
B:Platform restrictions can close the legacy enrollment path while retaining the supported BYOD profile
Incorrect Answers
A:That reverses the intended controls and permits legacy management
C:Manufacturer filtering alone does not prevent the older device-administrator path
D:Uninstalling an app is not an enrollment-platform restriction
Question 107
A shipping center issues personally owned Android devices to a pilot, while a restriction blocks the older Android device-administrator method. An Android handset attempts device administrator instead of its allowed work-profile flow immediately after a new restriction is assigned. Which mechanism should the admin check first?
- An application protection policy has not set a managed pasteboard flag
- The targeted user has an older device-restriction policy at higher priority that still permits the device-administrator platform
- The effective user/group platform restriction or its propagation may still allow the legacy method
- An Intune report displays the previous device name
Explanation
Correct Answer
C:Device-platform restriction assignments, including user-group and filter propagation, determine whether legacy enrollment is blocked
Incorrect Answers
A:MAM pasteboard behavior does not choose the device enrollment protocol
B:Intune applies the higher-priority effective enrollment restriction, but the stem describes a newly assigned restriction and the pilot must check its actual policy priority and propagation rather than presuming an unrelated token expired.
D:Reporting names do not authorize legacy enrollment
Question 108
A shipping center issues personally owned Android devices to a pilot, while a restriction blocks the older Android device-administrator method. Which acceptance test directly demonstrates the desired Android enrollment restriction?
- The group appears in Entra but no device is enrolled
- The Company Portal app launches on an unmanaged phone
- A device configuration profile displays a successful assignment timestamp
- A newly eligible BYOD phone completes work-profile enrollment and a test of the blocked administrator method is rejected for the targeted account
Explanation
Correct Answer
D:Both the allowed and forbidden enrollment paths must behave as the restriction specifies
Incorrect Answers
A:A group object alone cannot show enrollment-path enforcement
B:App launch does not prove the legacy method is blocked
C:Profile assignment does not test device-platform restrictions
Question 109
A corporate-owned Android Enterprise work-profile fleet is being moved from another MDM, while workers must retain approved personal app space. Which preparation meets the corporate-owned work-profile migration prerequisites?
- Enroll the same device in both MDMs with the old work profile still active
- Choose personally owned work-profile enrollment to avoid the reset while labeling the phone corporate
- Assign only an Android application policy without establishing device-owner enrollment
- Remove the previous MDM management and factory-reset devices before Intune corporate-owned work-profile enrollment
Explanation
Correct Answer
D:The corporate-owned work-profile flow requires reset and unsupported dual-MDM enrollment must be removed
Incorrect Answers
A:Simultaneous management is not a supported migration method
B:BYOD enrollment changes the asset-management boundary and does not satisfy the corporate flow
C:App management alone does not onboard the corporate device
Question 110
A corporate-owned Android Enterprise work-profile fleet is being moved from another MDM, while workers must retain approved personal app space. A company-owned test phone stays stuck in its previous work-profile provisioning state after an Intune corporate enrollment profile is created. Which likely missing step explains it?
- The Intune compliant-device report was exported as CSV instead of PDF
- The replacement corporate work-profile enrollment token exists, but the original MDM profile still owns the existing Android work profile
- The phone was not released from old MDM control and factory-reset for the new corporate-owned work-profile enrollment
- A device name contains a hyphen not allowed by Intune
Explanation
Correct Answer
C:Existing MDM enrollment artifacts obstruct the clean corporate ownership flow
Incorrect Answers
A:Export type cannot prevent the device from resetting and enrolling
B:A valid Intune token does not remove the former management profile from an already provisioned device; the corporate-owned migration requires release and an appropriate reset before reenrollment.
D:The stated migration failure is the residual management state, not an identified naming constraint