Flattening related tables into one wide, denormalized shape
Denormalizing data means combining data from multiple normalized tables into fewer, wider tables optimized for analytical read performance, typically by pre-joining dimension and fact data. In Microsoft Fabric, this is commonly done using Dataflows Gen2, notebooks (PySpark/Spark SQL), or pipeline Copy/Data Flow activities when preparing data for the silver or gold layer in a lakehouse or warehouse.
Must-know
- Denormalization trades storage space and redundancy for query performance by reducing the number of joins needed at query time, which is especially valuable for Power BI direct query and analytical workloads.
- In the medallion architecture, denormalization typically happens when moving data from the silver (cleansed, normalized) layer to the gold (business-ready, aggregated/denormalized) layer.
- Common techniques in Fabric include using Spark notebooks with DataFrame joins, Dataflows Gen2 Merge queries, or T-SQL JOINs in a Fabric Warehouse to flatten star-schema fact/dimension tables into a single wide table.
- A key gotcha is that denormalized tables increase storage and can introduce data update anomalies, so they are best suited for read-heavy reporting layers rather than transactional/OLTP-style processing.
- When denormalizing in Spark notebooks, broadcast joins can be used to efficiently join a large fact table with smaller dimension tables and avoid costly shuffles.
- Denormalized outputs are often materialized as Delta tables in the lakehouse (or tables in the warehouse) so downstream consumers like Power BI can query them directly without needing to perform joins.
A data engineer is preparing normalized source tables in a Fabric lakehouse for use in a Power BI semantic model. The engineer decides to denormalize several related tables into a single flat table before the report team consumes the data. Which outcome best describes the primary goal of this denormalization 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.