The correct answer is to configure incident grouping in the scheduled analytics rule. This setting allows multiple alerts triggered by the same entity—such as the same user account—within a defined time window to be merged into a single incident, which directly addresses the SOC’s need to consolidate brute-force alerts for the same account within an hour. On the Microsoft Azure Security Engineer Associate AZ-500 exam, this concept tests your understanding of how Sentinel analytics rules manage alert-to-incident conversion, specifically the “Group related alerts into a single incident” toggle and the grouping window parameter. A common trap is assuming that changing the alert creation frequency or entity mapping alone will merge incidents; instead, incident grouping is the explicit mechanism. For a memory tip, think of it as “same entity, same window, one incident”—if the brute-force activity targets the same account within the grouping window, incident grouping bundles them into a single, manageable case.
AZ-500 Manage identity and access Practice Question
This AZ-500 practice question tests your understanding of manage identity and access. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 Sentinel analytics rule creates a new incident every time the same brute-force activity is detected for the same account within an hour. The SOC wants one incident that continues to group related alerts. What should be changed?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure incident grouping in the scheduled analytics rule
Option B is correct because incident grouping in a scheduled analytics rule allows multiple alerts triggered by the same entity (e.g., the same account) within a specified time window to be combined into a single incident. By configuring the 'Group related alerts into a single incident' setting and setting the grouping window to one hour, the SOC ensures that all brute-force alerts for the same account are merged into one incident, reducing alert fatigue and providing a consolidated view of the attack.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Disable entity mapping for the account entity
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
✓
Configure incident grouping in the scheduled analytics rule
Why this is correct
Correct for the stated requirement.
Related concept
Read the scenario before looking for a memorised answer.
✗
Change the rule query to use project-away on TimeGenerated
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
✗
Run the rule as a near-real-time rule
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse incident grouping with alert suppression or think that disabling entity mapping will reduce noise, but entity mapping is actually required for grouping to work correctly.
Detailed technical explanation
How to think about this question
Under the hood, incident grouping in Microsoft Sentinel uses the 'Grouping configuration' within the analytics rule to define a 'Time window' (e.g., 1 hour) and 'Grouping key' (e.g., Account entity). The rule's query results are evaluated, and if multiple results share the same grouping key within the window, they are merged into a single incident with all related alerts attached. A subtle behavior is that the grouping window resets after each new alert, so if an alert occurs at minute 59 and another at minute 61, they may fall into separate incidents unless the window is set to 'Reset grouping' appropriately.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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 — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure incident grouping in the scheduled analytics rule — Option B is correct because incident grouping in a scheduled analytics rule allows multiple alerts triggered by the same entity (e.g., the same account) within a specified time window to be combined into a single incident. By configuring the 'Group related alerts into a single incident' setting and setting the grouping window to one hour, the SOC ensures that all brute-force alerts for the same account are merged into one incident, reducing alert fatigue and providing a consolidated view of the attack.
What should I do if I get this AZ-500 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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.