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.
AZ-500 Manage identity and access Practice Question
This AZ-500 practice question tests your understanding of manage identity and access. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: scheduled query rules run KQL queries at defined intervals.. 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 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?
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.
B
An NRT (near-real-time) rule
Why wrong: NRT rules provide low-latency detection but cannot join multiple data sources, which is required for correlating sign-ins and storage access.
C
A fusion rule
Why wrong: Fusion rules use advanced correlation to identify multi-stage attacks, but they are not customizable for specific user-defined patterns.
D
A machine learning-based analytics rule
Why wrong: ML-based rules use built-in anomaly detection models and are not designed for custom correlation of specific event sequences.
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.
Key principle: Scheduled query rules run KQL queries at defined intervals.
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.
Related concept
Scheduled query rules run KQL queries at defined intervals.
✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that 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.
Detailed technical explanation
How to think about this question
Under the hood, a scheduled query rule in Microsoft Sentinel runs on a recurring interval (e.g., every 5 minutes) and can query data from multiple tables using KQL's join operator with a time window constraint (e.g., `where TimeGenerated between (SigninTime .. SigninTime + 30m)`). This enables precise correlation of events across Azure AD and Azure Storage, leveraging the `UserPrincipalName` or `ObjectId` field in SigninLogs and the `CallerIpAddress` or `UserAgent` in StorageBlobLogs. In a real-world scenario, an attacker might use stolen credentials to sign in from a foreign IP and then script a bulk download from a storage account; the scheduled query can flag this by matching the IP and user within the 30-minute window.
KKey Concepts to Remember
Scheduled query rules run KQL queries at defined intervals.
They can join multiple data tables (e.g., SigninLogs, StorageBlobLogs).
Scheduled rules are highly customizable for specific detection logic.
They are suitable for correlating events across different log sources and time windows.
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
Scheduled query rules run KQL queries at defined intervals.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-500 question in full detail.
Manage identity and access — This question tests Manage identity and access — Scheduled query rules run KQL queries at defined intervals..
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this AZ-500 question wrong?
Review scheduled query rules run KQL queries at defined intervals., then practise related AZ-500 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Scheduled query rules run KQL queries at defined intervals.
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 →
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: Option A is correct because 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.
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.
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.
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.