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

Domain 3 – Implement and Manage Semantic Models (25–30%)

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

Log in to save your progress.

  1. ✓3.1 — Choose a Storage Mode, Including Direct LakeStorage mode is a property of each table in a semantic model. It decides where the data lives at query time, how fresh it is, and how fast visuals respond.Scenario: Pro
  2. ✓3.2 — Star Schema and Relationships in a Semantic ModelPower BI models are built for star schemas. Relationships carry filters from dimensions to facts, and most modeling questions are really about cardinality, filter direction and many-to-many cases.Scenario: Pro
  3. ✓3.3 — DAX Calculations: Variables, Iterators, Filtering, Windowing and Information FunctionsDP-600 tests whether you can read and choose DAX. The skills outline names four families: iterators, table filtering, windowing and information functions, plus variables.Scenario: Pro
  4. ✓3.4 — Calculation Groups, Dynamic Format Strings and Field ParametersThese three features make models smaller and more flexible. Instead of writing 30 measures (10 base measures × YTD, PY, YoY), you write the logic once and let users switch.Scenario: Pro
  5. ✓3.5 — Large Semantic Models, Composite Models and AggregationsEnterprise models outgrow default limits. You can raise the limits with the large semantic model storage format, or keep the detail at the source with composite models and aggregations.Scenario: Pro
  6. ✓3.6 — Implement and Validate Dynamic Row-Level and Object-Level SecurityModel security limits what report users see inside one semantic model. RLS filters rows. OLS hides tables or columns completely. Both must be implemented and tested.Scenario: Pro
  7. ✓3.7 — Optimize Queries, Visuals and DAX with Performance ToolsSlow reports are diagnosed from the visual down to the engine: which visual is slow, which DAX query it sends, where the engine spends its time, and what in the model causes it. Each tool covers one step.Scenario: Pro
  8. ✓3.8 — Implement Incremental RefreshIncremental refresh splits an Import table into date-based partitions. A refresh then reloads only the recent ones, so large models refresh faster, more reliably and with less load on the source.Scenario: Pro
Domain recapQuick overview of all lessons
  • Choose a storage mode (Import, DirectQuery, Dual, Direct Lake on OneLake or on SQL) and control Direct Lake fallback and framing
  • Build a star schema with the right relationships, including bridge tables, many-to-many and role-playing dimensions
  • Write DAX with variables, iterators, table filtering, window functions and information functions
  • Implement calculation groups, dynamic format strings and field parameters
  • Design large semantic models and composite models with aggregations
  • Implement and validate dynamic row-level security and object-level security
  • Optimize models, DAX and visuals with Performance analyzer, DAX Studio and Tabular Editor, and implement incremental refresh