Microsoft SC-900 Dumps
Microsoft SC-900 Practice Test 73
Question 720
For this case—A SOC architect describes a SIEM dashboard as a complete automated response system despite no defined incident workflow or approvals.—which implementation and acceptance check are correctly paired?
Explanation
Correct Answer
The situation is that a SOC architect describes a SIEM dashboard as a complete automated response system despite no defined incident workflow or approvals. Use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. Validation: Feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs. The action and test belong together because security information and event management supports detections and investigation, while orchestration and automation can execute governed response steps.
Incorrect Answers
That action-and-evidence pair concerns “use sentinel analytics rules to create actionable incidents”, not this decision. The appropriate action is to use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. To confirm, feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
The proposed pair focuses on “use sentinel workbooks for investigation visibility” instead. The appropriate action is to use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. To confirm, feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
“use kql hunting queries over available sentinel logs” evaluates a different intervention. The appropriate action is to use a SIEM to collect, correlate and investigate security events and SOAR workflows to coordinate approved response actions. To confirm, feed synthetic alerts to a test incident and verify analyst triage before a separately authorized automated ticket or notification occurs.
Question 721
An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. Which implementation or design choice most directly mitigates the stated issue?
Explanation
Correct Answer
Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. To verify, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
Incorrect Answers
“investigate sentinel incidents using entity context” is related to another task, not the failure shown here. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
This alternative focuses on “distinguish SIEM from soar responsibilities” instead of the required outcome. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
That choice concerns “trigger approved sentinel playbooks through logic apps”, not the immediate requirement. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Question 722
An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. Which technical explanation most directly supports the right approach?
Explanation
Correct Answer
Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. This supports the decision to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.
Incorrect Answers
The principle behind “use sentinel analytics rules to create actionable incidents” is not the one being tested. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
“trigger approved sentinel playbooks through logic apps” explains a different mechanism. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
That statement concerns “use threat intelligence indicators with meaningful scope” rather than the cause in this case. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Question 723
For this situation—An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments.—which check provides the strongest verification?
Explanation
Correct Answer
Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields. It is the relevant test because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Incorrect Answers
“use threat intelligence indicators with meaningful scope” would verify a different part of the system. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
That test concerns “use kql hunting queries over available sentinel logs”, not the requested outcome. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
This evidence addresses “use sentinel analytics rules to create actionable incidents” instead of confirming the repair. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
Question 724
An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. If the team does the following—"Create Sentinel analytics rules for a data source that was never connected and assume the rules can search events stored elsewhere."—what could go wrong?
Explanation
Correct Answer
Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on. The shortcut is unsafe because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Incorrect Answers
That consequence concerns “Security events may remain untriaged while leaders mistake dashboards for active detections and operational controls”, which is a different failure. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
“Legitimate business connectivity may be disrupted while low-confidence indicators obscure current threats and consume analyst attention” does not describe the result of this shortcut. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
The alternative risk relates to “Automation can amplify false-positive damage or expand privilege exposure if response actions are not constrained and…”, not the stated mistake. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
Question 725
An enterprise wants to correlate Entra sign-in activity with Azure Firewall logs using Microsoft Sentinel across approved environments. Which action and validation evidence belong together?
Explanation
Correct Answer
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
“use kql hunting queries over available sentinel logs” evaluates a different intervention. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
The linked action and check for “plan sentinel workspace and retention scope intentionally” would not resolve this case. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
That action-and-evidence pair concerns “use sentinel workbooks for investigation visibility”, not this decision. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
Question 726
An SC-900 learner considers: A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. What is the most appropriate next decision?
Explanation
Correct Answer
The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. To verify, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
Incorrect Answers
“use kql hunting queries over available sentinel logs” is related to another task, not the failure shown here. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
That choice concerns “use threat intelligence indicators with meaningful scope”, not the immediate requirement. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
The proposed action addresses “investigate sentinel incidents using entity context” rather than the problem described. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Question 727
A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Why does the recommended approach address this particular concern?
Explanation
Correct Answer
The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation. This supports the decision to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope.
Incorrect Answers
“distinguish SIEM from soar responsibilities” describes another technical distinction. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
“use sentinel workbooks for investigation visibility” explains a different mechanism. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
The principle behind “use kql hunting queries over available sentinel logs” is not the one being tested. Here, detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Question 728
A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Which evidence best validates the proposed outcome?
Explanation
Correct Answer
The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields. It is the relevant test because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Incorrect Answers
That test concerns “trigger approved sentinel playbooks through logic apps”, not the requested outcome. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
The proposed check is relevant to “distinguish SIEM from soar responsibilities”, but not sufficient here. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
This evidence addresses “use kql hunting queries over available sentinel logs” instead of confirming the repair. To check this result, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
Question 729
Consider this situation: A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. A team member suggests: "Create Sentinel analytics rules for a data source that was never connected and assume the rules can search events stored elsewhere." What is the main risk?
Explanation
Correct Answer
The situation is that a security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on. The shortcut is unsafe because detections can only analyze available and correctly parsed telemetry, so missing connectors or ingestion gaps weaken incident investigation.
Incorrect Answers
The alternative risk relates to “Legitimate users may be disrupted and the actual compromised identity may remain active if entity evidence…”, not the stated mistake. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
“Security investigations may be incomplete or too costly, and confidential event data may become accessible to…” can arise elsewhere, but it is not the most direct risk here. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
That consequence concerns “An investigation may incorrectly report no threats because the query targeted the wrong data source or…”, which is a different failure. Here, suspicious events may go undetected because the SIEM never ingests the activity its correlation rules depend on.
Question 730
A security and compliance reviewer considers: A security team publishes an identity threat rule but discovers its Sentinel workspace has no identity log connector configured. Which response and evidence should be linked?
Explanation
Correct Answer
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
“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.
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.
The proposed pair focuses on “plan sentinel workspace and retention scope intentionally” instead. The appropriate action is to use supported Microsoft Sentinel data connectors to ingest required cloud, identity and network security logs with correct permissions and workspace scope. To confirm, generate a harmless test sign-in and firewall event and verify both reach the intended Sentinel workspace with expected timestamps and fields.
Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests
- Microsoft SC-900 Practice Test 71 - 10 Questions (Last Reviewed 07-Nov-2026)
- Microsoft SC-900 Practice Test 72 - 10 Questions (Last Reviewed 06-Nov-2026)
- Microsoft SC-900 Practice Test 73 - 10 Questions (Last Reviewed 05-Nov-2026)
- Microsoft SC-900 Practice Test 74 - 10 Questions (Last Reviewed 04-Nov-2026)
- Microsoft SC-900 Practice Test 75 - 10 Questions (Last Reviewed 03-Nov-2026)