Question 720
For Seabright Municipal Works, the security review of public-sector records and operations highlights this gap: Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
A qualifying test incident invokes the approved playbook and records its action outcome. This is the relevant proof because it tests whether the selected corrective action (Use supported Sentinel automation rules and playbooks for security orchestration and automated response) addressed the initiating problem (Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path) in Seabright Municipal Works's public-sector records and operations environment, not merely whether a task was marked complete.
Incorrect Answers
A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not. This is useful evidence for a different situation (A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule) and action (Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule). For the reported issue at Seabright Municipal Works, it does not establish the required outcome: A qualifying test incident invokes the approved playbook and records its action outcome.
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 Seabright Municipal Works, it does not establish the required outcome: A qualifying test incident invokes the approved playbook and records its action outcome.
A workbook refresh updates incident trend counts from current workspace data without manual re-entry. This is useful evidence for a different situation (Executives need a dashboard of detection trends but analysts export screenshots and manually recount incidents every week) and action (Build suitable Microsoft Sentinel workbooks over authorized security data and relevant queries). For the reported issue at Seabright Municipal Works, it does not establish the required outcome: A qualifying test incident invokes the approved playbook and records its action outcome.