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 74

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.

Question 731

A SOC wants an incident when a test account triggers repeated failed logins followed by an unusual successful access. Which action best addresses this requirement?

  1. Choose an appropriate Log Analytics and Sentinel workspace topology with ingestion, access, retention and cost requirements documented.
  2. Use supported Microsoft Sentinel automation rules and Logic Apps playbooks for authorized notifications or containment actions with scoped identities.
  3. Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data.
  4. Enrich Sentinel investigations with trusted threat intelligence indicators and validate indicator relevance, expiry and confidence before defensive action.

Explanation

Correct Answer

C:

Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders. To verify, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Incorrect Answers

A:

This alternative focuses on “plan sentinel workspace and retention scope intentionally” instead of the required outcome. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

B:

That choice concerns “trigger approved sentinel playbooks through logic apps”, not the immediate requirement. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

D:

“use threat intelligence indicators with meaningful scope” is related to another task, not the failure shown here. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Question 732

A cloud security learner considers: A SOC wants an incident when a test account triggers repeated failed logins followed by an unusual successful access. Which underlying principle applies?

  1. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
  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. Incident correlation links account, host, IP and alert information, helping analysts distinguish one attack from unrelated background events.
  4. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Explanation

Correct Answer

D:

An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders. This supports the decision to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data.

Incorrect Answers

A:

“connect relevant Microsoft sentinel data sources” explains a different mechanism. Here, an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

B:

That statement concerns “use kql hunting queries over available sentinel logs” rather than the cause in this case. Here, an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

C:

The principle behind “investigate sentinel incidents using entity context” is not the one being tested. Here, an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Question 733

A SOC wants an incident when a test account triggers repeated failed logins followed by an unusual successful access. What should the team examine before accepting the result?

  1. Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.
  2. Verify synthetic events from required subscriptions appear in the intended workspace and that an unauthorized analyst cannot query sensitive log categories.
  3. Review a synthetic incident containing a user and IP entity, compare associated event times and document the evidence supporting disposition.
  4. Populate a test workbook from known sample incidents and compare its totals to the underlying query results and workspace timeframe.

Explanation

Correct Answer

A:

Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded. It is the relevant test because an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Incorrect Answers

B:

This evidence addresses “plan sentinel workspace and retention scope intentionally” instead of confirming the repair. To check this result, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

C:

“investigate sentinel incidents using entity context” would verify a different part of the system. To check this result, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

D:

That test concerns “use sentinel workbooks for investigation visibility”, not the requested outcome. To check this result, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Question 734

A SOC wants an incident when a test account triggers repeated failed logins followed by an unusual successful access. The proposed shortcut is: "Assume every ingested log row is automatically a high-confidence security incident without detection logic or suppression controls." 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. Threats may remain active despite centralized event storage when detection, triage and remediation are not connected.
  4. Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention.

Explanation

Correct Answer

B:

Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions. The shortcut is unsafe because an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Incorrect Answers

A:

The alternative risk relates to “Security investigations may be incomplete or too costly, and confidential event data may become accessible to…”, not the stated mistake. Here, analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

C:

That consequence concerns “Threats may remain active despite centralized event storage when detection, triage and remediation are not connected”, which is a different failure. Here, analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

D:

“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, analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

Question 735

For this case—A SOC wants an incident when a test account triggers repeated failed logins followed by an unusual successful access.—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: 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: 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.
  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

C:

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. The action and test belong together because an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Incorrect Answers

A:

The linked action and check for “plan sentinel workspace and retention scope intentionally” would not resolve this case. The appropriate action is to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. To confirm, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

B:

That action-and-evidence pair concerns “use sentinel workbooks for investigation visibility”, not this decision. The appropriate action is to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. To confirm, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

D:

“distinguish SIEM from soar responsibilities” evaluates a different intervention. The appropriate action is to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. To confirm, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Question 736

An operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. 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 a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions.
  3. Query collected security telemetry with appropriate Kusto Query Language filters and aggregations to investigate a defined suspicious behavior.
  4. Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data.

Explanation

Correct Answer

D:

The situation is that an operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. Configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders. To verify, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Incorrect Answers

A:

That choice concerns “plan sentinel workspace and retention scope intentionally”, not the immediate requirement. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

B:

The proposed action addresses “distinguish SIEM from soar responsibilities” rather than the problem described. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

C:

“use kql hunting queries over available sentinel logs” is related to another task, not the failure shown here. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Question 737

An operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. 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. KQL hunting finds patterns in ingested structured records and depends on correct tables, fields and time bounds rather than arbitrary natural-language guessing.
  3. A workbook visualizes available data and investigative trends but is not a substitute for the analytics rules and incident response process.
  4. Security information and event management supports detections and investigation, while orchestration and automation can execute governed response steps.

Explanation

Correct Answer

A:

The situation is that an operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. An analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders. This supports the decision to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data.

Incorrect Answers

B:

The principle behind “use kql hunting queries over available sentinel logs” is not the one being tested. Here, an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

C:

“use sentinel workbooks for investigation visibility” describes another technical distinction. Here, an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

D:

“distinguish SIEM from soar responsibilities” explains a different mechanism. Here, an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Question 738

For this situation—An operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern.—which check provides the strongest verification?

  1. Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
  2. Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.
  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. 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 an operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. Create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded. It is the relevant test because an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Incorrect Answers

A:

This evidence addresses “connect relevant Microsoft sentinel data sources” instead of confirming the repair. To check this result, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

C:

That test concerns “use kql hunting queries over available sentinel logs”, not the requested outcome. To check this result, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

D:

The proposed check is relevant to “plan sentinel workspace and retention scope intentionally”, but not sufficient here. To check this result, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

Question 739

An operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. If the team does the following—"Assume every ingested log row is automatically a high-confidence security incident without detection logic or suppression controls."—what could go wrong?

  1. Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
  2. Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention.
  3. Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.
  4. Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and tested.

Explanation

Correct Answer

C:

The situation is that an operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. Analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions. The shortcut is unsafe because an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Incorrect Answers

A:

“Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend…” can arise elsewhere, but it is not the most direct risk here. Here, analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

B:

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, analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

D:

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, analysts may miss real correlated threats or be overwhelmed with noise because events were never turned into useful incident definitions.

Question 740

An operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. Which action and validation evidence belong together?

  1. Action: Review Defender Vulnerability Management exposure findings and prioritize supported device software vulnerabilities by exploitability and business impact. Validation: Check a test endpoint's inventory for an intentionally outdated supported application and verify remediation updates the exposure assessment.
  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: 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: 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

D:

The situation is that an operator inspects thousands of Sentinel log rows manually each day without configuring a rule for its known attack pattern. 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. The action and test belong together because an analytics rule turns matched event patterns into alerts or incidents, whereas raw log storage alone does not notify responders.

Incorrect Answers

A:

That action-and-evidence pair concerns “use defender vulnerability management to prioritize remediation”, not this decision. The appropriate action is to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. To confirm, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

B:

The proposed pair focuses on “use kql hunting queries over available sentinel logs” instead. The appropriate action is to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. To confirm, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

C:

“trigger approved sentinel playbooks through logic apps” evaluates a different intervention. The appropriate action is to configure supported scheduled or near-real-time Microsoft Sentinel analytics rules with meaningful conditions and incident grouping for the available data. To confirm, create a harmless synthetic event pattern, execute a pilot analytics rule and confirm the expected incident grouping and severity are recorded.

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