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: kQL is the query language for Azure Monitor Logs and Microsoft Sentinel.. 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 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?
KQL allows joining tables on common fields to correlate events across data sources, which is exactly what this scenario requires.
B
Watchlist
Why wrong: Watchlists are used to store and reference static data (e.g., known IP addresses) for enrichment, not for real-time correlation of events.
C
Automation rule
Why wrong: Automation rules trigger responses (e.g., tagging, running playbooks) after an alert is generated; they do not define the logic for correlation.
D
Playbook
Why wrong: Playbooks are workflows (often Logic Apps) that execute actions in response to alerts; they are not used for correlation logic within the analytics rule.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
KQL query with join on UserId
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.
Key principle: KQL is the query language for Azure Monitor Logs and Microsoft Sentinel.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
KQL query with join on UserId
Why this is correct
KQL allows joining tables on common fields to correlate events across data sources, which is exactly what this scenario requires.
Related concept
KQL is the query language for Azure Monitor Logs and Microsoft Sentinel.
✗
Watchlist
Why it's wrong here
Watchlists are used to store and reference static data (e.g., known IP addresses) for enrichment, not for real-time correlation of events.
✗
Automation rule
Why it's wrong here
Automation rules trigger responses (e.g., tagging, running playbooks) after an alert is generated; they do not define the logic for correlation.
✗
Playbook
Why it's wrong here
Playbooks are workflows (often Logic Apps) that execute actions in response to alerts; they are not used for correlation logic within the analytics rule.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse a Watchlist (used for static lookups) with a correlation mechanism, or mistakenly think Automation rules or Playbooks can perform event correlation, when in fact only KQL queries with joins can correlate multiple events in a single detection rule.
Detailed technical explanation
How to think about this question
Under the hood, the KQL join operation in Sentinel uses the `join` operator with a `where` clause to enforce a time window (e.g., `where TimeGenerated between (CreationTime .. CreationTime + 5m)`), leveraging the `UserId` field from Azure AD audit logs (e.g., `AuditLogs` table) and SharePoint access logs (e.g., `OfficeActivity` table). This approach requires careful handling of time zone differences and potential delays in log ingestion to avoid false negatives. In real-world scenarios, attackers often create a user and quickly attempt lateral movement, making this correlation critical for detecting privilege escalation or insider threats.
KKey Concepts to Remember
KQL is the query language for Azure Monitor Logs and Microsoft Sentinel.
The `join` operator in KQL combines records from different tables based on common values.
Custom analytics rules in Sentinel are defined using KQL queries.
Time-series analysis and windowing are performed in KQL using `where` clauses and time functions.
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
KQL is the query language for Azure Monitor Logs and Microsoft Sentinel.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-500 question in full detail.
Review kQL is the query language for Azure Monitor Logs and Microsoft Sentinel., then practise related AZ-500 questions on the same topic to reinforce the concept.
Manage identity and access — This question tests Manage identity and access — KQL is the query language for Azure Monitor Logs and Microsoft Sentinel..
What is the correct answer to this question?
The correct answer is: KQL query with join on UserId — 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.
What should I do if I get this AZ-500 question wrong?
Review kQL is the query language for Azure Monitor Logs and Microsoft Sentinel., then practise related AZ-500 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
KQL is the query language for Azure Monitor Logs and Microsoft Sentinel.
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 →
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.