Fabric DP-600 cheat sheet for key facts, traps, service mappings, and final review.
Use this cheat sheet for Microsoft Certified: Fabric Analytics Engineer Associate (DP-600) after you know the basics but before you start a timed practice block. The goal is not to memorize a vendor catalog; the goal is to classify the scenario and reject attractive wrong answers quickly.
Use this when the stem mixes model grain, relationships, refresh, sharing, or optimization.
flowchart TD
S["Scenario"] --> M["Check model grain and measures"]
M --> R["Check relationships and refresh"]
R --> G["Check governance and sharing boundaries"]
G --> O["Check optimization and performance"]
| Lane | Decision rule | Reject when |
|---|---|---|
| Semantic models | Design relationships, measures, calculation logic, refresh, and security for analytical consumption. | Confusing a report visual problem with a model design problem. |
| Power BI reporting | Build visuals, interactions, filters, accessibility, and performance-aware report layouts. | Adding visuals without deciding the business question or audience action. |
| Data preparation | Use Power Query, dataflows, lakehouse or warehouse sources, and shaping steps appropriately. | Solving repeatable transformation logic only inside one report when it belongs upstream. |
| Governance and deployment | Manage workspaces, endorsement, sensitivity, lineage, deployment pipelines, and sharing controls. | Sharing broadly without certification, data protection, or role separation. |
| Optimization | Tune DAX, model size, relationships, aggregation, refresh, and query behavior. | Blaming capacity before checking model design and expensive calculations. |
| Trap | Better instinct |
|---|---|
| Report-first thinking | Start with model grain, relationships, measures, and security before the visual layer. |
| Uncontrolled sharing | Use workspace roles, item permissions, sensitivity labels, and endorsement deliberately. |
| Bad DAX context | Reason through filter context, row context, relationships, and measure evaluation. |
| Refresh blind spots | Confirm data source, gateway, credentials, schedule, dependencies, and incremental refresh logic. |
| If the stem says | Start with |
|---|---|
| least privilege, private access, compliance, or audit | identity scope, data boundary, policy enforcement, logging, and ownership |
| least operational effort | managed service, native integration, simple workflow, and fewer moving parts |
| high availability, recovery, or outage | failure domain, recovery objective, health check, rollback, and validation |
| performance, scale, or cost | bottleneck evidence, traffic pattern, sizing, caching, batching, and quotas |
| troubleshoot, diagnose, or investigate | symptom, recent change, logs, metrics, status, dependency, and smallest safe test |
Use IT Mastery for the exact product route, practice status, spaced review when available, and close-answer explanation practice as coverage expands.
Open the exact IT Mastery route here: DP-600 on MasteryExamPrep.
Analytics questions usually hinge on model grain, calculation context, refresh reliability, sharing boundary, and user action.