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

Domain 2 – Prepare Data (45–50%)

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

Log in to save your progress.

  1. ✓2.1 — Connect To and Discover DataPreparing data starts with finding it and connecting to it securely. Fabric gives you catalogs for discovery and reusable connections for access.Scenario: Pro
  2. ✓2.2 — Ingest, Copy and Schedule DataFabric has five ways to bring data in. The exam asks you to pick the right one from the source, volume, transformation needs and team skills, and then to schedule and orchestrate it.Scenario: Pro
  3. ✓2.3 — Choose a Store, Use OneLake Integration and Partition FilesAn analytics engineer chooses where curated data lives (lakehouse, warehouse or eventhouse), knows how to make data from any engine available in OneLake, and lays out large lakehouse tables so that queries read less.Scenario: Pro
  4. ✓2.4 — Create Views, Functions and Stored Procedures, and Enrich DataT-SQL objects package logic so that it's reusable, secured and close to the data. Where you can create them depends on the item.Scenario: Pro
  5. ✓2.5 — Star Schemas, Slowly Changing Dimensions and Bridge TablesA semantic model is only as good as the tables under it. Building a star schema in the lakehouse or warehouse (the gold layer) is core DP-600 work.Scenario: Pro
  6. ✓2.6 — Cleanse and Shape DataDP-600 lists a set of shaping skills: cleanse, denormalize, aggregate or de-aggregate, merge or join, fix duplicates, missing values and nulls, convert types, filter. You should be able to do each one in SQL, PySpark and Power Query, and spot the right line of code.Scenario: Pro
  7. ✓2.7 — Query Data with SQL and the Visual Query EditorAnalytics engineers explore and validate data with T-SQL, either written by hand or built with the visual query editor, against warehouses and lakehouse SQL analytics endpoints. Exam items show a query and ask what it returns, or ask which clause to change.Scenario: Pro
  8. ✓2.8 — Query Data with KQLKusto Query Language (KQL) queries data in eventhouses and KQL databases. It reads top to bottom as a pipeline of operators joined by the pipe character. You need to be able to select, filter and aggregate with it, and read short queries.Scenario: Pro
  9. ✓2.9 — Optimize Loading Performance and Delta File SizesDP-600 asks you to find and fix bottlenecks in dataflows, notebooks and SQL, and to fix Delta tables whose files are too small or too many. These tables slow down every engine that reads them, Direct Lake included.Scenario: Pro
Domain recapQuick overview of all lessons
  • Get data: discover it in the OneLake catalog and Real-Time hub, connect through managed connections and gateways, and choose between a lakehouse, warehouse and eventhouse
  • Ingest, copy and schedule with pipelines, Copy jobs, dataflows, notebooks and shortcuts, and use OneLake integration for eventhouses and semantic models
  • Transform data: views, functions and stored procedures, star schemas with SCD Type 1 and 2, bridge tables, cleansing, joins, aggregation, deduplication, nulls and type conversion
  • Query and analyze data with SQL, the visual query editor and KQL
  • Optimize dataflows, notebooks, SQL loads and Delta table file sizes
Next domain

Domain 3: Implement and manage semantic models →