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 73

Question 720

For this case—A SOC architect describes a SIEM dashboard as a complete automated response system despite no defined incident workflow or approvals.—which implementation and acceptance check are correctly paired?

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

Explanation

Correct Answer

D:

The situation is that a SOC architect describes a SIEM dashboard as a complete automated response system despite no defined incident workflow or approvals. 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. The action and test belong together because security information and event management supports detections and investigation, while orchestration and automation can execute governed response steps.

Incorrect Answers

A:

That action-and-evidence pair concerns “use sentinel analytics rules to create actionable incidents”, not this decision. The appropriate action is to use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. To confirm, feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.

B:

The proposed pair focuses on “use sentinel workbooks for investigation visibility” instead. The appropriate action is to use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. To confirm, feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.

C:

“use kql hunting queries over available sentinel logs” evaluates a different intervention. The appropriate action is to use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. To confirm, feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.

Question 721

An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. Which implementation or design choice most directly mitigates the stated issue?

  1. Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.
  2. Use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action.
  3. Use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions.
  4. Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities.

Explanation

Correct Answer

A:

Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. To verify, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

Incorrect Answers

B:

“investigate sentinel incidents using entity context” is related to another task, not the failure shown here. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

C:

This alternative focuses on “distinguish SIEM from soar responsibilities” instead of the required outcome. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

D:

That choice concerns “trigger approved sentinel playbooks through logic apps”, not the immediate requirement. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Question 722

An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. Which technical explanation most directly supports the right approach?

  1. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.
  2. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
  3. A playbook can orchestrate repeatable response steps, but connectors, permissions and approvals must prevent uncontrolled broad action.
  4. An indicator such as a suspicious domain can be useful context but may become stale or overlap legitimate shared infrastructure.

Explanation

Correct Answer

B:

Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. This supports the decision to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.

Incorrect Answers

A:

The principle behind “use sentinel analytics rules to create actionable incidents” is not the one being tested. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

C:

“trigger approved sentinel playbooks through logic apps” explains a different mechanism. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

D:

That statement concerns “use threat intelligence indicators with meaningful scope” rather than the cause in this case. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Question 723

For this situation—An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments.—which check provides the strongest verification?

  1. Import a synthetic indicator with an explicit expiry and demonstrate an investigation query uses its source and confidence appropriately.
  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. Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Explanation

Correct Answer

C:

Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields. It is the relevant test because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Incorrect Answers

A:

“use threat intelligence indicators with meaningful scope” would verify a different part of the system. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

B:

That test concerns “use kql hunting queries over available sentinel logs”, not the requested outcome. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

D:

This evidence addresses “use sentinel analytics rules to create actionable incidents” instead of confirming the repair. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

Question 724

An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. If the team does the following—"Create Sentinel analytics rules for a data source that was never connected and assume the rules can search events stored elsewhere."—what could go wrong?

  1. Security events may remain untriaged while leaders mistake dashboards for active detections and operational controls.
  2. Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention.
  3. Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.
  4. Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

Explanation

Correct Answer

D:

Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on. The shortcut is unsafe because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Incorrect Answers

A:

That consequence concerns “Security events may remain untriaged while leaders mistake dashboards for active detections and operational controls”, which is a different failure. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

B:

“Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention” does not describe the result of this shortcut. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

C:

The alternative risk relates to “Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and…”, not the stated mistake. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

Question 725

An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. Which action and validation evidence belong together?

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

Explanation

Correct Answer

A:

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. The action and test belong together because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Incorrect Answers

B:

“use kql hunting queries over available sentinel logs” evaluates a different intervention. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

C:

The linked action and check for “plan sentinel workspace and retention scope intentionally” would not resolve this case. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

D:

That action-and-evidence pair concerns “use sentinel workbooks for investigation visibility”, not this decision. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

Question 726

An SC-900 learner considers: A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. What is the most appropriate next decision?

  1. Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior.
  2. Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.
  3. Enrich Sentinel investigations with trusted threat intelligence indicators and validate indicator relevance, expiry and confidence before defensive action.
  4. Use Microsoft Sentinel incident timelines, entities and related events to investigate scope and evidence before taking disruptive action.

Explanation

Correct Answer

B:

The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. To verify, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

Incorrect Answers

A:

“use kql hunting queries over available sentinel logs” is related to another task, not the failure shown here. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

C:

That choice concerns “use threat intelligence indicators with meaningful scope”, not the immediate requirement. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

D:

The proposed action addresses “investigate sentinel incidents using entity context” rather than the problem described. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Question 727

A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Why does the recommended approach address this particular concern?

  1. Security information and event management supports detections and investigation, while orchestration and automation can execute governed response steps.
  2. A workbook visualizes available data and investigative trends but is not a substitute for the analytics rules and incident response process.
  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

C:

The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. This supports the decision to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.

Incorrect Answers

A:

“distinguish SIEM from soar responsibilities” describes another technical distinction. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

B:

“use sentinel workbooks for investigation visibility” explains a different mechanism. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

D:

The principle behind “use kql hunting queries over available sentinel logs” is not the one being tested. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Question 728

A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. 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. Feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
  3. Run a bounded KQL query on synthetic sign-in data to find repeated failures by account and confirm counts against the source sample.
  4. Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

Explanation

Correct Answer

D:

The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields. It is the relevant test because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Incorrect Answers

A:

That test concerns “trigger approved sentinel playbooks through logic apps”, not the requested outcome. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

B:

The proposed check is relevant to “distinguish SIEM from soar responsibilities”, but not sufficient here. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

C:

This evidence addresses “use kql hunting queries over available sentinel logs” instead of confirming the repair. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

Question 729

Consider this situation: A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. A team member suggests: "Create Sentinel analytics rules for a data source that was never connected and assume the rules can search events stored elsewhere." What is the main risk?

  1. Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
  2. Legitimate users may be disrupted and the actual compromised identity may remain active if entity evidence is ignored.
  3. Security investigations may be incomplete or too costly, and confidential event data may become accessible to the wrong investigators.
  4. An investigation may incorrectly report no threats because the query targeted the wrong data source or time window.

Explanation

Correct Answer

A:

The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on. The shortcut is unsafe because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Incorrect Answers

B:

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, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

C:

“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, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

D:

That consequence concerns “An investigation may incorrectly report no threats because the query targeted the wrong data source or…”, which is a different failure. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.

Question 730

A security and compliance reviewer considers: A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. 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 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: 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.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. 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. The action and test belong together because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.

Incorrect Answers

A:

“distinguish SIEM from soar responsibilities” evaluates a different intervention. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

C:

The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. That action-and-evidence pair concerns “use sentinel workbooks for investigation visibility”, not this decision. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

D:

The proposed pair focuses on “plan sentinel workspace and retention scope intentionally” instead. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.

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