mediummultiple choiceObjective-mapped

A help desk engineer needs a Log Analytics query that returns each computer whose most recent heartbeat is older than 20 minutes. Which query should they use?

Question 1mediummultiple choice
Full question →

A help desk engineer needs a Log Analytics query that returns each computer whose most recent heartbeat is older than 20 minutes. Which query should they use?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Heartbeat | where TimeGenerated < ago(20m) | summarize LastSeen = max(TimeGenerated) by Computer

This can return computers that also sent a recent heartbeat, because the newer data is filtered out before summarizing.

B

Best answer

Heartbeat | summarize LastSeen = max(TimeGenerated) by Computer | where LastSeen < ago(20m)

This query first finds the latest heartbeat per computer and then filters for machines whose latest timestamp is older than 20 minutes. That matches the operational requirement exactly and avoids false positives caused by filtering before summarization.

C

Distractor review

Heartbeat | summarize count() by Computer | where count_ < 20

Heartbeat count does not indicate when the last record was received, so a low count does not prove the computer has been silent for 20 minutes.

D

Distractor review

Heartbeat | where TimeGenerated > ago(20m) | summarize LastSeen = max(TimeGenerated) by Computer

This query shows machines that have had recent heartbeats, which is the opposite of the requested output.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Heartbeat | summarize LastSeen = max(TimeGenerated) by Computer | where LastSeen < ago(20m) — The key requirement is to identify the most recent heartbeat for each computer and compare that timestamp to a 20-minute threshold. By summarizing first with max(TimeGenerated), the query calculates the latest observed heartbeat per computer. The subsequent where clause then returns only the machines whose last heartbeat is too old, which is the correct operational troubleshooting result. Why others are wrong: A is wrong because filtering before summarizing can hide recent heartbeats and produce misleading results. C is wrong because record count does not measure recency. D is wrong because it returns active systems instead of silent ones.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.