Question 70
A KQL query flags a common legitimate updater as suspicious due to process name alone. Which verification outcome matches the stated business and security goal?
Explanation
Correct Answer
The accepted outcome directly tests the required feature. Process-name-only matching has poor specificity. Specifically, legitimate updater events are excluded while malicious test behavior remains detected.
Incorrect Answers
For “An analyst needs evidence of which accounts performed suspicious file downloads from a cloud app”, “The result identifies users, files, and download timestamps” is appropriate on this basis: Cloud application events provide different evidence from endpoint process data. The required result for the present question is “Legitimate updater events are excluded while malicious test behavior remains detected”.
This would validate build a KQL join on supported device and process correlation fields. in another situation. The present scenario instead needs proof that legitimate updater events are excluded while malicious test behavior remains detected.
“A representative test event triggers the configured detection rule” verifies the separate situation “A threat hunter wants to turn a tested malicious-pattern query into proactive detection”. The technical basis is: Custom detections can promote query logic into repeatable alerts. Here the required result is “Legitimate updater events are excluded while malicious test behavior remains detected”; the alternate check alone cannot establish it.