Examworthyexamworthy.comMicrosoft Fabric Analytics Engineer Associate (DP-600) cheat sheet
Microsoft
Free to share. Examworthy is not affiliated with or endorsed by Microsoft; DP-600 and related marks belong to their respective owners.
At a glance
Format: Multiple choice and multiple response, at a Pearson VUE testing center or online proctored
Domain weight map
Heaviest first - spend your time hereHow this exam thinks
DP-600 is the analytics engineer's full workflow on Microsoft Fabric tested as scenario judgement: secure and version the solution, prepare data into a star schema in the right store, and model it with the correct storage mode, and the right answer is the option that meets the stated requirement with the least operational overhead and the correct governance scope.
Spot the trap
Tempting wrong answers, and why they failCommon misconception
That a personal-mode gateway can be shared so a whole team reuses one connection to a local server. Personal mode is single-user only.
Prepare Data
Common misconception
That Contributor can reshare items they personally created. Resharing needs Member or Admin regardless of who authored the item.
Maintain a Data Analytics Solution
Common misconception
That many-to-many cardinality directly resolves a genuine many-to-many between dimensions. It weakens filtering; a bridge table of key pairs is the supported fix.
Implement and Manage Semantic Models
Common misconception
That a firewall service-tag exception lets a cloud connection reach a database with public access disabled. There is no public endpoint for it to route to.
Prepare Data
Common misconception
That hiding columns in the semantic model secures them. It only hides them in reports; anyone querying the Warehouse directly still sees the raw values.
Maintain a Data Analytics Solution
Common misconception
That bidirectional filtering on every bridge relationship is a safe default fix. It also lets transaction selections filter the customer list, the reverse the rule forbids.
Implement and Manage Semantic Models
Common misconception
That storing a storage key in a workspace parameter and referencing it in queries is good credential governance. A parameter is not a secure secret store.
Prepare Data
Common misconception
That recreating a SQL row-level security predicate protects a Direct Lake model too. Direct Lake reads Parquet directly and bypasses the SQL endpoint entirely.
Maintain a Data Analytics Solution
Key terms
Exam-day rules
- Read the scenario for the stated requirement first, then match it to the Fabric option that meets it with the least operational overhead and the correct scope. Distractors are written to sound reasonable; the right answer is the precise documented behaviour, not a hand-rolled or more powerful alternative.
- On any store-choice question, separate the surfaces: a Lakehouse for files, Delta, and Spark, a Warehouse for a fully transactional T-SQL store, an Eventhouse and KQL database for real-time events. Need T-SQL writes and procedural objects means Warehouse, not the read-only SQL analytics endpoint of a Lakehouse.
- For storage mode, decide by freshness and copy: Direct Lake reads OneLake Delta in memory with live freshness and no scheduled refresh, import caches and needs a refresh, DirectQuery queries live but loses in-memory speed. An oversized import model needs the large semantic model storage format, not a storage-mode change.
- On version control and promotion, separate the two mechanisms: Git integration gives branch-based source control with pull-request review and is reconciled with Commit to push and Update to pull merged changes, while deployment pipelines promote content across development, test, and production with deployment rules.
- On any role or security question, pick the least-privileged role and the correct security tier. Contributor, not Member or Admin, is the lowest role that authors all items; a composite model chained by DirectQuery already honours the source model's row-level security, so do not recreate roles.
Revision schedule
- Day 1Map the blueprint and book a date
- Week 1Learn the Fabric store and ingestion decisions
- Weeks 2 to 3Go deep on preparation and querying
- Week 4Master semantic models and storage modes
- Week 5Master maintenance, security, and the lifecycle