A county must patch Windows devices used by building inspectors without interrupting daytime field work. Which Workspace ONE assignment is appropriate?
Select an answer to reveal the explanation.
Short Explanation
Inspectors are a named crew, not the whole county. Aim the patch at their Windows smart group and force the reboot after hours, not at the inspection counter.
Full Explanation
A county patching Windows devices used by building inspectors without interrupting daytime field work should publish the patch to the Inspectors – Windows smart group with a deadline and an after-hours force-reboot window. Treat the after-hours window as the inspectors' overnight garage time so field tablets are not force-rebooted mid-inspection. Assigning the patch to all county devices immediately with a forced midday reboot fails by concept because it widens blast radius beyond inspectors and interrupts daytime field work. Publishing the patch only to the NSX-T Inspectors security group fails because NSX security groups enforce overlay firewall membership, not UEM patch assignment. Emailing a KB article and relying on inspectors to self-install before the next permit surge fails because voluntary self-install is not managed patch assignment with reporting. Exam caveat: UEM smart-group assignment with deadline and after-hours reboot is the appropriate operational pattern for field Windows devices. Operational check: target the Inspectors – Windows smart group, set deadline and after-hours force reboot, verify compliance without midday field disruption, and document the window in the county field-device patch standard.