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 76

Question 750

An engineer reviewing Blue Haven Media and its creative files and production workspaces services documents: Executives need a dashboard of detection trends but analysts export screenshots and manually recount incidents every week. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. Only a qualifying test incident launches the playbook and the activity record identifies its run.
  2. A qualifying test incident invokes the approved playbook and records its action outcome.
  3. A workbook refresh updates incident trend counts from current workspace data without manual re-entry.
  4. A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria.

Explanation

Correct Answer

C:

A workbook refresh updates incident trend counts from current workspace data without manual re-entry. This is the relevant proof because it tests whether the selected corrective action (Build suitable Microsoft Sentinel workbooks over authorized security data and relevant queries) addressed the initiating problem (Executives need a dashboard of detection trends but analysts export screenshots and manually recount incidents every week) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.

Incorrect Answers

A:

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 workbook refresh updates incident trend counts from current workspace data without manual re-entry.

B:

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 Blue Haven Media, it does not establish the required outcome: A workbook refresh updates incident trend counts from current workspace data without manual re-entry.

D:

A reproducible hunting query identifies the suspicious test event and the resulting detection has recorded acceptance criteria. This is useful evidence for a different situation (A cloud SOC sees broad authentication anomalies but does not explore related signals to formulate a new detection hypothesis) and action (Use Microsoft Sentinel hunting queries to investigate patterns and promote validated findings to detection content). For the reported issue at Blue Haven Media, it does not establish the required outcome: A workbook refresh updates incident trend counts from current workspace data without manual re-entry.

Question 751

An engineer reviewing Oceanview Payments and its regulated card workflows and employee access services documents: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. 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. Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule.
  3. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.
  4. Configure the intended automation rule trigger, conditions and playbook permissions explicitly.

Explanation

Correct Answer

D:

Configure the intended automation rule trigger, conditions and playbook permissions explicitly. This directly addresses the observed weakness: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. For Oceanview Payments and its regulated card workflows and employee access, a meaningful acceptance check would be: Only a qualifying test incident launches the playbook and the activity record identifies its run.

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

B:

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

C:

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 Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Question 752

An engineer reviewing Oceanview Payments and its regulated card workflows and employee access services documents: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. Only a qualifying test incident launches the playbook and the activity record identifies its run.
  2. A qualifying test incident invokes the approved playbook and records its action outcome.
  3. A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
  4. A recent sample identity event is searchable with the expected schema in the connected data source.

Explanation

Correct Answer

A:

Only a qualifying test incident launches the playbook and the activity record identifies its run. This is the relevant proof because it tests whether the selected corrective action (Configure the intended automation rule trigger, conditions and playbook permissions explicitly) addressed the initiating problem (A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration) in Oceanview Payments's regulated card workflows and employee access environment, not merely whether a task was marked complete.

Incorrect Answers

B:

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 Oceanview Payments, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

C:

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 Oceanview Payments, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

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 Oceanview Payments, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Question 753

Orion Network Services operates subscriber applications and remote operations with a limited maintenance window. Its review records the following concern: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. 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. Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule.
  3. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.
  4. Configure the intended automation rule trigger, conditions and playbook permissions explicitly.

Explanation

Correct Answer

D:

Configure the intended automation rule trigger, conditions and playbook permissions explicitly. This directly addresses the observed weakness: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. For Orion Network Services and its subscriber applications and remote operations, a meaningful acceptance check would be: Only a qualifying test incident launches the playbook and the activity record identifies its run.

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: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

B:

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

C:

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 Orion Network Services and its subscriber applications and remote operations, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Question 754

Orion Network Services operates subscriber applications and remote operations with a limited maintenance window. Its review records the following concern: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A recent sample identity event is searchable with the expected schema in the connected data source.
  2. Only a qualifying test incident launches the playbook and the activity record identifies its run.
  3. A qualifying test incident invokes the approved playbook and records its action outcome.
  4. A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.

Explanation

Correct Answer

B:

Only a qualifying test incident launches the playbook and the activity record identifies its run. This is the relevant proof because it tests whether the selected corrective action (Configure the intended automation rule trigger, conditions and playbook permissions explicitly) addressed the initiating problem (A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration) in Orion Network Services's subscriber applications and remote operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

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 Orion Network Services, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

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: Only a qualifying test incident launches the playbook and the activity record identifies its run.

D:

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 Orion Network Services, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Question 755

For Aspen Digital, the security review of client advisory systems and shared files highlights this gap: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. Which action BEST addresses the described security, identity, or compliance gap?

  1. Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule.
  2. Use supported Sentinel automation rules and playbooks for security orchestration and automated response.
  3. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.
  4. Configure the intended automation rule trigger, conditions and playbook permissions explicitly.

Explanation

Correct Answer

D:

Configure the intended automation rule trigger, conditions and playbook permissions explicitly. This directly addresses the observed weakness: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. For Aspen Digital and its client advisory systems and shared files, a meaningful acceptance check would be: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Incorrect Answers

A:

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 Aspen Digital and its client advisory systems and shared files, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

B:

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: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

C:

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 Aspen Digital and its client advisory systems and shared files, the issue is instead: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. This alternative alone would not demonstrate the needed result: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Question 756

For Aspen Digital, the security review of client advisory systems and shared files highlights this gap: A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. Only a qualifying test incident launches the playbook and the activity record identifies its run.
  2. A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not.
  3. A qualifying test incident invokes the approved playbook and records its action outcome.
  4. A recent sample identity event is searchable with the expected schema in the connected data source.

Explanation

Correct Answer

A:

Only a qualifying test incident launches the playbook and the activity record identifies its run. This is the relevant proof because it tests whether the selected corrective action (Configure the intended automation rule trigger, conditions and playbook permissions explicitly) addressed the initiating problem (A security workflow assumes a Microsoft Sentinel playbook runs automatically on every alert regardless of its trigger or automation configuration) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.

Incorrect Answers

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 Aspen Digital, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

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 Aspen Digital, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

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 Aspen Digital, it does not establish the required outcome: Only a qualifying test incident launches the playbook and the activity record identifies its run.

Question 757

For Silver Cove Payments, the security review of transaction data and fraud monitoring highlights this gap: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. 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. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.
  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

D:

Use Sentinel incident triage, entity investigation, comments and ownership fields to track response. This directly addresses the observed weakness: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. For Silver Cove Payments and its transaction data and fraud monitoring, a meaningful acceptance check would be: A test incident has an accountable assignee, classification and evidence of the final disposition.

Incorrect Answers

A:

Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts. This addresses a different security or governance gap: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. For Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. This alternative alone would not demonstrate the needed result: A test incident has an accountable assignee, classification and evidence of the final disposition.

B:

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 Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. This alternative alone would not demonstrate the needed result: A test incident has an accountable assignee, classification and evidence of the final disposition.

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 Silver Cove Payments and its transaction data and fraud monitoring, the issue is instead: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. This alternative alone would not demonstrate the needed result: A test incident has an accountable assignee, classification and evidence of the final disposition.

Question 758

For Silver Cove Payments, the security review of transaction data and fraud monitoring highlights this gap: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A recent sample identity event is searchable with the expected schema in the connected data source.
  2. A qualifying test incident invokes the approved playbook and records its action outcome.
  3. A test incident has an accountable assignee, classification and evidence of the final disposition.
  4. Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.

Explanation

Correct Answer

C:

A test incident has an accountable assignee, classification and evidence of the final disposition. This is the relevant proof because it tests whether the selected corrective action (Use Sentinel incident triage, entity investigation, comments and ownership fields to track response) addressed the initiating problem (A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes) in Silver Cove Payments's transaction data and fraud monitoring environment, not merely whether a task was marked complete.

Incorrect Answers

A:

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 Silver Cove Payments, it does not establish the required outcome: A test incident has an accountable assignee, classification and evidence of the final disposition.

B:

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 Silver Cove Payments, it does not establish the required outcome: A test incident has an accountable assignee, classification and evidence of the final disposition.

D:

Multiple test alerts belonging to one scenario are represented in an attributable incident grouping. This is useful evidence for a different situation (Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping) and action (Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts). For the reported issue at Silver Cove Payments, it does not establish the required outcome: A test incident has an accountable assignee, classification and evidence of the final disposition.

Question 759

An engineer reviewing Horizon Energy Services and its remote field-worker sign-ins and operations services documents: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. 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 Sentinel incident triage, entity investigation, comments and ownership fields to track response.
  4. Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace.

Explanation

Correct Answer

C:

Use Sentinel incident triage, entity investigation, comments and ownership fields to track response. This directly addresses the observed weakness: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. For Horizon Energy Services and its remote field-worker sign-ins and operations, a meaningful acceptance check would be: A test incident has an accountable assignee, classification and evidence of the final disposition.

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 Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. This alternative alone would not demonstrate the needed result: A test incident has an accountable assignee, classification and evidence of the final disposition.

B:

Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts. This addresses a different security or governance gap: Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping. For Horizon Energy Services and its remote field-worker sign-ins and operations, the issue is instead: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. This alternative alone would not demonstrate the needed result: A test incident has an accountable assignee, classification and evidence of the final disposition.

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 suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. This alternative alone would not demonstrate the needed result: A test incident has an accountable assignee, classification and evidence of the final disposition.

Question 760

An engineer reviewing Horizon Energy Services and its remote field-worker sign-ins and operations services documents: A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A qualifying test incident invokes the approved playbook and records its action outcome.
  2. Multiple test alerts belonging to one scenario are represented in an attributable incident grouping.
  3. A recent sample identity event is searchable with the expected schema in the connected data source.
  4. A test incident has an accountable assignee, classification and evidence of the final disposition.

Explanation

Correct Answer

D:

A test incident has an accountable assignee, classification and evidence of the final disposition. This is the relevant proof because it tests whether the selected corrective action (Use Sentinel incident triage, entity investigation, comments and ownership fields to track response) addressed the initiating problem (A suspicious event is detected but the SOC closes it before assigning an owner or preserving investigation notes) 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 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 Horizon Energy Services, it does not establish the required outcome: A test incident has an accountable assignee, classification and evidence of the final disposition.

B:

Multiple test alerts belonging to one scenario are represented in an attributable incident grouping. This is useful evidence for a different situation (Many alerts from the same affected entity appear as unrelated tickets because the team never configures or reviews incident grouping) and action (Use supported Sentinel incident creation and grouping settings where appropriate for correlated alerts). For the reported issue at Horizon Energy Services, it does not establish the required outcome: A test incident has an accountable assignee, classification and evidence of the final disposition.

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 Horizon Energy Services, it does not establish the required outcome: A test incident has an accountable assignee, classification and evidence of the final disposition.