Launch Deal · 50% off 1st month ·
← DP-700 study guide

Domain 2 – Ingest and Transform Data (30–35%)

8 lessons, each ending with a practice scenario (Pro)

Log in to save your progress.

  1. ✓2.1 — Design and Implement Full and Incremental LoadsA full load copies everything every time. An incremental load copies only what changed since the last successful run. Incremental loading is cheaper and faster, and it puts less load on the source. Full loads still make sense for small tables, or when the source can't tell you what changed.Scenario: Pro
  2. ✓2.2 — Prepare Data for a Dimensional ModelA star schema splits data into fact tables (measurable events such as sales or clicks, at one grain) and dimension tables (descriptive context such as product, customer and date). Preparing data for it means reshaping source rows, assigning keys and managing history.Scenario: Pro
  3. ✓2.3 — Choose a Data Store and a Transformation ToolMany DP-700 questions start with a team's skills, data shape and access pattern, then ask where to store the data or what to transform it with. Every Fabric store keeps its data in OneLake. Eventhouse data is the exception: it reaches OneLake only if you turn on OneLake availability.Scenario: Pro
  4. ✓2.4 — Create Shortcuts and Implement MirroringShortcuts and mirroring both bring outside data into OneLake without building an ETL process. A shortcut references data where it already lives, so nothing is copied. Mirroring continuously replicates a database into OneLake as Delta tables.Scenario: Pro
  5. ✓2.5 — Ingest Data by Using PipelinesThe pipeline Copy activity is Fabric's workhorse for moving data. It connects to dozens of sources, copies at scale, converts file formats and needs no code. Pipelines wrap it in loops, conditions, retries and alerts.Scenario: Pro
  6. ✓2.6 — Transform Data with PySpark, SQL and KQLThe exam expects you to read transformation code in three languages and choose the line that does the job. The same five tasks come up again and again: denormalize, aggregate, remove duplicates, handle missing values, handle late-arriving data.Scenario: Pro
  7. ✓2.7 — Streaming Loads, Engines and EventstreamsStreaming data arrives continuously and has to be processed within seconds or minutes, not in nightly batches. Fabric has three streaming engines. They often work together: an eventstream ingests and routes the events, then an eventhouse (KQL) or Spark Structured Streaming processes them.Scenario: Pro
  8. ✓2.8 — Spark Structured Streaming, KQL and Windowing FunctionsThis skill is code-level streaming. You process a stream with Spark Structured Streaming into Delta tables, process it with KQL in an eventhouse, and group events into time windows.Scenario: Pro
Domain recapQuick overview of all lessons
  • Design full and incremental loads, and prepare data for a dimensional model
  • Choose the right data store and transformation tool for the team and the workload
  • Bring data in with shortcuts, mirroring, pipelines and Copy jobs
  • Transform batch data with PySpark, SQL and KQL: denormalize, aggregate, and handle duplicate, missing and late-arriving data
  • Choose a streaming engine and process streams with eventstreams, Spark Structured Streaming, KQL and windowing functions
Next domain

Domain 3: Monitor and optimize an analytics solution →