The clerk of court wants agendas pushed to council iPads and revoked after the meeting. Which UEM capability is that request?
Select an answer to reveal the explanation.
Short Explanation
Council packets should appear for the meeting and vanish afterward, like loaner binders. That is content push and revoke, not installing a new APK.
Full Explanation
Pushing agendas to council iPads and revoking them after the meeting is content distribution and revocation of civic documents. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: Installing an internally signed LOB APK is application management, not agenda revoke-after-meeting. Distractor concept: Entitling a Horizon desktop pool delivers a VDI session, heavier than a meeting packet lifecycle. Distractor concept: Workspace ONE Intelligence custom reports are analytics, not document push/revoke. Exam caveat: "Push then revoke documents" uses content-management verbs; do not answer with apps, VDI pools, or Intelligence. Operational check: Distribute the agenda before the meeting, confirm open on iPads, revoke after adjournment, and verify retention/wipe behavior. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service.