Question 301 of 1,000
Manage identity and accessmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is a scheduled query rule. This is the correct choice because it allows you to define a KQL query that runs on a recurring schedule—such as every five minutes—to detect when an Azure VM is created with a public IP not in an approved list, using AzureActivity logs or Azure Resource Graph for periodic evaluation. On the Microsoft Azure Security Engineer Associate AZ-500 exam, this scenario tests your understanding of custom detection logic in Microsoft Sentinel, where scheduled query rules are the go-to for proactive, time-based monitoring, unlike NRT or fusion rules which serve different purposes. A common trap is confusing scheduled rules with analytics rules that trigger on specific events only; remember that scheduled rules are for recurring checks, not one-off alerts. Memory tip: think “Schedule = Scan,” meaning the rule scans logs on a timer to catch unauthorized public IPs.

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 on a defined schedule.. 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 operations team uses Microsoft Sentinel. They want to create a custom analytics rule that detects when an Azure virtual machine is created with a public IP address that is not in an approved list. Which type of rule should they use?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Scheduled query rule

A scheduled query rule is the correct choice because it allows you to define a KQL query that runs on a recurring schedule (e.g., every 5 minutes) to detect when an Azure VM is created with a public IP not in an approved list. This rule type is designed for custom detection logic that requires periodic evaluation of log data, such as AzureActivity logs or Azure Resource Graph, making it ideal for this scenario.

Key principle: Scheduled query rules run KQL queries on a defined schedule.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Scheduled query rule

    Why this is correct

    Correct. Scheduled query rules allow you to run a KQL query on a schedule and create incidents based on the results. This is ideal for checking new VM creations against an approved IP list.

    Related concept

    Scheduled query rules run KQL queries on a defined schedule.

  • NRT rule

    Why it's wrong here

    NRT (Near-Real-Time) rules run more frequently (every minute) but are still a type of scheduled query. However, they are designed for scenarios requiring low latency, not specifically for list-based checks. A standard scheduled query rule is simpler and sufficient.

  • Anomaly rule

    Why it's wrong here

    Anomaly rules use machine learning to detect unusual patterns, not static list matching. They are not suitable for checking against a fixed approved IP list.

  • Fusion rule

    Why it's wrong here

    Fusion rules correlate multiple alerts from different sources to detect multi-stage attacks. They are not used for single-event detection like a new VM creation.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse NRT rules with scheduled query rules, assuming NRT's lower latency is always better, but NRT rules lack the ability to reference external data sources like watchlists for dynamic approved IP comparisons.

Trap categories for this question

  • Scenario analysis trap

    NRT (Near-Real-Time) rules run more frequently (every minute) but are still a type of scheduled query. However, they are designed for scenarios requiring low latency, not specifically for list-based checks. A standard scheduled query rule is simpler and sufficient.

Detailed technical explanation

How to think about this question

Under the hood, a scheduled query rule in Microsoft Sentinel uses a KQL query that joins AzureActivity (e.g., 'Microsoft.Compute/virtualMachines/write') with a custom watchlist containing approved public IP ranges, filtering for IPs not in the list. The rule's schedule and alert threshold (e.g., 1 event) ensure timely detection, and it can trigger automated responses via playbooks. A real-world scenario is a SOC needing to enforce a policy that only specific public IPs are allowed on new VMs to reduce attack surface, where a scheduled query rule provides the flexibility to maintain an evolving approved list.

KKey Concepts to Remember

  • Scheduled query rules run KQL queries on a defined schedule.
  • They are used to detect specific patterns or conditions in log data.
  • Results from the query can generate security incidents in Sentinel.
  • Watchlists can be integrated with scheduled queries for list-based checks.

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 on a defined schedule.

Real-world example

How this comes up in practice

An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.

What to study next

Got this wrong? Here's your next step.

Review scheduled query rules run KQL queries on a defined schedule., then practise related AZ-500 questions on the same topic to reinforce the concept.

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.

Practice this exam

Start a free AZ-500 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-500 question test?

Manage identity and access — This question tests Manage identity and access — Scheduled query rules run KQL queries on a defined schedule..

What is the correct answer to this question?

The correct answer is: Scheduled query rule — A scheduled query rule is the correct choice because it allows you to define a KQL query that runs on a recurring schedule (e.g., every 5 minutes) to detect when an Azure VM is created with a public IP not in an approved list. This rule type is designed for custom detection logic that requires periodic evaluation of log data, such as AzureActivity logs or Azure Resource Graph, making it ideal for this scenario.

What should I do if I get this AZ-500 question wrong?

Review scheduled query rules run KQL queries on a defined schedule., 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 on a defined schedule.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on AZ-500

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 operations team uses Microsoft Sentinel. They want to create a rule that generates an incident when an Azure virtual machine is deployed with a public IP address that is not in a predefined approved list. The rule should run every hour and query Azure Activity logs. Which type of analytics rule should they create?

medium
  • A.Scheduled query rule
  • B.NRT (Near-Real-Time) rule
  • C.Anomaly rule
  • D.Fusion rule

Why A: A scheduled query rule is correct because the requirement specifies a rule that runs every hour and queries Azure Activity logs. Scheduled query rules in Microsoft Sentinel are designed for periodic, time-based queries against log data, such as Azure Activity logs, and can generate incidents based on predefined conditions like detecting a VM deployment with an unapproved public IP. This aligns perfectly with the need for a recurring, non-real-time check.

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.