Microsoft Defender for Identity: Monitored Activities
Your organization is implementing Microsoft Defender for Identity to protect on-premises Active Directory. Which THREE activities does Defender for Identity monitor?
Quick Answer
The answer is reconnaissance attacks using LDAP queries, lateral movement paths, and privilege escalation. Defender for Identity monitors these specific on-premises Active Directory activities because they represent the core stages of a cyberattack chain: reconnaissance via LDAP queries reveals how attackers map the environment, lateral movement paths show potential routes to high-value accounts, and privilege escalation indicates an attempt to gain elevated access. On the Microsoft Cybersecurity Architect exam, this question tests your ability to distinguish Defender for Identity’s scope from other Microsoft security tools—a common trap is confusing it with file integrity monitoring (Defender for Servers) or network traffic monitoring (Defender for Network). Remember that Defender for Identity is laser-focused on identity-based attack behaviors within AD, not files or internet traffic. A helpful memory tip: think “R-L-P” for Recon, Lateral movement, Privilege escalation—the three pillars of identity threat detection.
⚠ Common exam trap
A common trap is confusing file integrity monitoring with identity-based monitoring. Defender for Identity focuses on user behaviors and authentication patterns, not file changes.
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
✓
Privilege escalation attempts
Correct answers: A, B, D. Defender for Identity monitors privilege escalation attempts (A) by detecting suspicious changes in user privileges. Lateral movement paths using Pass-the-Hash (B) are detected by analyzing network activity and authentication patterns. Reconnaissance attacks using LDAP queries (D) are identified by unusual LDAP search patterns. Option C is incorrect: file integrity changes on domain controllers are monitored by Defender for Servers or Azure Policy, not Defender for Identity. Option E is incorrect: network traffic to external IP addresses is monitored by Defender for Network or network security groups, not Defender for Identity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Privilege escalation attempts
Why this is correct
Defender for Identity monitors for privilege escalation.
- ✓
Lateral movement paths using Pass-the-Hash
Why this is correct
Defender for Identity detects lateral movement techniques.
- ✗
File integrity changes on domain controllers
Why it's wrong here
File integrity monitoring is not a primary Defender for Identity feature.
- ✓
Reconnaissance attacks using LDAP queries
Why this is correct
Defender for Identity detects reconnaissance activities.
- ✗
Network traffic to external IP addresses
Why it's wrong here
Network traffic monitoring is outside Defender for Identity scope.
Go deeper
Related to this question
About these practice questions
This SC-100 question is part of Courseiva's 208-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 →
Same concept, more angles
1 more way this is tested on SC-100
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your organization uses Microsoft Defender for Identity (MDI) to protect on-premises Active Directory. You need to integrate MDI with Microsoft Sentinel to centralize detection and response. What is the required configuration?
medium- A.Deploy the MDI sensor on an Azure VM to send data to Sentinel.
- B.Integrate Microsoft Entra ID Protection with Sentinel instead.
- ✓ C.Enable the Microsoft Defender for Identity data connector in Microsoft Sentinel.
- D.Configure MDI to forward logs to a Syslog server, then use the Syslog connector in Sentinel.
Why C: The Microsoft Defender for Identity data connector in Microsoft Sentinel enables ingestion of MDI alerts and events, integrating on-premises AD protection with cloud-based SIEM. Option A is incorrect because the MDI sensor is already deployed on-premises; deploying it on an Azure VM is unnecessary. Option B is incorrect because Microsoft Entra ID Protection focuses on cloud identities, not on-premises AD. Option D is incorrect because MDI does not natively forward alerts to Syslog; it uses its own connector in Sentinel.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SC-100 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-100 exam.