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?
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.
Best answer
A scheduled query rule using KQL
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.
Distractor review
An NRT (near-real-time) rule
NRT rules provide low-latency detection but cannot join multiple data sources, which is required for correlating sign-ins and storage access.
Distractor review
A fusion rule
Fusion rules use advanced correlation to identify multi-stage attacks, but they are not customizable for specific user-defined patterns.
Distractor review
A machine learning-based analytics rule
ML-based rules use built-in anomaly detection models and are not designed for custom correlation of specific event sequences.
Common exam trap
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Technical deep dive
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
- Static NAT maps one inside address to one outside address.
- PAT allows many inside hosts to share one public address using ports.
- Inside local and inside global describe the private and translated addresses.
- NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
- Identify inside and outside interfaces first.
- Check whether the scenario needs static NAT, dynamic NAT or PAT.
- Do not confuse NAT matching ACLs with normal packet-filtering intent.
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?
Static NAT maps one inside address to one outside address.
What is the correct answer to this question?
The correct answer is: A scheduled query rule using KQL — Scheduled query rules allow you to run Kusto Query Language (KQL) queries at regular intervals to correlate data from multiple tables (e.g., SigninLogs and StorageBlobLogs) and detect patterns across time. NRT rules provide low latency but have limited capabilities and cannot join multiple data sources easily. Fusion rules are for multi-stage attack detection using correlation algorithms, not custom queries. ML-Based Analytics uses built-in machine learning models for anomaly detection, not custom event correlation.
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
Sign in to join the discussion.