The answer is `where TimeGenerated >= ago(30m)`. This KQL where clause filter for the last 30 minutes works by using the `ago()` function, which dynamically calculates a datetime exactly 30 minutes before the current moment, and the `>=` operator ensures only records with a `TimeGenerated` timestamp at or after that point are returned. On the AZ-104 exam, this tests your ability to write time-based filters in Kusto Query Language, often appearing in log analytics scenarios where you must isolate recent heartbeat or health data. A common trap is confusing `ago()` with `now()` or forgetting the comparison operator—using `>` instead of `>=` would exclude records exactly 30 minutes old. Memory tip: think of `ago(30m)` as “30 minutes ago from now,” and always pair it with `>=` to catch everything from that moment forward.
AZ-104 Monitor and Maintain Azure Resources Practice Question
This AZ-104 practice question tests your understanding of monitor and maintain azure resources. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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.
Exhibit
KQL draft:
Heartbeat
| __________
| summarize LastSeen = max(TimeGenerated) by Computer
Requirement: show only records from the last 30 minutes before summarizing.
Based on the exhibit, which KQL clause should replace the blank to show only heartbeat records from the last 30 minutes?
KQL draft:
Heartbeat
| __________
| summarize LastSeen = max(TimeGenerated) by Computer
Requirement: show only records from the last 30 minutes before summarizing.
A
project Computer, TimeGenerated
Why wrong: Project changes the columns returned, but it does not limit the records by time.
B
where TimeGenerated >= ago(30m)
The where clause filters rows before summarizing, and ago(30m) is the KQL function that represents the last 30 minutes from the current time. This is the correct way to restrict the Heartbeat table to recent records before calculating the most recent check-in for each computer. It is a standard operational troubleshooting pattern in Log Analytics.
C
extend TimeWindow = 30m
Why wrong: Extend creates a new calculated column, but it does not filter the table to recent records.
D
sort by TimeGenerated desc
Why wrong: Sorting changes the order of results, but it does not exclude older heartbeat records from the query.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
where TimeGenerated >= ago(30m)
The KQL clause `where TimeGenerated >= ago(30m)` filters the results to include only records where the `TimeGenerated` timestamp is within the last 30 minutes. The `ago()` function calculates a datetime value relative to the current time, and the `>=` operator ensures only records from that point forward are returned. This directly satisfies the requirement to show heartbeat records from the last 30 minutes.
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.
✗
project Computer, TimeGenerated
Why it's wrong here
Project changes the columns returned, but it does not limit the records by time.
✓
where TimeGenerated >= ago(30m)
Why this is correct
The where clause filters rows before summarizing, and ago(30m) is the KQL function that represents the last 30 minutes from the current time. This is the correct way to restrict the Heartbeat table to recent records before calculating the most recent check-in for each computer. It is a standard operational troubleshooting pattern in Log Analytics.
Related concept
Read the scenario before looking for a memorised answer.
✗
extend TimeWindow = 30m
Why it's wrong here
Extend creates a new calculated column, but it does not filter the table to recent records.
✗
sort by TimeGenerated desc
Why it's wrong here
Sorting changes the order of results, but it does not exclude older heartbeat records from the query.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse filtering (`where`) with projection (`project`), sorting (`sort`), or extending (`extend`), and may choose a clause that manipulates the output format or order instead of actually restricting the rows based on a time condition.
Detailed technical explanation
How to think about this question
The `ago()` function in Kusto Query Language (KQL) returns a datetime value representing the current UTC time minus the specified timespan (e.g., `ago(30m)` returns the timestamp 30 minutes before the query execution). This is evaluated at query runtime, making it dynamic and ideal for real-time monitoring scenarios. In Azure Monitor, heartbeat records from Azure Arc or Log Analytics agents include a `TimeGenerated` column that is set to the UTC time when the record was generated, so filtering with `ago()` ensures you only see recent agent connectivity data.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
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 TimeGenerated >= ago(30m) — The KQL clause `where TimeGenerated >= ago(30m)` filters the results to include only records where the `TimeGenerated` timestamp is within the last 30 minutes. The `ago()` function calculates a datetime value relative to the current time, and the `>=` operator ensures only records from that point forward are returned. This directly satisfies the requirement to show heartbeat records from the last 30 minutes.
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 →
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. Based on the exhibit, which KQL operator should replace the blank to return only those columns?
easy
A.where, because it filters rows and also selects the visible columns.
B.summarize, because it groups the failed records into a smaller result set.
✓ C.project, because it returns only the named columns in the result.
D.extend, because it creates new output columns for the selected fields.
Why C: The `project` operator in Kusto Query Language (KQL) is specifically designed to select a subset of columns from the input table, returning only the named columns in the result set. This matches the requirement to 'return only those columns,' making option C correct.
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-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.
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.