AZ-500 Manage identity and access Practice Question
A security team uses Microsoft Sentinel. They want to detect a potential privilege escalation scenario: when a user is added to the Global Administrator role in Azure AD (audit log) and within 10 minutes that user signs in from a suspicious location (sign-in log). Which type of analytics rule should they create to correlate these two different log sources?
⚠ Common exam trap
Watch out — candidates often confuse Fusion rules (which correlate alerts) with the need to correlate raw log entries, or they mistakenly think NRT rules can handle multi-table joins with custom time windows, when in fact only scheduled query rules provide the necessary KQL flexibility for this scenario.
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
✓
Scheduled query rule
A scheduled query rule is the correct choice because it allows you to define a KQL query that joins the AuditLogs table (for role assignment events) with the SigninLogs table (for sign-in events) and then uses a time window (e.g., 10 minutes) to correlate the two disparate log sources. This rule type supports cross-table joins and custom time-based correlation, which is exactly what is needed to detect a user added to Global Administrator followed by a suspicious sign-in.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Fusion rule
Why it's wrong here
Fusion rules are built-in, Microsoft-managed analytics rules that leverage machine learning to correlate alerts from multiple security products into a multi-stage attack story. They do not accept custom KQL queries or allow users to specify cross-table join logic, so they cannot be adapted for a custom detection based on specific correlation requirements.
- ✓
Scheduled query rule
Why this is correct
Scheduled query rules are the correct choice because they let you author custom KQL queries that join multiple tables such as SecurityEvent, SigninLogs, and CommonSecurityLog to correlate events across data sources. By setting a query schedule and alert logic, you can precisely define the multi-source correlation the security team needs.
- ✗
Anomaly rule
Why it's wrong here
Anomaly rules use built-in machine learning models to detect outliers against a learned baseline for individual data sources, such as user sign-ins or behavior from a specific product. They do not support custom KQL joins across different tables, so they cannot correlate events from multiple sources to uncover a custom multi-event attack pattern.
- ✗
NRT rule (Near Real-Time)
Why it's wrong here
Near Real-Time (NRT) rules are a specific category of scheduled query rules designed for 1-minute latency, but they restrict query syntax and data set size to maintain speed. While they can join some tables, the limited query complexity and lack of support for certain operators make them less suitable for complex cross-source correlation, making the broader 'Scheduled query rule' category the correct answer.
Go deeper
Related to this question
About these practice questions
One of 194 original AZ-500 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-500 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 AZ-500 exam.