Question 730
For Blue Haven Media, the security review of creative files and production workspaces highlights this gap: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not. This is the relevant proof because it tests whether the selected corrective action (Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule) addressed the initiating problem (A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.
Incorrect Answers
A recent sample identity event is searchable with the expected schema in the connected data source. This is useful evidence for a different situation (A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events) and action (Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace). For the reported issue at Blue Haven Media, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
An incident query joins an identity event and a network event by matching time and entity attributes. This is useful evidence for a different situation (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) and action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations). For the reported issue at Blue Haven Media, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
Only a qualifying test incident launches the playbook and the activity record identifies its run. This is useful evidence for a different situation (A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration) and action (Configure the intended automation rule trigger, conditions and playbook permissions explicitly). For the reported issue at Blue Haven Media, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.