The CIO wants Monday's packet of non-compliant city devices as a reusable Intelligence artifact, not a one-off click through a UEM list. What should the operator generate?
Select an answer to reveal the explanation.
Short Explanation
Monday's CIO packet is a report, not a sticky note from one UEM screen. Intelligence is the civic briefing machine for non-compliant devices.
Full Explanation
When the CIO wants Monday's packet of non-compliant city devices as a reusable Intelligence artifact—not a one-off click through a UEM list—the operator should generate a Workspace ONE Intelligence report of non-compliant devices. Intelligence reports are designed to be saved, scheduled, and shared as analytics artifacts across the civic tenant. A screenshot of the Horizon Help Desk session grid captures VDI sessions, not device compliance populations. Authoring a brand-new UEM compliance payload from scratch creates policy, not a reusable compliance report. An NSX Distributed Firewall export is a network policy artifact, not an endpoint compliance report. Exam caveat: UEM lists are fine for break-fix; Intelligence is the exam answer when leadership asks for a reusable analytics report. Operational check: in Intelligence, build a non-compliant devices report, save it, run for Monday's window, export for the CIO packet, and optionally schedule weekly recurrence. 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.