A user reports that a suspicious executable was copied onto their enrolled Windows 11 device this morning. The service desk must have Microsoft Defender Antivirus examine that device using security intelligence no older than the current release, and must drive the work from the Microsoft Intune admin center without anyone at the keyboard of the device. The antivirus policy assigned to the device leaves the option to check for security intelligence before a scan at its default. Which approach meets that requirement?
- ARun the Update Windows Defender security intelligence remote action, confirm from the device action status that it has completed, and then run a scan remote action against the same device. Correct
- BRun the Quick scan remote action on its own, relying on the scan to obtain the current security intelligence before it begins examining the device, which is what a Defender scan does by default.
- CRun the Sync remote action and then the Full scan remote action, relying on the check-in that Sync forces to bring the security intelligence on the device in line with the service before the scan starts.
- DRun the Collect diagnostics remote action and then the Quick scan remote action, relying on the diagnostics package to refresh the Defender components on the device as it gathers the logs.
Why A is correct: Correct. The two remote actions are independent of each other, so sequencing them and checking the first has completed is what guarantees the scan runs against current security intelligence.
Why B is wrong: Tempting because a scan can be made to update first, but that is an antivirus policy option left at its default here, so a scan started on its own may run against whatever definitions the client already holds.
Why C is wrong: Tempting because Sync is the usual way to make a device act immediately, but Intune holds no security intelligence content for a device, so the check-in leaves the definition version exactly where it was.
Why D is wrong: Tempting because Collect diagnostics is the right tool for investigating a Defender fault, but it only gathers logs and configuration for an engineer to download later and changes nothing on the device.