McAfee-Secured Website

Exam Bundle

Exam Code: SC-900

Exam Name Microsoft Security, Compliance, and Identity Fundamentals

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Security, Compliance, and Identity Fundamentals

Microsoft SC-900 Bundle $44.99

100% Microsoft SC-900 Guaranteed Success With Testking Training Materials

Get Real SC-900 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    SC-900 Questions & Answers

    259 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual SC-900 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • SC-900 Video Course

    SC-900 Video Course

    147 Video Lectures

    SC-900 Video Course is developed by Microsoft Professionals to help you pass the SC-900 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Security, Compliance, and Identity Fundamentals exam.
  • Study Guide

    SC-900 Study Guide

    413 PDF Pages

    Developed by industry experts, this 413-page guide spells out in painstaking detail all of the information you need to ace SC-900 exam.

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

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    259 Questions

    $124.99
  • SC-900 Video Course

    Video Course

    147 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    413 PDF Pages

    $29.99

Microsoft SC-900 Practice Test 74

Question 730

For Blue Haven Media, the security review of creative files and production workspaces highlights this gap: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
  2. A recent sample identity event is searchable with the expected schema in the connected data source.
  3. An incident query joins an identity event and a network event by matching time and entity attributes.
  4. Only a qualifying test incident launches the playbook and the activity record identifies its run.

Explanation

Correct Answer

A:

A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not. This is the relevant proof because it tests whether the selected corrective action (Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule) addressed the initiating problem (A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A recent sample identity event is searchable with the expected schema in the connected data source. This is useful evidence for a different situation (A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events) and action (Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace). For the reported issue at Blue Haven Media, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

C:

An incident query joins an identity event and a network event by matching time and entity attributes. This is useful evidence for a different situation (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) and action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations). For the reported issue at Blue Haven Media, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

D:

Only a qualifying test incident launches the playbook and the activity record identifies its run. This is useful evidence for a different situation (A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration) and action (Configure the intended automation rule trigger, conditions and playbook permissions explicitly). For the reported issue at Blue Haven Media, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

Question 731

An engineer reviewing Cobalt Aerospace and its engineering programs and secure collaboration services documents: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. Which action BEST addresses the described security, identity, or compliance gap?

  1. Configure the intended automation rule trigger, conditions and playbook permissions explicitly.
  2. Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations.
  3. Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule.
  4. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.

Explanation

Correct Answer

C:

Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule. This directly addresses the observed weakness: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. For Cobalt Aerospace and its engineering programs and secure collaboration, a meaningful acceptance check would be: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

Incorrect Answers

A:

Configure the intended automation rule trigger, conditions and playbook permissions explicitly. This addresses a different security or governance gap: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. For Cobalt Aerospace and its engineering programs and secure collaboration, the issue is instead: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. This alternative alone would not demonstrate the needed result: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

B:

Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations. This addresses a different security or governance gap: A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems. For Cobalt Aerospace and its engineering programs and secure collaboration, the issue is instead: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. This alternative alone would not demonstrate the needed result: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

D:

Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace. This addresses a different security or governance gap: A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events. For Cobalt Aerospace and its engineering programs and secure collaboration, the issue is instead: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. This alternative alone would not demonstrate the needed result: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

Question 732

An engineer reviewing Cobalt Aerospace and its engineering programs and secure collaboration services documents: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An incident query joins an identity event and a network event by matching time and entity attributes.
  2. A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
  3. A recent sample identity event is searchable with the expected schema in the connected data source.
  4. Only a qualifying test incident launches the playbook and the activity record identifies its run.

Explanation

Correct Answer

B:

A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not. This is the relevant proof because it tests whether the selected corrective action (Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule) addressed the initiating problem (A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule) in Cobalt Aerospace's engineering programs and secure collaboration environment, not merely whether a task was marked complete.

Incorrect Answers

A:

An incident query joins an identity event and a network event by matching time and entity attributes. This is useful evidence for a different situation (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) and action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations). For the reported issue at Cobalt Aerospace, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

C:

A recent sample identity event is searchable with the expected schema in the connected data source. This is useful evidence for a different situation (A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events) and action (Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace). For the reported issue at Cobalt Aerospace, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

D:

Only a qualifying test incident launches the playbook and the activity record identifies its run. This is useful evidence for a different situation (A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration) and action (Configure the intended automation rule trigger, conditions and playbook permissions explicitly). For the reported issue at Cobalt Aerospace, it does not establish the required outcome: A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

Question 733

An engineer reviewing Orion Network Services and its subscriber applications and remote operations services documents: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use supported Sentinel automation rules and playbooks for security orchestration and automated response.
  2. Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations.
  3. Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts.
  4. Use Sentinel incident triage, entity investigation, comments and ownership fields to track response.

Explanation

Correct Answer

C:

Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts. This directly addresses the observed weakness: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. For Orion Network Services and its subscriber applications and remote operations, a meaningful acceptance check would be: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Incorrect Answers

A:

Use supported Sentinel automation rules and playbooks for security orchestration and automated response. This addresses a different security or governance gap: Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

B:

Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations. This addresses a different security or governance gap: A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

D:

Use Sentinel incident triage, entity investigation, comments and ownership fields to track response. This addresses a different security or governance gap: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. For Orion Network Services and its subscriber applications and remote operations, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Question 734

An engineer reviewing Orion Network Services and its subscriber applications and remote operations services documents: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A test incident has an accountable assignee, classification and evidence of the final disposition.
  2. Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.
  3. A qualifying test incident invokes the approved playbook and records its action outcome.
  4. An incident query joins an identity event and a network event by matching time and entity attributes.

Explanation

Correct Answer

B:

Multiple test alerts belonging to one scenario are represented in an attributable incident grouping. This is the relevant proof because it tests whether the selected corrective action (Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts) addressed the initiating problem (Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping) in Orion Network Services's subscriber applications and remote operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A test incident has an accountable assignee, classification and evidence of the final disposition. This is useful evidence for a different situation (A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes) and action (Use Sentinel incident triage, entity investigation, comments and ownership fields to track response). For the reported issue at Orion Network Services, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

C:

A qualifying test incident invokes the approved playbook and records its action outcome. This is useful evidence for a different situation (Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path) and action (Use supported Sentinel automation rules and playbooks for security orchestration and automated response). For the reported issue at Orion Network Services, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

D:

An incident query joins an identity event and a network event by matching time and entity attributes. This is useful evidence for a different situation (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) and action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations). For the reported issue at Orion Network Services, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Question 735

Aspen Digital operates client advisory systems and shared files under a least-privilege requirement. Its review records the following concern: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use supported Sentinel automation rules and playbooks for security orchestration and automated response.
  2. Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts.
  3. Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations.
  4. Use Sentinel incident triage, entity investigation, comments and ownership fields to track response.

Explanation

Correct Answer

B:

Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts. This directly addresses the observed weakness: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. For Aspen Digital and its client advisory systems and shared files, a meaningful acceptance check would be: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Incorrect Answers

A:

Use supported Sentinel automation rules and playbooks for security orchestration and automated response. This addresses a different security or governance gap: Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path. For Aspen Digital and its client advisory systems and shared files, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

C:

Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations. This addresses a different security or governance gap: A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems. For Aspen Digital and its client advisory systems and shared files, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

D:

Use Sentinel incident triage, entity investigation, comments and ownership fields to track response. This addresses a different security or governance gap: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. For Aspen Digital and its client advisory systems and shared files, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Question 736

Aspen Digital operates client advisory systems and shared files under a least-privilege requirement. Its review records the following concern: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A test incident has an accountable assignee, classification and evidence of the final disposition.
  2. An incident query joins an identity event and a network event by matching time and entity attributes.
  3. Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.
  4. A qualifying test incident invokes the approved playbook and records its action outcome.

Explanation

Correct Answer

C:

Multiple test alerts belonging to one scenario are represented in an attributable incident grouping. This is the relevant proof because it tests whether the selected corrective action (Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts) addressed the initiating problem (Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A test incident has an accountable assignee, classification and evidence of the final disposition. This is useful evidence for a different situation (A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes) and action (Use Sentinel incident triage, entity investigation, comments and ownership fields to track response). For the reported issue at Aspen Digital, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

B:

An incident query joins an identity event and a network event by matching time and entity attributes. This is useful evidence for a different situation (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) and action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations). For the reported issue at Aspen Digital, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

D:

A qualifying test incident invokes the approved playbook and records its action outcome. This is useful evidence for a different situation (Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path) and action (Use supported Sentinel automation rules and playbooks for security orchestration and automated response). For the reported issue at Aspen Digital, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Question 737

For Stonehaven Logistics, the security review of warehouse scheduling and shipping records highlights this gap: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts.
  2. Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations.
  3. Use supported Sentinel automation rules and playbooks for security orchestration and automated response.
  4. Use Sentinel incident triage, entity investigation, comments and ownership fields to track response.

Explanation

Correct Answer

A:

Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts. This directly addresses the observed weakness: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. For Stonehaven Logistics and its warehouse scheduling and shipping records, a meaningful acceptance check would be: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Incorrect Answers

B:

Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations. This addresses a different security or governance gap: A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems. For Stonehaven Logistics and its warehouse scheduling and shipping records, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

C:

Use supported Sentinel automation rules and playbooks for security orchestration and automated response. This addresses a different security or governance gap: Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path. For Stonehaven Logistics and its warehouse scheduling and shipping records, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

D:

Use Sentinel incident triage, entity investigation, comments and ownership fields to track response. This addresses a different security or governance gap: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. For Stonehaven Logistics and its warehouse scheduling and shipping records, the issue is instead: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. This alternative alone would not demonstrate the needed result: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Question 738

For Stonehaven Logistics, the security review of warehouse scheduling and shipping records highlights this gap: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An incident query joins an identity event and a network event by matching time and entity attributes.
  2. Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.
  3. A qualifying test incident invokes the approved playbook and records its action outcome.
  4. A test incident has an accountable assignee, classification and evidence of the final disposition.

Explanation

Correct Answer

B:

Multiple test alerts belonging to one scenario are represented in an attributable incident grouping. This is the relevant proof because it tests whether the selected corrective action (Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts) addressed the initiating problem (Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping) in Stonehaven Logistics's warehouse scheduling and shipping records environment, not merely whether a task was marked complete.

Incorrect Answers

A:

An incident query joins an identity event and a network event by matching time and entity attributes. This is useful evidence for a different situation (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) and action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations). For the reported issue at Stonehaven Logistics, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

C:

A qualifying test incident invokes the approved playbook and records its action outcome. This is useful evidence for a different situation (Analysts manually create the same response ticket for every confirmed alert although they want a consistent approved automation path) and action (Use supported Sentinel automation rules and playbooks for security orchestration and automated response). For the reported issue at Stonehaven Logistics, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

D:

A test incident has an accountable assignee, classification and evidence of the final disposition. This is useful evidence for a different situation (A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes) and action (Use Sentinel incident triage, entity investigation, comments and ownership fields to track response). For the reported issue at Stonehaven Logistics, it does not establish the required outcome: Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Question 739

For Horizon Energy Services, the security review of remote field-worker sign-ins and operations highlights this gap: A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use Microsoft Sentinel hunting queries to investigate patterns and promote validated findings to detection content.
  2. Build suitable Microsoft Sentinel workbooks over authorized security data and relevant queries.
  3. Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule.
  4. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.

Explanation

Correct Answer

A:

Use Microsoft Sentinel hunting queries to investigate patterns and promote validated findings to detection content. This directly addresses the observed weakness: A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis. For Horizon Energy Services and its remote field-worker sign-ins and operations, a meaningful acceptance check would be: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

Incorrect Answers

B:

Build suitable Microsoft Sentinel workbooks over authorized security data and relevant queries. This addresses a different security or governance gap: Executives need a dashboard of detection trends but analysts export screenshots and manually recount incidents every week. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis. This alternative alone would not demonstrate the needed result: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

C:

Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule. This addresses a different security or governance gap: A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis. This alternative alone would not demonstrate the needed result: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

D:

Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace. This addresses a different security or governance gap: A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis. This alternative alone would not demonstrate the needed result: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

Question 740

For Horizon Energy Services, the security review of remote field-worker sign-ins and operations highlights this gap: A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A workbook refresh updates incident trend counts from current workspace data without manual re-entry.
  2. A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
  3. A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.
  4. A recent sample identity event is searchable with the expected schema in the connected data source.

Explanation

Correct Answer

C:

A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria. This is the relevant proof because it tests whether the selected corrective action (Use Microsoft Sentinel hunting queries to investigate patterns and promote validated findings to detection content) addressed the initiating problem (A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis) in Horizon Energy Services's remote field-worker sign-ins and operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A workbook refresh updates incident trend counts from current workspace data without manual re-entry. This is useful evidence for a different situation (Executives need a dashboard of detection trends but analysts export screenshots and manually recount incidents every week) and action (Build suitable Microsoft Sentinel workbooks over authorized security data and relevant queries). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

B:

A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not. This is useful evidence for a different situation (A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule) and action (Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

D:

A recent sample identity event is searchable with the expected schema in the connected data source. This is useful evidence for a different situation (A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events) and action (Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.