SC-200 Perform threat hunting Practice Question
During a threat hunt, you discover a previously unknown malware variant that communicates over HTTPS to a command-and-control (C2) server. You want to create a custom detection in Microsoft Sentinel that triggers when any device in the organization resolves the C2 domain via DNS. Which data connector should you ensure is enabled?
⚠ Common exam trap
SC-200 often tests whether candidates confuse endpoint security event telemetry with network-layer telemetry — the trap is picking 'Windows Security Events via AMA' because it sounds like it captures everything on the device, when in fact DNS query logs require the dedicated DNS connector.
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
✓
DNS (Preview) via AMA
The DNS (Preview) via AMA connector ingests DNS query logs from onboarded devices into Microsoft Sentinel, which is exactly the telemetry needed to detect when any device resolves the malicious C2 domain. Since the detection requirement is specifically about DNS resolution of the C2 domain, this connector provides the authoritative query events (including queried domain names and client IPs) that a custom analytics rule can match against. Without DNS logs flowing into the workspace, no KQL rule can trigger on domain resolution regardless of how well it is written.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
DNS (Preview) via AMA
Why this is correct
The DNS (Preview) via AMA connector ingests DNS query events from devices, which is the only telemetry that records domain resolution. Enabling it satisfies the requirement to trigger when any device resolves the C2 domain, since network connectors alone would not capture resolution.
- ✗
Azure Activity
Why it's wrong here
Azure Activity records control-plane operations on Azure resources, such as role assignments and resource deployments; it contains no DNS query telemetry, so C2 domain resolutions never appear. It is tempting because it does surface suspicious activity, but it would be the right connector for detecting Azure subscription changes, not endpoint DNS lookups.
- ✗
Office 365 (Preview)
Why it's wrong here
The Office 365 connector ingests Exchange, SharePoint and Teams audit events, which contain no endpoint DNS resolution records, so the detection would never fire. It is tempting because it is the standard connector for hunting email-borne threats and anomalous Microsoft 365 user activity.
- ✗
Windows Security Events via AMA
Why it's wrong here
Windows Security Events via AMA collects event log data such as process creation and logons; DNS client queries are not written to those channels, so domain resolution would go unseen. It is tempting because it is the default connector for endpoint-level hunting across Windows devices.
Visual reference
Go deeper
Related to this question
About these practice questions
This SC-200 question is part of Courseiva's 1,303-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.