Question 250
A KQL query flags a common legitimate updater as suspicious due to process name alone. What should the Microsoft 365 administrator implement to address this situation?
Explanation
Correct Answer
The matching Microsoft 365 administration decision is add contextual command line, signer, and lineage conditions to the query. The underlying principle is Process-name-only matching has poor specificity. Check: legitimate updater events are excluded while malicious test behavior remains detected.
Incorrect Answers
This other action addresses a different situation: security engineers want to match a malicious file hash to endpoint telemetry. Its technical purpose is Hash-based hunting ties a known artifact to executed or created files. The current task instead requires legitimate updater events are excluded while malicious test behavior remains detected.
This would focus on defender advanced hunting returns no events and an admin assumes all endpoints are clean. rather than the present constraint. No query results may indicate missing telemetry rather than safety. The required success state remains legitimate updater events are excluded while malicious test behavior remains detected.
Although relevant to an analyst writes an advanced hunting query with invalid table names and obtains errors., it does not establish the requested outcome. Table and column names vary by event surface and must be valid. Here the measurable requirement is legitimate updater events are excluded while malicious test behavior remains detected.