Transit dispatch phones that fail passcode complexity should receive an email and then an enterprise wipe after a grace period. Which compliance design matches that response?
Select an answer to reveal the explanation.
Short Explanation
Compliance actions are a warning ticket then a tow, not a wrecking ball on the first miss. Email first, grace period, then enterprise wipe. Instant unenroll on one fail is a valid action, but it is not the escalating pattern transit asked for.
Full Explanation
Workspace ONE UEM compliance policies support sequenced actions such as email notification, application block, and enterprise wipe after a defined grace period. That escalation is how administrators give users time to fix passcode complexity before destructive action. Immediate unenroll on first failure is harsher than requested. NSX-T time-based firewall rules and Carbon Black Cloud isolation do not implement UEM passcode-compliance wipe workflows.