Endpoint Administrator MD-102 Practice Test 9
Question 80
During Device Administrator-to-work-profile migration, a user selects Resolve but work-profile creation fails. The phone supports the feature and Company Portal is current. Enrollment restrictions explicitly block personally owned Android Enterprise work profiles. What must change?
- Allow the intended users to enroll personally owned Android Enterprise work profiles, then repeat the migration flow
- Increase the Android device enrollment limit to accommodate the migrating users
- Remove the work-profile enrollment assignment and hope existing legacy Device Administrator policy migrates automatically
- Reset the device as a dedicated kiosk without investigating the restriction
Explanation
Correct Answer
A:The migration guide identifies blocked work-profile enrollment as a direct cause of Resolve failure; the platform restriction must permit this enrollment before the profile can be created.
Incorrect Answers
B:The error is an ownership/platform restriction on work profiles, not the number of devices each user may enroll.
C:Removing the intended enrollment path does not override the platform restriction blocking work-profile creation.
D:Dedicated enrollment changes the device model and leaves the explicit BYOD enrollment block unresolved.
Question 81
After the migration, a technician needs to confirm work-data separation without reading personal content. Which evidence is strongest?
- Company Portal still appears in the app drawer but no work-profile boundary can be found
- The old Device Administrator management is removed, a separate managed Android work profile exists, and managed apps/policies operate inside it
- The user can open a personal photo while the legacy enrollment remains active
- Company Portal reports a successful sync but still labels the device as Device Administrator managed
Explanation
Correct Answer
B:This checks the removal of the legacy management mode and the resulting supported work-profile boundary, not merely an account sign-in.
Incorrect Answers
A:App installation alone does not show that the Android Enterprise profile was created.
C:Personal access does not prove completion of the planned migration.
D:A completed device check-in is not evidence that the new Android Enterprise work profile replaced legacy management.
Question 82
An existing Intune Android Enterprise dedicated-device enrollment profile is used by warehouse scanners. Its QR enrollment token is approaching expiration, while deployed scanners are healthy. What is the scoped administrative action?
- Retire all deployed scanners and recreate every device record
- Replace the expiring enrollment token in the existing dedicated-device profile and distribute the replacement securely to technicians
- Convert the profile to Android personally owned work profile enrollment
- Post the old QR token on a public instructions page until its expiry
Explanation
Correct Answer
B:Intune offers a Replace token action for dedicated enrollment profiles; it renews the bootstrap credential without changing healthy devices to another ownership mode.
Incorrect Answers
A:Token renewal for future enrollment does not require retiring functioning managed devices.
C:User-affiliated BYOD is not suitable for these userless corporate scanners.
D:Exposing the bootstrap enrollment credential creates an avoidable authorization risk and does not renew it.
Question 83
The help desk says a dedicated Android enrollment profile disappeared from the standard profile list immediately after its token expired. Which check most directly distinguishes expiration from deletion?
- Filter only Active Android dedicated enrollment profiles and conclude the previous token was deleted
- In Android dedicated enrollment profiles, include Inactive policy states in the filter and inspect the expired profile/token
- Check the policy assignment to an existing scanner but not the enrollment profile state
- Remove the company Android kiosk app from Managed Google Play
Explanation
Correct Answer
B:Microsoft states that expired-token profiles disappear from the default view and can be seen when active and inactive policy-state filters are selected.
Incorrect Answers
A:The default active view hides a profile whose enrollment token has expired; filter Inactive to inspect it.
C:Assignment to a device already enrolled does not identify the inactive dedicated enrollment token.
D:Application assignment does not recover an inactive enrollment profile from the filter.
Question 84
A warehouse replaced its dedicated Android token and issued a new QR code. Which acceptance test distinguishes successful token recovery from a merely saved configuration?
- An already enrolled scanner retains its existing wallpaper
- The token replacement button is no longer highlighted in the portal
- A new factory-reset test scanner enrolls using the replacement QR code, appears under the intended dedicated profile and receives its kiosk policy
- An existing kiosk stays online and launches the warehouse app after its original enrollment
Explanation
Correct Answer
C:Fresh device enrollment using the replacement credential and expected policy verifies the bootstrap path end to end.
Incorrect Answers
A:Previously enrolled device state does not test a new QR token.
B:A control-state change alone does not show the replacement credential is usable.
D:Current operation of a previously enrolled kiosk is not a test of new enrollment using the replaced QR credential.
Question 85
A reseller preprovisions corporate-owned Android 13 phones with fully managed staging tokens. The tenant also requires static group membership to exist at enrollment time for first-check-in app assignments. Which enrollment design meets the group requirement?
- Keep the staging token and add a group to its profile.
- Use the default fully managed enrollment token with supported enrollment-time grouping instead of the staging-token flow.
- Switch to an Android dedicated device token and keep each phone personally assigned.
- Wait for Entra dynamic membership to process before starting the device setup wizard.
Explanation
Correct Answer
B:The staging token supports preprovisioning, but enrollment-time grouping is not supported with that token type; the default token supports the specified grouping.
Incorrect Answers
A:A staging enrollment token does not support enrollment-time grouping regardless of the later group selection.
C:Dedicated userless enrollment is a different ownership and user-affinity model, not a group-targeting remedy.
D:Delayed dynamic membership does not supply the specifically requested enrollment-time group capability.
Question 86
A pilot phone enrolls with the corporate fully managed staging token, but the first-check-in group required by the deployment policy is absent even though the group exists. Which cause is most consistent with the configured token?
- The reseller accidentally selected an app-version update channel.
- The staging token does not support enrollment-time grouping; the team selected a token flow incompatible with its requirement.
- The dynamic group name has too many characters for Android 13.
- The user has not installed Microsoft Outlook.
Explanation
Correct Answer
B:The token limitation explains why waiting for a staging-device group assignment is not a valid fix.
Incorrect Answers
A:App update channels do not determine enrollment-time grouping availability.
C:The restriction here concerns the token type, not a specified group-name character limit.
D:Outlook installation does not enable enrollment-time grouping for staging tokens.
Question 87
After selecting the default fully managed token, how should the team prove that the required static device group membership is established during enrollment?
- Show a screenshot of the reseller’s staging token name.
- Check only that the company Android app appeared in Managed Google Play.
- Enroll a new pilot device with the default token and check its selected static Entra device group membership and first-check-in policy assignment.
- Verify that the manufacturer serial number is present in the procurement file.
Explanation
Correct Answer
C:The pilot must demonstrate actual group membership and required policy arrival, not merely the existence of a group.
Incorrect Answers
A:A staging token label cannot prove membership through the compatible default token flow.
B:App catalog visibility does not verify membership or first-check-in policy targeting.
D:Inventory records do not show group evaluation during Intune enrollment.
Question 88
A factory provisions RealWear AOSP headsets without Google Mobile Services. Its userless enrollment QR code expires after a 90-day rollout and includes staging Wi-Fi credentials. Which provisioning practice is supported and reduces exposure?
- Replace the AOSP enrollment QR token before expiry and use a limited-access staging Wi-Fi network for the embedded credentials.
- Reuse the expired QR and rely on the Company Portal sign-in to refresh it.
- Send the QR with production network administrator credentials to each vendor.
- Use the plain-text token string generated beside the QR to enroll the headset.
Explanation
Correct Answer
A:The AOSP token has a maximum 90-day validity and its QR contents can carry Wi-Fi credentials in clear text.
Incorrect Answers
B:Expired AOSP enrollment tokens are not renewed by a user sign-in; these devices enroll without a user.
C:The QR may contain network secrets; putting broad production credentials in it increases risk.
D:For this AOSP userless flow, Microsoft documents that the plain-text token cannot be used for enrollment.
Question 89
New userless AOSP headsets stop enrolling, but already enrolled units keep checking in. The QR token is older than 90 days and the vendor used the exported plain-text token. What is the primary enrollment failure?
- The AOSP enrollment token has expired, and the vendor must scan a valid enrollment QR rather than use its unusable plain-text token.
- Previously enrolled headsets automatically lose their Entra shared-device identities when a token expires.
- The kiosk app must be changed to an Apple user enrollment app.
- AOSP enrollment fails because it requires Google Mobile Services.
Explanation
Correct Answer
A:Token replacement applies to new enrollment without removing previously enrolled devices.
Incorrect Answers
B:Existing enrollment is not invalidated by rotating the token; the failure affects new enrollments.
C:App vendor selection is unrelated to an expired Android AOSP enrollment QR.
D:The AOSP userless management method expressly supports devices without Google Mobile Services.
Question 90
After replacing the token and staging network, which combined result confirms new AOSP enrollment and protects the production Wi-Fi boundary?
- Existing headsets continue to check in using their previous token.
- The QR export downloads successfully without testing a reset headset.
- The production Wi-Fi password appears in the QR JSON export.
- A newly reset headset scans the new QR, enters Intune userless/shared-device management, and connects using staging-only Wi-Fi credentials.
Explanation
Correct Answer
D:This verifies the actual enrollment mode and limits the plaintext Wi-Fi exposure contained in the QR.
Incorrect Answers
A:Old check-ins do not test the newly issued QR or new equipment enrollment.
B:Export success does not attest the device can enroll or connect on the network.
C:Exposing the production credential demonstrates the risk, not a compliant staging-network deployment.