Question 510
A regulated Azure tenant has this security condition: A security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel. Which configuration change most directly resolves this problem?
Explanation
Correct Answer
The cause is: A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The appropriate change is: Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content. Verify it with this outcome: The workspace exposes Sentinel analytics, incident management and authorized security content appropriately.
Incorrect Answers
This action concerns sentinel automation rule order and stop processing, where Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The reported incident instead involves A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.
This action concerns azure monitor transformation for sensitive fields, where Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The corrective response here is “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content”; this alternative does not provide that response.
This action concerns sentinel threat intelligence indicator freshness, where Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. The stem reports a security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel; this control addresses a different failure condition.