A parks tablet is assigned the timekeeping app, but install status is pending because the device is off the network. What should verification conclude?
Select an answer to reveal the explanation.
Short Explanation
Pending is "out for delivery," not "returned to sender." The parks tablet is off-network, so UEM has not finished the install. That is not a failed policy and it is not a wipe ticket.
Full Explanation
When a parks tablet is assigned the timekeeping app but install status is pending because the device is off the network, verification should conclude that pending means the assignment has not reached the device yet, not that the install failed. Offline or rarely checked-in devices commonly show pending until connectivity returns. Treating pending as a failed UEM compliance policy and wiping the tablet is destructive and incorrect. Converting the pending install into an App Volumes package so it attaches offline misuses Windows layering for a mobile app state. Pending on a mobile app does not mean Horizon Connection Server rejected a session. Exam caveat: distinguish Pending, Failed, and Installed before changing app packages or wiping civic devices. Operational check: confirm assignment is correct, note last-seen offline, ask parks to bring the tablet online, force check-in, and re-read install status after sync rather than wiping. In municipal EUC operations, record the console path and the rejected alternatives in the change ticket so the next on-call technician repeats the same evidence-first workflow for city staff. Re-validate after the next maintenance window that the same control still holds for the civic tenant.