easymultiple choiceObjective-mapped

Exhibit

AzureActivity sample rows:
TimeGenerated              OperationName           ActivityStatusValue   Caller
2026-04-26T08:00:00Z      Start Virtual Machine    Succeeded             alice@contoso.com
2026-04-26T08:05:00Z      Stop Virtual Machine     Failed                bob@contoso.com
2026-04-26T08:07:00Z      Restart Virtual Machine  Failed                carol@contoso.com

Based on the exhibit, you need to return only the failed operations from the log entries. Which KQL query should you use?

Question 1easymultiple choice
Full question →

Based on the exhibit, you need to return only the failed operations from the log entries. Which KQL query should you 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

Best answer

AzureActivity | where ActivityStatusValue == "Failed" | project TimeGenerated, OperationName, Caller

This filters the table to failed rows and keeps the useful columns for review.

B

Distractor review

AzureActivity | summarize count() by Caller

This groups results by caller, but it does not return only failed operations.

C

Distractor review

AzureActivity | top 10 by TimeGenerated

This shows the most recent entries, but it does not filter by failure status.

D

Distractor review

AzureActivity | where ActivityStatusValue == "Succeeded"

This returns successful operations, which is the opposite of the stated requirement.

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: AzureActivity | where ActivityStatusValue == "Failed" | project TimeGenerated, OperationName, Caller — In KQL, filtering the AzureActivity table with where ActivityStatusValue == "Failed" returns only records whose status is failed. Project keeps the useful columns for review. This directly answers the need to isolate failed operations from mixed success and failure entries. The exhibit shows both succeeded and failed actions, so a filter on the status column is required. Why others are wrong: Summarize aggregates data instead of listing only failed rows, so it cannot isolate the incidents. Top orders records by time but leaves both success and failure entries in the result. Filtering for succeeded rows is the opposite of the requirement and would hide the failures you are trying to investigate.

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.