Building inspectors must meet a Workspace ONE UEM compliance policy. What should the operator verify in the UEM dashboard?
Select an answer to reveal the explanation.
Short Explanation
This is a clipboard check, not building a new jail. Confirm the policy is pinned to inspectors and that a sample phone reads Compliant or Not Compliant. Writing NSX rules or Horizon payloads is a different exam.
Full Explanation
Building inspectors must meet a Workspace ONE UEM compliance policy, so the operator verifies that the policy is assigned to inspectors and that a sample phone shows Currently Compliant or Not Compliant in the UEM compliance view. Assignment proves scope; sample device status proves evaluation outcome for civic field staff. Authoring a new NSX quarantine security policy for inspector virtual machines addresses datacenter micro-segmentation, not UEM mobile compliance evaluation. Rewriting the compliance payload from Horizon Console desktop-pool settings confuses VDI pool configuration with MDM compliance. Converting the rule into an App Volumes package assignment delivers Windows apps, not mobile compliance posture. Exam caveat: Not Compliant is useful evidence—do not immediately redesign the entire policy estate before reading why the sample failed. Operational check: open the inspectors' compliance policy in UEM, confirm smart-group assignment, open a sample inspector phone, record Compliant or Not Compliant with the failing rule if any, and remediate based on that evidence. 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.