Scheduled Query Rules for Multi-Table Correlation
A security team uses Microsoft Sentinel. They want to create a custom detection rule that identifies a potential data exfiltration scenario: when a user signs in from an unusual location and then, within 30 minutes, performs a large download from Azure Blob Storage. They need to correlate sign-in logs from Azure AD with storage diagnostic logs. Which type of analytics rule should they create in Microsoft Sentinel?
Quick Answer
The answer is a scheduled query rule using KQL. This is the correct choice because it is the only Microsoft Sentinel analytics rule type that supports custom Kusto Query Language logic for multi-table correlation, allowing you to join Azure AD sign-in logs (SigninLogs) with Azure Storage diagnostic logs (StorageBlobLogs) on a user identifier and enforce a 30-minute time window between the unusual sign-in and the large blob download. On the AZ-500 exam, this scenario tests your understanding of how to build custom detection rules for complex, time-sensitive threats that span multiple data sources, often appearing as a scenario-based question where you must distinguish scheduled query rules from NRT, anomaly, or fusion rules. A common trap is choosing a fusion rule, which relies on built-in machine learning correlations rather than custom KQL joins. Memory tip: think “Scheduled = SQL-like joins across tables” — if you need to write a JOIN with a WHERE clause on time, you need a scheduled query rule.
⚠ Common exam trap
Candidates often confuse NRT rules with scheduled queries, assuming NRT's low latency is better for time-sensitive correlations, but NRT rules cannot handle multi-table joins or extended time windows, making scheduled queries the only viable option 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
✓
A scheduled query rule using KQL
A scheduled query rule is correct because it allows you to write a KQL query that joins Azure AD sign-in logs (SigninLogs) with Azure Storage diagnostic logs (StorageBlobLogs) based on a user identifier, and then uses a time window (e.g., 30 minutes) to correlate the two events. This is the only rule type that supports custom KQL logic for multi-table joins and time-based correlation, which is essential for detecting the described exfiltration pattern.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A scheduled query rule using KQL
Why this is correct
Scheduled rules can run KQL queries that join multiple tables (e.g., SigninLogs and StorageBlobLogs) to correlate events and trigger alerts when the pattern is detected.
- ✗
An NRT (near-real-time) rule
Why it's wrong here
NRT rules provide low-latency detection but cannot join multiple data sources, which is required for correlating sign-ins and storage access.
- ✗
A fusion rule
Why it's wrong here
Fusion rules use advanced correlation to identify multi-stage attacks, but they are not customizable for specific user-defined patterns.
- ✗
A machine learning-based analytics rule
Why it's wrong here
ML-based rules use built-in anomaly detection models and are not designed for custom correlation of specific event sequences.
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
About these practice questions
This AZ-500 question is part of Courseiva's 194-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 AZ-500
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. A security team uses Microsoft Sentinel. They want to create a custom analytics rule that detects when a user account is created in Azure AD and then within 5 minutes attempts to access a sensitive SharePoint site. What should they use to correlate these two events?
medium- ✓ A.KQL query with join on UserId
- B.Watchlist
- C.Automation rule
- D.Playbook
Why A: A KQL query with a join on UserId allows you to correlate two separate tables—such as AuditLogs for user creation and SharePoint access logs—based on a common field (UserId) within a specified time window (5 minutes). This is the standard method in Microsoft Sentinel for creating multi-event detection rules that require temporal correlation between distinct activities.
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.