Question 640
An administrator is assessing this problem: An incident analyst wants to know which machines and users are associated with several alerts returned from advanced hunting. Which information supports a defensible investigation?
Explanation
Correct Answer
Compare the relevant AlertInfo and AlertEvidence join keys and resulting entity rows. The case concerns correlate alertinfo with alertevidence: An incident analyst wants to know which machines and users are associated with several alerts returned from advanced hunting. Evidence tables make alert-to-entity attribution possible when the correct keys are used. This answers the evidence needed to discriminate between possible causes because it addresses the explicit constraint. That evidence tests the underlying interpretation: advanced hunting alert metadata and entity evidence can be correlated by appropriate alert identifiers. It is more discriminating than unrelated service indicators.
Incorrect Answers
Incident correlation unifies security evidence across Defender workloads when signals relate. The reason this does not settle the present case is the actual condition: Advanced hunting alert metadata and entity evidence can be correlated by appropriate alert identifiers.
Incident prioritization should weigh credible impact, exposure, and evidence. The current corrective requirement is: Join alert metadata with related evidence to enumerate affected users and endpoints.
Advanced hunting supports proactive evidence discovery but does not independently remediate threats. The appropriate acceptance check is: The query returns coherent alert/entity associations rather than a duplicated unrelated Cartesian set.