Question 1,035 of 1,170
Monitor and Maintain Azure ResourceseasyMultiple SelectObjective-mapped

KQL Filtering with where and ago()

This AZ-104 practice question tests your understanding of monitor and maintain azure resources. 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. 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 help desk analyst needs to find Azure VM heartbeat records in Log Analytics and limit results to the last 30 minutes. Which two KQL elements should be used? Select two.

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

where

The `where` operator filters the result set based on a specified condition, which is essential for limiting records to those with a timestamp within the last 30 minutes. The `ago()` function returns a datetime value representing the current time minus a given timespan, allowing you to create a dynamic filter like `where TimeGenerated > ago(30m)`. Together, they enable precise time-based filtering in Kusto Query Language (KQL) for Log Analytics.

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.

  • where

    Why this is correct

    The where clause filters rows, such as limiting records by time or status.

    Related concept

    Read the scenario before looking for a memorised answer.

  • ago()

    Why this is correct

    The ago() function creates a relative time boundary such as the last 30 minutes.

    Related concept

    Read the scenario before looking for a memorised answer.

  • summarize

    Why it's wrong here

    Summarize aggregates rows, but it is not the simplest way to filter recent heartbeats.

    When this WOULD be correct

    A question that asks: 'Which KQL element should be used to count the number of heartbeat records per hour for the last 24 hours?' In that case, summarize with bin(TimeGenerated, 1h) would be correct to group and count records.

  • join

    Why it's wrong here

    Join combines tables, which is unnecessary for a basic heartbeat time filter.

    When this WOULD be correct

    A question asks: 'You need to combine heartbeat records from two different Azure VMs into a single result set based on a common field like ResourceId.' In that case, 'join' would be correct.

  • extend

    Why it's wrong here

    Extend creates calculated columns, but it does not directly filter recent records.

    When this WOULD be correct

    When you need to add a new column to query results, such as calculating uptime from heartbeat timestamps, 'extend' is correct. For example: 'Heartbeat | extend Uptime = now() - TimeGenerated'.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

whereCorrect answer

Why this is correct

The where clause filters rows, such as limiting records by time or status.

summarizeWrong answer — click to see why

Why this is wrong here

The question asks for filtering heartbeat records to the last 30 minutes, which requires a time filter (where with ago()) and not aggregation. summarize is used for aggregating data (e.g., count, average), not for filtering time ranges.

★ When this WOULD be the correct answer

A question that asks: 'Which KQL element should be used to count the number of heartbeat records per hour for the last 24 hours?' In that case, summarize with bin(TimeGenerated, 1h) would be correct to group and count records.

Why candidates choose this

Candidates may confuse filtering with aggregation, thinking that summarizing data by time is the same as limiting results to a time range, or they may misread the question as requiring a count of heartbeats.

joinWrong answer — click to see why

Why this is wrong here

The 'join' operator is used to combine rows from two tables based on a matching key, not to filter time-based data. It does not limit results to the last 30 minutes.

★ When this WOULD be the correct answer

A question asks: 'You need to combine heartbeat records from two different Azure VMs into a single result set based on a common field like ResourceId.' In that case, 'join' would be correct.

Why candidates choose this

Candidates may think 'join' is needed to merge heartbeat data from multiple sources, but the question only requires filtering a single table by time.

extendWrong answer — click to see why

Why this is wrong here

The 'extend' operator creates calculated columns but does not filter data by time. To limit results to the last 30 minutes, you need a time filter using 'where' with 'ago()'.

★ When this WOULD be the correct answer

When you need to add a new column to query results, such as calculating uptime from heartbeat timestamps, 'extend' is correct. For example: 'Heartbeat | extend Uptime = now() - TimeGenerated'.

Why candidates choose this

Candidates may think 'extend' can filter time by adding a time-related column, confusing column creation with row filtering.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Common exam traps

Common exam trap: answer the scenario, not the keyword

Microsoft often tests the misconception that `summarize` or `extend` can filter data by time, but only `where` with a time-based condition like `ago()` actually removes rows from the result set.

Detailed technical explanation

How to think about this question

Under the hood, `ago(30m)` is evaluated at query execution time, converting to an absolute UTC timestamp (e.g., 2025-03-28T14:00:00Z) that is compared against the `TimeGenerated` column in the Heartbeat table. Log Analytics uses a time-series index for the `TimeGenerated` column, so the `where` clause with `ago()` can leverage this index for efficient scanning, avoiding full table scans even in large workspaces. In real-world scenarios, this pattern is critical for real-time monitoring dashboards where stale data must be excluded to avoid false alerts.

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

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.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-104 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-104 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-104 question test?

Monitor and Maintain Azure Resources — This question tests Monitor and Maintain Azure Resources — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: where — The `where` operator filters the result set based on a specified condition, which is essential for limiting records to those with a timestamp within the last 30 minutes. The `ago()` function returns a datetime value representing the current time minus a given timespan, allowing you to create a dynamic filter like `where TimeGenerated > ago(30m)`. Together, they enable precise time-based filtering in Kusto Query Language (KQL) for Log Analytics.

What should I do if I get this AZ-104 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More AZ-104 practice questions

Last reviewed: Jun 30, 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-104 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-104 exam.