Skip to content

Querying and reshaping event data with KQL

In Microsoft Fabric, KQL (Kusto Query Language) is used to query and transform data stored in Eventhouse KQL databases, typically for real-time or high-volume analytical workloads. Learners create KQL Querysets to write, run, and save KQL queries against tables, and can also use KQL for lightweight transformations before or during ingestion.

1 · Learn the must-know

  • KQL queries follow a tabular, pipe (|) based syntax where operators like where, extend, summarize, and project are chained left to right to progressively filter and shape data.
  • The 'let' statement can define reusable variables or scalar/tabular expressions to simplify complex queries.
  • Update policies allow automatic transformation of data as it lands in a source table, writing derived/transformed results into a target table without manual re-run of queries.
  • The mv-expand operator is used to expand dynamic (JSON-like) arrays or property bags into multiple rows for easier analysis.
  • KQL Querysets in Fabric can connect to one or more KQL databases (and cross-query with Lakehouse/Warehouse via appropriate connectors), and results can be visualized or pinned to dashboards.
  • Functions such as bin(), ago(), and datetime() are commonly used for time-series bucketing and filtering, which is a core use case for KQL-based Eventhouse data.

2 · Check your understanding

Check this objectiveFree · always available

A data engineer has a KQL database table named DeviceEvents that stores IoT telemetry with an EventTime column (datetime) and a Value column (real). The engineer needs a query that returns the number of events for each consecutive 5-minute time window. Which query meets this requirement?

Your objective map0 tried · 0 answered correctly · 54 untouched

What you have tried across DP-700's objectives, not a readiness score.

Implement and manage an analytics solution30-35% of the exam0 of 18 tried
Ingest and transform data30-35% of the exam0 of 19 tried
Monitor and optimize an analytics solution30-35% of the exam0 of 17 tried

3 · Keep going