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.
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.
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?
What you have tried across DP-700's objectives, not a readiness score.
Implement and manage an analytics solution
- Tuning a workspace's Spark compute defaults and pool sizing
- Grouping and governing workspaces with a Fabric domain
- Setting per-workspace defaults for OneLake storage
- Standing up an Airflow job runtime inside a workspace
- Connecting a workspace to a Git repository
- Managing schema changes with a database project
- Promoting Fabric items across environments with a deployment pipeline
- Granting and restricting access at the workspace level
- Locking down who can open a single Fabric item
- Layering row, column, object, and file-level security rules
- Hiding sensitive column values behind a dynamic mask
- Classifying Fabric items with a sensitivity label
- Marking a trusted item as promoted or certified
- Reading a Fabric audit log to see who did what
- Securing data at the OneLake storage layer
- Picking the right build tool among a dataflow, a pipeline, and a notebook
- Kicking off a job on a schedule or in response to an event
- Chaining notebooks and pipelines together with parameters and dynamic expressions
Ingest and transform data
- Deciding between a full reload and an incremental load
- Shaping source data ahead of a dimensional-model load
- Landing a continuous stream of data into storage
- Matching a workload to the right Fabric data store
- Picking a transformation tool from dataflows, notebooks, KQL, or T-SQL
- Linking to external data without copying it via a OneLake shortcut
- Keeping a source database continuously replicated into Fabric
- Moving data into Fabric with a data pipeline
- Writing transform logic in PySpark, SQL, or KQL
- Flattening related tables into one wide, denormalized shape
- Rolling records up with group-by aggregations
- Dealing with duplicate rows, gaps, and data that arrives late
- Selecting the right engine for a real-time workload
- Weighing storage-in-place against a linked shortcut for a Real-Time Intelligence table
- Weighing an accelerated shortcut against a standard one for query speed
- Routing and reshaping live events with an Eventstream
- Handling a continuous flow of records with Spark's structured streaming
- Querying and reshaping event data with KQL
- Aggregating a stream over sliding or tumbling time windows
Monitor and optimize an analytics solution
- Watching an ingestion job's health and progress
- Watching a transformation job's health and progress
- Tracking whether a semantic model's refresh actually succeeded
- Setting up an alert to catch a failure early
- Tracking down why a pipeline run failed and fixing it
- Diagnosing why a dataflow run failed
- Debugging a notebook run that failed
- Troubleshooting a misbehaving Eventhouse
- Troubleshooting a misbehaving Eventstream
- Debugging a T-SQL statement that failed
- Fixing a broken or unreachable shortcut
- Speeding up a Lakehouse table with maintenance operations
- Making a slow pipeline run faster
- Tuning a Fabric warehouse for faster queries
- Improving throughput on real-time streaming components
- Tuning a Spark job to run faster and cheaper
- Making a slow query run faster
Coverage checked against the published exam guide on Aug 11, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.