Study guide
1.3 Microsoft Fabric Platform Fundamentals
Exam DP-600: Implementing Analytics Solutions Using Microsoft Fabric Exam
Track your progress as you read
Finished sections get a check mark.
1 DP-600 Exam Overview & Fabric Foundations
1.1 What DP-600 Certifies 1.2 Exam Logistics & Blueprint 1.3 Microsoft Fabric Platform Fundamentals
2 Maintain a Data Analytics Solution (25-30%)
2.1 Workspace & Item Security 2.2 Row/Column/Object/File-Level Security 2.3 Sensitivity Labels & Endorsement 2.4 Lifecycle: Git Integration & PBIP 2.5 Deployment Pipelines & XMLA
3 Prepare Data (45-50%)
3.1 Data Connections & Ingestion 3.2 Discover Data: OneLake Catalog & Real-Time Hub 3.3 Choose the Right Store: Lakehouse vs Warehouse vs Eventhouse 3.4 Transform & Model for Analytics 3.5 Data Quality Remediation 3.6 Querying: Visual Query, SQL, KQL, DAX
4 Implement & Manage Semantic Models (25-30%)
4.1 Storage Modes & Direct Lake 4.2 Semantic Star Schema & Relationships 4.3 DAX Foundations 4.4 Advanced Model Features 4.5 Optimization & Refresh
5 Exam Strategy & Final Preparation
5.1 A Hands-On Study Plan 5.2 High-Yield Traps & Confusions 5.3 Exam-Day & Retake Strategy
1.3 Microsoft Fabric Platform Fundamentals
Key Takeaways Explain This Topic AI
OneLake is the single, tenant-wide logical data lake storing tabular data in open Delta/Parquet format — one copy of data, no silos, addressed like OneDrive for data.
Workspaces are collaboration containers that hold Fabric items and are the unit of capacity assignment, security roles, and Git/deployment lifecycle.
Capacities are the purchased compute units (Fabric SKUs, e.g., F2, F64) that power all workloads in assigned workspaces.
Fabric is a SaaS platform: lakehouse, warehouse, eventhouse, semantic model, notebook, pipeline, and report are all first-class items in one product.
Shortcuts virtualize external or cross-workspace data into OneLake without copying it, enabling one logical lake across sources.
Last updated: June 2026
Fabric Is One SaaS Platform
Quick Answer: Microsoft Fabric is a software-as-a-service (SaaS) analytics platform. Every analytics artifact — lakehouse , warehouse , eventhouse , semantic model , notebook, data pipeline, and report — is a typed item that lives in a workspace , stores data in OneLake , and runs on a purchased capacity . There are no separate servers to provision.
Understanding this architecture is foundational because nearly every DP-600 question assumes you know where data physically lives and which item a task belongs in. "Choose between different data stores" is an explicit skill in the Prepare data domain.
OneLake: One Copy of Data
OneLake is the single, tenant-wide logical data lake automatically provisioned with Fabric. Exam-critical properties:
One per tenant. Like OneDrive for files, every organization gets exactly one OneLake. It removes data silos and means storage location is logical, not a separate account you create.
Open format. Tabular data is stored in Delta/Parquet , so it is readable by Spark, T-SQL, KQL, and Direct Lake semantic models without conversion or copying .
Hierarchical addressing. Data is addressed by tenant > workspace > item > folder/table , similar to a file path.
Shortcuts. A shortcut is a virtual reference that surfaces external storage (Amazon S3, Azure Data Lake Storage Gen2, Google Cloud Storage, or another Fabric workspace) inside OneLake without copying the data. This keeps a single logical lake across many physical sources and is the correct answer whenever a scenario says "make data available without duplicating it."
Workspaces: The Collaboration and Governance Unit
A workspace is the container that holds Fabric items and is the boundary for collaboration, security, capacity, and lifecycle:
Items (lakehouse, warehouse, semantic model, report, etc.) are created inside a workspace.
Workspace roles grant baseline access to its contents, layered from most to least privileged.
A workspace is assigned to exactly one capacity , which supplies its compute.
Git integration and deployment pipelines operate at the workspace level — making the workspace the natural dev/test/prod boundary tested under "Maintain the analytics development lifecycle."
- Workspace Role Can Do (roughly)
- Admin Everything, including managing access and deleting the workspace
- Member Add others (up to Member), publish/update content, share items
- Contributor Create and edit content; cannot manage workspace access
- Viewer Read and interact with content only; no editing
- Capacities: The Compute Engine
A capacity is the pool of purchased compute that powers all workloads in its assigned workspaces. Capacities are sold as Fabric SKUs (for example F2 through large F-series such as F64 , where the number is the count of capacity units). All Fabric engines — Spark, SQL warehouse, KQL, semantic-model query — draw from the same shared capacity, so a heavy Spark job can throttle report queries on the same SKU. F64 and above unlocks free Power BI content consumption for report viewers (no per-user Pro license), a common cost-decision question. Capacity sizing therefore affects every workload, not just one engine.
Item Types You Must Recognize
- Item Purpose Primary Query Language
- Lakehouse Open Delta/Parquet file + table analytics, Spark-friendly, read-only SQL endpoint SQL (read), Spark
- Warehouse Relational T-SQL data warehousing, full read/write SQL with transactions T-SQL
- Eventhouse / KQL DB Real-time and time-series telemetry analytics KQL
- Semantic model BI consumption layer for Power BI reports DAX
- Data pipeline / Dataflow Gen2 Ingestion and orchestration of data movement Low-code / config
- Notebook Code-first Spark transformations PySpark / Spark SQL
The single most-tested distinction is lakehouse vs. warehouse : the lakehouse SQL analytics endpoint is read-only (writes happen via Spark/notebooks or dataflows), while the warehouse supports full read/write T-SQL with multi-table transactions. Pick the lakehouse for data-engineering and unstructured/Spark workloads, and the warehouse when analysts need to run INSERT/UPDATE/DELETE in pure T-SQL.
Choosing a Data Store: A Decision Guide
Because "choose between different data stores" is an explicit exam objective, internalize this quick decision flow rather than memorizing isolated facts:
Files, semi-structured data, or Spark/notebook transforms? Use a lakehouse . It stores raw and curated Delta tables and exposes a read-only SQL endpoint for analysts.
Analysts who write T-SQL and need transactional INSERT/UPDATE/DELETE? Use a warehouse . It is the only Fabric SQL store with full write support and multi-statement transactions.
High-velocity event, log, or IoT telemetry needing sub-second time-series queries? Use an eventhouse / KQL database and query with KQL.
A governed layer for Power BI report consumption? Build a semantic model and query with DAX, ideally in Direct Lake mode over OneLake tables.
Every one of these stores writes to OneLake in open Delta/Parquet, so the same physical data can be reached by multiple engines without copying — a recurring theme in scenario questions.
Why Architecture Knowledge Earns Marks
A large share of DP-600 questions are phrased as "a team needs X without doing Y — which item or capability?" The right answer almost always hinges on three platform truths covered above: (1) data lives once in OneLake and is virtualized elsewhere via shortcuts ; (2) the workspace is the unit of security, capacity, and dev/test/prod lifecycle; and (3) the capacity SKU is shared by every engine, so sizing is a cross-workload and a cost decision.
When a scenario mentions duplicating data, think shortcut; when it mentions promoting or securing content, think workspace; when it mentions performance or licensing trade-offs, think capacity. Anchoring each question to one of these three concepts turns vague scenarios into fast, defensible answers and prevents the classic mistake of reaching for a deployment pipeline or a semantic model when a simpler, in-place capability is the intended solution.