Question 1mediummultiple choice
Full question →mediummultiple choiceObjective-mapped
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?
Answer choices
Why each option matters
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
A
Distractor review
Fusion rule
Fusion rules use Microsoft's machine learning models to detect multi-stage attacks based on known patterns, and they cannot be customized for specific correlation logic.
B
Best answer
Scheduled query rule
Scheduled query rules allow you to write custom KQL queries that can join logs from different tables, enabling correlation events across data sources.
C
Distractor review
Anomaly rule
Anomaly rules use machine learning to detect deviations from baselines in a single data source; they do not support cross-table correlation.
D
Distractor review
NRT rule (Near Real-Time)
NRT rules are a subset of scheduled rules optimized for low-latency execution, but they still require KQL queries and can join data sources; however, the correct category is 'Scheduled query rule'.
Common exam trap
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Technical deep dive
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
- Authentication checks who the user is.
- Authorization controls what the user is allowed to do after login.
- Privilege levels affect access to EXEC and configuration commands.
- AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
- Do not assume successful login means full administrative access.
- Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
- Separate login problems from permission problems before choosing the answer.
Related practice questions
Related AZ-500 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
More questions from this exam
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
A DevOps team wants Defender for Cloud to identify secrets exposed in GitHub repositories. What should be configured?
Question 2
A public web application should be protected from OWASP-style attacks and network-layer DDoS attacks. Which two Azure services are most relevant?
Question 3
A Sentinel scheduled rule runs every 5 minutes and looks back 1 hour. Analysts see repeated alerts for the same event. Which change best prevents duplicate detections without missing late-arriving logs?
Question 4
A SOC analyst needs a Sentinel query that detects multiple failed sign-ins followed by a successful sign-in for the same user. Which table is the best primary source?
Question 5
A Sentinel watchlist contains high-value administrator accounts. Which KQL pattern best uses it in a detection rule?
Question 6
A SOC wants a Sentinel rule to include account, host, and IP entities so analysts can pivot during investigation. What should be configured in the analytics rule?
FAQ
Questions learners often ask
What does this AZ-500 question test?
Authentication checks who the user is.
What is the correct answer to this question?
The correct answer is: Scheduled query rule — Scheduled query rules in Microsoft Sentinel allow custom KQL queries that can join multiple tables (e.g., AuditLogs and SignInLogs) to correlate events over a specified time window. Fusion rules use pre-built machine learning models and do not support custom correlation logic. Anomaly rules are designed for single-source anomaly detection. NRT (near real-time) rules are similar to scheduled rules but focus on low-latency scenarios; however, the fundamental type that supports multi-table joins is 'Scheduled query rule'.
What should I do if I get this AZ-500 question wrong?
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Discussion
Loading comments…
Sign in to join the discussion.