- A
Use a self-join: query DeviceProcessEvents for mstsc.exe, extract the target device (e.g., from command line), and then join with another query on DeviceProcessEvents for PowerShell on the target device where the time difference between the events is less than 10 minutes.
This pattern correctly joins the two event sequences: the RDP client process on the source device and the subsequent script execution on the target device, with a time constraint to correlate them.
- B
Query DeviceNetworkEvents for RDP connections (port 3389) and then join with DeviceProcessEvents for PowerShell on the same device.
Why wrong: Network events show connections but do not easily reveal the process that initiated them. This approach is less direct and may miss the context of the RDP client process (mstsc.exe).
- C
Use the 'union' operator to combine all mstsc.exe and PowerShell events, then summarize by device and time.
Why wrong: Union merely combines tables; it does not correlate events across devices. You need a join with a time window to link the two related events.
- D
Query DeviceLogonEvents for RDP logon type and then join with DeviceProcessEvents for PowerShell on the same device.
Why wrong: DeviceLogonEvents show successful logons, but the scenario focuses on the RDP client process (mstsc.exe) which may not always be logged as a logon event. This would miss the source device process.
SC-200 Mitigate threats using Microsoft Defender XDR Practice Question
This SC-200 practice question tests your understanding of mitigate threats using microsoft defender xdr. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: kQL's `DeviceProcessEvents` table tracks process creation and termination.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security analyst is investigating an advanced persistent threat campaign that involves lateral movement using RDP. The analyst suspects that an attacker uses RDP from DeviceA to DeviceB, and then within a few minutes executes a malicious PowerShell script on DeviceB. The analyst wants to create a custom detection rule in Microsoft 365 Defender that triggers when this pattern occurs. Which KQL query pattern should be used to correlate these events across devices?
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
Use a self-join: query DeviceProcessEvents for mstsc.exe, extract the target device (e.g., from command line), and then join with another query on DeviceProcessEvents for PowerShell on the target device where the time difference between the events is less than 10 minutes.
Option A is correct because it uses a self-join on DeviceProcessEvents to first detect the mstsc.exe process (RDP client) on DeviceA, extract the target device name from the command line, and then join with a second query on DeviceProcessEvents for PowerShell on DeviceB. The join condition includes a time difference of less than 10 minutes, which directly correlates the lateral movement (RDP) with the subsequent malicious script execution across devices, matching the described attack pattern.
Key principle: KQL's `DeviceProcessEvents` table tracks process creation and termination.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use a self-join: query DeviceProcessEvents for mstsc.exe, extract the target device (e.g., from command line), and then join with another query on DeviceProcessEvents for PowerShell on the target device where the time difference between the events is less than 10 minutes.
Why this is correct
This pattern correctly joins the two event sequences: the RDP client process on the source device and the subsequent script execution on the target device, with a time constraint to correlate them.
Related concept
KQL's `DeviceProcessEvents` table tracks process creation and termination.
- ✗
Query DeviceNetworkEvents for RDP connections (port 3389) and then join with DeviceProcessEvents for PowerShell on the same device.
Why it's wrong here
Network events show connections but do not easily reveal the process that initiated them. This approach is less direct and may miss the context of the RDP client process (mstsc.exe).
- ✗
Use the 'union' operator to combine all mstsc.exe and PowerShell events, then summarize by device and time.
Why it's wrong here
Union merely combines tables; it does not correlate events across devices. You need a join with a time window to link the two related events.
- ✗
Query DeviceLogonEvents for RDP logon type and then join with DeviceProcessEvents for PowerShell on the same device.
Why it's wrong here
DeviceLogonEvents show successful logons, but the scenario focuses on the RDP client process (mstsc.exe) which may not always be logged as a logon event. This would miss the source device process.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose options that only correlate events on a single device (like B or D) or use aggregation operators like 'union' (C) that lose the cross-device temporal sequence, failing to recognize that the self-join pattern is required to correlate events across different devices in a lateral movement scenario.
Trap categories for this question
Command / output trap
Network events show connections but do not easily reveal the process that initiated them. This approach is less direct and may miss the context of the RDP client process (mstsc.exe).
Scenario analysis trap
DeviceLogonEvents show successful logons, but the scenario focuses on the RDP client process (mstsc.exe) which may not always be logged as a logon event. This would miss the source device process.
Detailed technical explanation
How to think about this question
In Microsoft 365 Defender, DeviceProcessEvents captures process creation events including command-line arguments, which for mstsc.exe often contain the target device name (e.g., 'mstsc.exe /v:DeviceB'). The self-join pattern leverages this by extracting the target device from the command line using parse or extract functions, then joining with a second DeviceProcessEvents query filtered for PowerShell (powershell.exe or pwsh.exe) on that target device. The time difference condition (e.g., 'where TimeGenerated between (TimeGenerated1 .. TimeGenerated1 + 10m)') ensures the events are temporally correlated, which is critical for detecting automated or scripted lateral movement where the attacker quickly executes malicious code after establishing the RDP session.
KKey Concepts to Remember
- KQL's `DeviceProcessEvents` table tracks process creation and termination.
- Self-joins in KQL correlate events from the same table based on derived relationships.
- Time-based correlation (`between` operator) is vital for sequencing events in KQL.
- Extracting data from fields like `CommandLine` is crucial for cross-event linking.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
KQL's `DeviceProcessEvents` table tracks process creation and termination.
Real-world example
How this comes up in practice
A healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
What to study next
Got this wrong? Here's your next step.
Review kQL's `DeviceProcessEvents` table tracks process creation and termination., then practise related SC-200 questions on the same topic to reinforce the concept.
- →
Mitigate threats using Microsoft Defender XDR — study guide chapter
Learn the concepts, then practise the questions
- →
Mitigate threats using Microsoft Defender XDR practice questions
Targeted practice on this topic area only
- →
All SC-200 questions
1,639 questions across all exam domains
- →
Microsoft Security Operations Analyst SC-200 study guide
Full concept coverage aligned to exam objectives
- →
SC-200 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SC-200 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Manage a security operations environment practice questions
Practise SC-200 questions linked to Manage a security operations environment.
Respond to security incidents practice questions
Practise SC-200 questions linked to Respond to security incidents.
Perform threat hunting practice questions
Practise SC-200 questions linked to Perform threat hunting.
Mitigate threats using Microsoft Defender XDR practice questions
Practise SC-200 questions linked to Mitigate threats using Microsoft Defender XDR.
Mitigate threats using Microsoft Defender for Cloud practice questions
Practise SC-200 questions linked to Mitigate threats using Microsoft Defender for Cloud.
Mitigate threats using Microsoft Sentinel practice questions
Practise SC-200 questions linked to Mitigate threats using Microsoft Sentinel.
SC-200 fundamentals practice questions
Practise SC-200 questions linked to SC-200 fundamentals.
SC-200 scenario practice questions
Practise SC-200 questions linked to SC-200 scenario.
SC-200 troubleshooting practice questions
Practise SC-200 questions linked to SC-200 troubleshooting.
Practice this exam
Start a free SC-200 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SC-200 question test?
Mitigate threats using Microsoft Defender XDR — This question tests Mitigate threats using Microsoft Defender XDR — KQL's `DeviceProcessEvents` table tracks process creation and termination..
What is the correct answer to this question?
The correct answer is: Use a self-join: query DeviceProcessEvents for mstsc.exe, extract the target device (e.g., from command line), and then join with another query on DeviceProcessEvents for PowerShell on the target device where the time difference between the events is less than 10 minutes. — Option A is correct because it uses a self-join on DeviceProcessEvents to first detect the mstsc.exe process (RDP client) on DeviceA, extract the target device name from the command line, and then join with a second query on DeviceProcessEvents for PowerShell on DeviceB. The join condition includes a time difference of less than 10 minutes, which directly correlates the lateral movement (RDP) with the subsequent malicious script execution across devices, matching the described attack pattern.
What should I do if I get this SC-200 question wrong?
Review kQL's `DeviceProcessEvents` table tracks process creation and termination., then practise related SC-200 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
KQL's `DeviceProcessEvents` table tracks process creation and termination.
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: Jun 11, 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.