Question 867 of 1,038
SC-200 Respond to security incidents Practice Question
Exhibit
Refer to the exhibit.
```json
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"workspaceName": {
"value": "sentinel-workspace"
},
"location": {
"value": "eastus"
},
"enableUEBA": {
"value": true
},
"dataConnectors": {
"value": [
"AzureIdentity",
"AzureActivity",
"MicrosoftThreatProtection"
]
}
}
}
```You are deploying Microsoft Sentinel using the above ARM template parameters. After deployment, you notice that Microsoft Defender for Cloud alerts are not being ingested. What is the MOST likely reason?
⚠ Common exam trap
Many exam-takers assume the 'MicrosoftThreatProtection' connector ingests all Microsoft security alerts, including Defender for Cloud, because of the broad 'Threat Protection' naming, but in reality it only covers Microsoft Defender XDR signals.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The 'MicrosoftThreatProtection' connector only ingests Microsoft Defender XDR signals, not Defender for Cloud alerts.
The 'MicrosoftThreatProtection' connector is specifically designed to ingest signals from Microsoft Defender XDR (formerly Microsoft 365 Defender), which includes Defender for Endpoint, Defender for Office 365, Defender for Identity, and Defender for Cloud Apps. It does not ingest Microsoft Defender for Cloud alerts. To ingest Defender for Cloud alerts, you must use the dedicated 'Defender for Cloud' data connector in Microsoft Sentinel. Therefore, deploying only the 'MicrosoftThreatProtection' connector will result in Defender for Cloud alerts not being ingested.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
UEBA is enabled, which conflicts with Defender for Cloud data ingestion.
Why it's wrong here
UEBA does not conflict with Defender for Cloud connectors.
- ✗
The workspace location (eastus) does not support Defender for Cloud connector.
Why it's wrong here
All regions support Defender for Cloud connector.
- ✓
The 'MicrosoftThreatProtection' connector only ingests Microsoft Defender XDR signals, not Defender for Cloud alerts.
Why this is correct
Defender for Cloud alerts require 'AzureSecurityCenter' connector.
- ✗
The workspace name 'sentinel-workspace' is reserved for internal use.
Why it's wrong here
Workspace name is arbitrary and not reserved.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jul 4, 2026
This SC-200 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SC-200 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.