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 76

Question 750

For this case—A responder proposes blocking an entire office subnet based on one Sentinel alert without checking its correlated incident details.—which implementation and acceptance check are correctly paired?

  1. Action: Choose an appropriate Log Analytics and Sentinel workspace topology with ingestion, access, retention and cost requirements documented. Validation: Verify synthetic events from required subscriptions appear in the intended workspace and that an unauthorized analyst cannot query sensitive log categories.
  2. 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.
  3. Action: Use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. Validation: Feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a responder proposes blocking an entire office subnet based on one Sentinel alert without checking its correlated incident details. 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. The action and test belong together because incident correlation links account, host, IP and alert information, helping analysts distinguish one attack from unrelated background events.

Incorrect Answers

A:

“plan sentinel workspace and retention scope intentionally” evaluates a different intervention. The appropriate action is to use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action. To confirm, review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.

C:

That action-and-evidence pair concerns “distinguish SIEM from soar responsibilities”, not this decision. The appropriate action is to use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action. To confirm, review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.

D:

The proposed pair focuses on “use threat intelligence indicators with meaningful scope” instead. The appropriate action is to use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action. To confirm, review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.

Question 751

An incident responder wants to identify users with repeated failed logins in one hour from an unfamiliar IP range. Which implementation or design choice most directly mitigates the stated issue?

  1. Choose an appropriate Log Analytics and Sentinel workspace topology with ingestion, access, retention and cost requirements documented.
  2. Use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action.
  3. Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior.
  4. Enrich Sentinel investigations with trusted threat intelligence indicators and validate indicator relevance, expiry and confidence before defensive action.

Explanation

Correct Answer

C:

Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing. To verify, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Incorrect Answers

A:

This alternative focuses on “plan sentinel workspace and retention scope intentionally” instead of the required outcome. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

B:

That choice concerns “investigate sentinel incidents using entity context”, not the immediate requirement. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

D:

“use threat intelligence indicators with meaningful scope” is related to another task, not the failure shown here. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Question 752

An incident responder wants to identify users with repeated failed logins in one hour from an unfamiliar IP range. Which technical explanation most directly supports the right approach?

  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. Incident correlation links account, host, IP and alert information, helping analysts distinguish one attack from unrelated background events.
  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

D:

KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing. This supports the decision to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior.

Incorrect Answers

A:

“trigger approved sentinel playbooks through logic apps” explains a different mechanism. Here, KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

B:

That statement concerns “distinguish SIEM from soar responsibilities” rather than the cause in this case. Here, KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

C:

The principle behind “investigate sentinel incidents using entity context” is not the one being tested. Here, KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Question 753

For this situation—An incident responder wants to identify users with repeated failed logins in one hour from an unfamiliar IP range.—which check provides the strongest verification?

  1. Run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.
  2. Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
  3. Populate a test workbook from known sample incidents and compare its totals to the underlying query results and workspace timeframe.
  4. Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Explanation

Correct Answer

A:

Run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample. It is the relevant test because KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Incorrect Answers

B:

This evidence addresses “connect relevant Microsoft sentinel data sources” instead of confirming the repair. To check this result, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

C:

“use sentinel workbooks for investigation visibility” would verify a different part of the system. To check this result, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

D:

That test concerns “use sentinel analytics rules to create actionable incidents”, not the requested outcome. To check this result, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Question 754

An incident responder wants to identify users with repeated failed logins in one hour from an unfamiliar IP range. If the team does the following—"Search a nonexistent Sentinel table and conclude there were no suspicious logins without checking ingestion or schema."—what could go wrong?

  1. Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention.
  2. An investigation may incorrectly report no threats because the query targeted the wrong data source or time window.
  3. Security events may remain untriaged while leaders mistake dashboards for active detections and operational controls.
  4. Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

Explanation

Correct Answer

B:

An investigation may incorrectly report no threats because the query targeted the wrong data source or time window. The shortcut is unsafe because KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Incorrect Answers

A:

The alternative risk relates to “Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention”, not the stated mistake. Here, an investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

C:

That consequence concerns “Security events may remain untriaged while leaders mistake dashboards for active detections and operational controls”, which is a different failure. Here, an investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

D:

“Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned…” does not describe the result of this shortcut. Here, an investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

Question 755

An incident responder wants to identify users with repeated failed logins in one hour from an unfamiliar IP range. Which action and validation evidence belong together?

  1. 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.
  2. 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.
  3. 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.
  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

C:

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. The action and test belong together because KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Incorrect Answers

A:

The linked action and check for “use sentinel analytics rules to create actionable incidents” would not resolve this case. The appropriate action is to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. To confirm, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

B:

That action-and-evidence pair concerns “investigate sentinel incidents using entity context”, not this decision. The appropriate action is to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. To confirm, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

D:

“trigger approved sentinel playbooks through logic apps” evaluates a different intervention. The appropriate action is to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. To confirm, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Question 756

During a Microsoft security fundamentals review, A junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. What is the most appropriate next decision?

  1. Use supported Microsoft Defender XDR automated investigation and response features with appropriate evidence review and action controls.
  2. Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data.
  3. Build a Microsoft Sentinel workbook using supported queries and visual components for the specific metrics a security team needs.
  4. Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior.

Explanation

Correct Answer

D:

The situation is that a junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing. To verify, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Incorrect Answers

A:

That choice concerns “use coordinated defender xdr investigation without blind automatic remediation”, not the immediate requirement. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

B:

The proposed action addresses “use sentinel analytics rules to create actionable incidents” rather than the problem described. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

C:

“use sentinel workbooks for investigation visibility” is related to another task, not the failure shown here. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Question 757

A junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. Why does the recommended approach address this particular concern?

  1. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.
  2. Workspace scope determines which events can be queried together, who may investigate them and how much ingestion and retention cost is incurred.
  3. A workbook visualizes available data and investigative trends but is not a substitute for the analytics rules and incident response process.
  4. Incident correlation links account, host, IP and alert information, helping analysts distinguish one attack from unrelated background events.

Explanation

Correct Answer

A:

The situation is that a junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing. This supports the decision to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior.

Incorrect Answers

B:

The principle behind “plan sentinel workspace and retention scope intentionally” is not the one being tested. Here, KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

C:

“use sentinel workbooks for investigation visibility” describes another technical distinction. Here, KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

D:

“investigate sentinel incidents using entity context” explains a different mechanism. Here, KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Question 758

A junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. Which evidence best validates the proposed outcome?

  1. Review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.
  2. Run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.
  3. Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
  4. Import a synthetic indicator with an explicit expiry and demonstrate an investigation query uses its source and confidence appropriately.

Explanation

Correct Answer

B:

The situation is that a junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. Run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample. It is the relevant test because KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Incorrect Answers

A:

This evidence addresses “investigate sentinel incidents using entity context” instead of confirming the repair. To check this result, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

C:

That test concerns “connect relevant Microsoft sentinel data sources”, not the requested outcome. To check this result, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

D:

The proposed check is relevant to “use threat intelligence indicators with meaningful scope”, but not sufficient here. To check this result, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Question 759

Consider this situation: A junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. A team member suggests: "Search a nonexistent Sentinel table and conclude there were no suspicious logins without checking ingestion or schema." 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. An investigation may incorrectly report no threats because the query targeted the wrong data source or time window.
  4. Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

Explanation

Correct Answer

C:

The situation is that a junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. An investigation may incorrectly report no threats because the query targeted the wrong data source or time window. The shortcut is unsafe because KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Incorrect Answers

A:

“Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned…” can arise elsewhere, but it is not the most direct risk here. Here, an investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

B:

That consequence concerns “Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and…”, which is a different failure. Here, an investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

D:

The alternative risk relates to “Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend…”, not the stated mistake. Here, an investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

Question 760

A security and compliance reviewer considers: A junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. Which response and evidence should be linked?

  1. Action: Use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. Validation: Feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
  2. 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.
  3. 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.
  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

D:

The situation is that a junior analyst filters the wrong timestamp column in a Sentinel workspace and announces a clean security report. 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. The action and test belong together because KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.

Incorrect Answers

A:

That action-and-evidence pair concerns “distinguish SIEM from soar responsibilities”, not this decision. The appropriate action is to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. To confirm, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

B:

The proposed pair focuses on “trigger approved sentinel playbooks through logic apps” instead. The appropriate action is to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. To confirm, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

C:

“use threat intelligence indicators with meaningful scope” evaluates a different intervention. The appropriate action is to query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior. To confirm, run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.

Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests