Rolling records up with group-by aggregations
In Microsoft Fabric, grouping and aggregating data is a core transformation step used to summarize datasets by one or more columns, typically producing counts, sums, averages, or other statistical results. This can be accomplished through Power Query's Group By feature in Dataflows Gen2 and Data Pipelines, through Spark DataFrame operations (groupBy/agg) in Notebooks, or via SQL GROUP BY clauses in the Lakehouse SQL endpoint or Warehouse. Choosing the right tool depends on the ingestion pattern (low-code vs. code-first) and where the transformation logically fits in the medallion architecture.
Must-know
- Power Query's Group By dialog lets you group by one or more columns and apply aggregations (Sum, Average, Count, Min, Max, etc.) without writing code, and it generates an M query step behind the scenes.
- In Power Query, you can choose 'Basic' or 'Advanced' grouping mode; Advanced allows multiple group-by columns and multiple aggregated output columns in a single step.
- In Spark notebooks, groupBy() combined with agg() (or shorthand functions like sum(), count(), avg()) creates a new DataFrame with aggregated results, and results are lazily evaluated until an action is called.
- When aggregating in SQL (Lakehouse SQL endpoint or Warehouse), every non-aggregated column in the SELECT list must appear in the GROUP BY clause, or the query will error.
- A common gotcha: grouping and aggregating early in a pipeline (bronze/silver) can improve downstream performance, but doing so too early may cause loss of granular data needed for later transformations or auditing.
- Aggregations performed in Dataflows Gen2 are computed within the Power Query mashup engine, which may have different performance characteristics than pushing aggregation logic down to Spark or the SQL engine for large-scale data.
A data engineer is building a Dataflow Gen2 in Fabric to summarize an orders table. In the Group By transformation, they need to group by Region and, in the same step, calculate the total revenue (sum), the number of orders (count), and the most recent order date (max) for each region. Which approach in the Group By dialog achieves this in a single transformation step?
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.