Microsoft SC-900 Dumps
Microsoft SC-900 Practice Test 78
Question 770
An organization deploys a Sentinel dashboard for executive reporting but omits the rules required to raise high-priority incidents. Which action and validation evidence belong together?
Explanation
Correct Answer
The situation is that an organization deploys a Sentinel dashboard for executive reporting but omits the rules required to raise high-priority incidents. Build a Microsoft Sentinel workbook using supported queries and visual components for the specific metrics a security team needs. Validation: Populate a test workbook from known sample incidents and compare its totals to the underlying query results and workspace timeframe. The action and test belong together because a workbook visualizes available data and investigative trends but is not a substitute for the analytics rules and incident response process.
Incorrect Answers
“trigger approved sentinel playbooks through logic apps” evaluates a different intervention. The appropriate action is to build a Microsoft Sentinel workbook using supported queries and visual components for the specific metrics a security team needs. To confirm, populate a test workbook from known sample incidents and compare its totals to the underlying query results and workspace timeframe.
That action-and-evidence pair concerns “connect relevant Microsoft sentinel data sources”, not this decision. The appropriate action is to build a Microsoft Sentinel workbook using supported queries and visual components for the specific metrics a security team needs. To confirm, populate a test workbook from known sample incidents and compare its totals to the underlying query results and workspace timeframe.
The proposed pair focuses on “use sentinel analytics rules to create actionable incidents” instead. The appropriate action is to build a Microsoft Sentinel workbook using supported queries and visual components for the specific metrics a security team needs. To confirm, populate a test workbook from known sample incidents and compare its totals to the underlying query results and workspace timeframe.
Question 771
During a tenant protection and compliance review, A SOC wants to open an incident ticket and alert an on-call engineer automatically when a confirmed high-severity detection arrives. What is the most appropriate next decision?
Explanation
Correct Answer
Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action. To verify, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
Incorrect Answers
This alternative focuses on “connect relevant Microsoft sentinel data sources” instead of the required outcome. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
That choice concerns “use defender for servers for eligible server workload protection”, not the immediate requirement. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
“use sentinel workbooks for investigation visibility” is related to another task, not the failure shown here. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Question 772
A SOC wants to open an incident ticket and alert an on-call engineer automatically when a confirmed high-severity detection arrives. Why does the recommended approach address this particular concern?
Explanation
Correct Answer
A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action. This supports the decision to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities.
Incorrect Answers
“use sentinel workbooks for investigation visibility” explains a different mechanism. Here, a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
That statement concerns “use kql hunting queries over available sentinel logs” rather than the cause in this case. Here, a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
The principle behind “distinguish SIEM from soar responsibilities” is not the one being tested. Here, a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Question 773
A SOC wants to open an incident ticket and alert an on-call engineer automatically when a confirmed high-severity detection arrives. Which evidence best validates the proposed outcome?
Explanation
Correct Answer
Trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts. It is the relevant test because a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Incorrect Answers
This evidence addresses “investigate sentinel incidents using entity context” instead of confirming the repair. To check this result, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
“distinguish SIEM from soar responsibilities” would verify a different part of the system. To check this result, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
That test concerns “plan sentinel workspace and retention scope intentionally”, not the requested outcome. To check this result, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
Question 774
Consider this situation: A SOC wants to open an incident ticket and alert an on-call engineer automatically when a confirmed high-severity detection arrives. A team member suggests: "Give a Sentinel playbook unrestricted tenant admin permissions to block all users whenever any low-severity alert appears." What is the main risk?
Explanation
Correct Answer
Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested. The shortcut is unsafe because a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Incorrect Answers
The alternative risk relates to “Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned…”, not the stated mistake. Here, automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
That consequence concerns “Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention”, which is a different failure. Here, automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
“Threats may remain active despite centralized event storage when detection, triage and remediation are not connected” does not describe the result of this shortcut. Here, automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
Question 775
A security and compliance reviewer considers: A SOC wants to open an incident ticket and alert an on-call engineer automatically when a confirmed high-severity detection arrives. Which response and evidence should be linked?
Explanation
Correct Answer
Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. Validation: Trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts. The action and test belong together because a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Incorrect Answers
The linked action and check for “use threat intelligence indicators with meaningful scope” would not resolve this case. The appropriate action is to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. To confirm, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
That action-and-evidence pair concerns “use sentinel analytics rules to create actionable incidents”, not this decision. The appropriate action is to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. To confirm, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
“use kql hunting queries over available sentinel logs” evaluates a different intervention. The appropriate action is to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. To confirm, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
Question 776
An analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. Which action best addresses this requirement?
Explanation
Correct Answer
The situation is that an analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action. To verify, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
Incorrect Answers
That choice concerns “investigate sentinel incidents using entity context”, not the immediate requirement. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
The proposed action addresses “distinguish SIEM from soar responsibilities” rather than the problem described. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
“use sentinel analytics rules to create actionable incidents” is related to another task, not the failure shown here. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Question 777
A cloud security learner considers: An analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. Which underlying principle applies?
Explanation
Correct Answer
The situation is that an analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action. This supports the decision to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities.
Incorrect Answers
The situation is that an analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. The principle behind “distinguish SIEM from soar responsibilities” is not the one being tested. Here, a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
“connect relevant Microsoft sentinel data sources” describes another technical distinction. Here, a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
“use kql hunting queries over available sentinel logs” explains a different mechanism. Here, a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Question 778
An analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. What should the team examine before accepting the result?
Explanation
Correct Answer
The situation is that an analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. Trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts. It is the relevant test because a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Incorrect Answers
This evidence addresses “use safe attachments to analyze suspicious message files” instead of confirming the repair. To check this result, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
That test concerns “use threat intelligence indicators with meaningful scope”, not the requested outcome. To check this result, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
The proposed check is relevant to “investigate sentinel incidents using entity context”, but not sufficient here. To check this result, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
Question 779
An analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. The proposed shortcut is: "Give a Sentinel playbook unrestricted tenant admin permissions to block all users whenever any low-severity alert appears." Which failure is most likely?
Explanation
Correct Answer
The situation is that an analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested. The shortcut is unsafe because a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Incorrect Answers
“Security investigations may be incomplete or too costly, and confidential event data may become accessible to…” can arise elsewhere, but it is not the most direct risk here. Here, automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
That consequence concerns “Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned…”, which is a different failure. Here, automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
The alternative risk relates to “Legitimate users may be disrupted and the actual compromised identity may remain active if entity evidence…”, not the stated mistake. Here, automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
Question 780
For this case—An analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step.—which implementation and acceptance check are correctly paired?
Explanation
Correct Answer
The situation is that an analyst creates a playbook that disables every account mentioned by any alert without requiring severity checks or an approval step. Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. Validation: Trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts. The action and test belong together because a playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
Incorrect Answers
That action-and-evidence pair concerns “use threat intelligence indicators with meaningful scope”, not this decision. The appropriate action is to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. To confirm, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
The proposed pair focuses on “connect relevant Microsoft sentinel data sources” instead. The appropriate action is to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. To confirm, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
“investigate sentinel incidents using entity context” evaluates a different intervention. The appropriate action is to use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities. To confirm, trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests
- Microsoft SC-900 Practice Test 76 - 10 Questions (Last Reviewed 02-Nov-2026)
- Microsoft SC-900 Practice Test 77 - 10 Questions (Last Reviewed 01-Nov-2026)
- Microsoft SC-900 Practice Test 78 - 10 Questions (Last Reviewed 31-Oct-2026)
- Microsoft SC-900 Practice Test 79 - 10 Questions (Last Reviewed 30-Oct-2026)
- Microsoft SC-900 Practice Test 80 - 10 Questions (Last Reviewed 29-Oct-2026)