Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

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?

  1. Action: 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.
  2. Action: 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.
  3. Action: Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. Validation: Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
  4. Action: Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. Validation: Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Explanation

Correct Answer

B:

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

A:

“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.

C:

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.

D:

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?

  1. Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.
  2. Enable applicable Defender for Servers protection for eligible machines and review its supported endpoint vulnerability and attack monitoring coverage.
  3. Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities.
  4. Build a Microsoft Sentinel workbook using supported queries and visual components for the specific metrics a security team needs.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

“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?

  1. A workbook visualizes available data and investigative trends but is not a substitute for the analytics rules and incident response process.
  2. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.
  3. Security information and event management supports detections and investigation, while orchestration and automation can execute governed response steps.
  4. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.

Explanation

Correct Answer

D:

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

A:

“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.

B:

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.

C:

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?

  1. Trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
  2. Review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.
  3. Feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
  4. Verify synthetic events from required subscriptions appear in the intended workspace and that an unauthorized analyst cannot query sensitive log categories.

Explanation

Correct Answer

A:

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

B:

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.

C:

“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.

D:

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?

  1. Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.
  2. Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
  3. Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention.
  4. Threats may remain active despite centralized event storage when detection, triage and remediation are not connected.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

“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?

  1. Action: Enrich Sentinel investigations with trusted threat intelligence indicators and validate indicator relevance, expiry and confidence before defensive action. Validation: Import a synthetic indicator with an explicit expiry and demonstrate an investigation query uses its source and confidence appropriately.
  2. Action: Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. Validation: Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.
  3. Action: 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.
  4. Action: Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. Validation: Run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

“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?

  1. Use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action.
  2. Use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions.
  3. Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data.
  4. Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

“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?

  1. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
  2. Security information and event management supports detections and investigation, while orchestration and automation can execute governed response steps.
  3. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
  4. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Explanation

Correct Answer

A:

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

B:

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.

C:

“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.

D:

“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?

  1. Deliver a vendor-provided harmless attachment test case to a sandbox mailbox and verify the policy disposition and alert are captured.
  2. Trigger a harmless lab incident and verify its playbook creates the intended test ticket without modifying unrelated production accounts.
  3. Import a synthetic indicator with an explicit expiry and demonstrate an investigation query uses its source and confidence appropriately.
  4. Review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Security investigations may be incomplete or too costly, and confidential event data may become accessible to the wrong investigators.
  2. Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.
  3. Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
  4. Legitimate users may be disrupted and the actual compromised identity may remain active if entity evidence is ignored.

Explanation

Correct Answer

C:

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

A:

“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.

B:

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.

D:

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?

  1. Action: Enrich Sentinel investigations with trusted threat intelligence indicators and validate indicator relevance, expiry and confidence before defensive action. Validation: Import a synthetic indicator with an explicit expiry and demonstrate an investigation query uses its source and confidence appropriately.
  2. Action: Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. Validation: Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
  3. Action: Use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action. Validation: Review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.
  4. Action: 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

“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