Memory hook: Capacity runs the work; workspace organizes it; OneLake stores it.
Must remember
Microsoft Fabric combines analytics experiences around OneLake and shared platform capabilities. A workspace contains items; capacity supplies supported execution resources. A domain organizes business ownership/governance across workspaces rather than acting as an automatic security boundary. Workspace assignment and settings influence where and how jobs run.
A Lakehouse combines files and managed table patterns, commonly Delta, with Spark and supported SQL access. A Warehouse targets relational T-SQL analytical development. Eventhouse/KQL databases target event/time-series analytical workloads. Choose from access pattern, transformation language, transaction needs, latency and operating model, not product name alone.
Configure Spark pools/session behavior, environments/libraries and workspace defaults consistently. OneLake settings affect supported access and integration. Apache Airflow workspace configuration enables its supported orchestration integration; credentials, dependencies and runtime settings still need control. Separate development and production assumptions.
Git integration versions supported item definitions; deployment pipelines promote supported content across stages. They are not automatically a complete backup of every underlying data file or secret. Use database projects for declarative SQL schema development where supported, review differences and manage environment-specific connections/parameters. A successful deployment does not prove target data or permissions are correct.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Spark-oriented Delta engineering | Lakehouse. |
| SQL-first relational analytics | Warehouse. |
| High-volume event exploration with KQL | Eventhouse. |
Traps
- A workspace is not the same as capacity.
- Git integration does not automatically version every byte of data.
Active recall
1. What is OneLake?
Fabric’s unified logical data lake supporting its analytics experiences.
2. What does a domain organize?
Business ownership/governance grouping across workspaces.
3. Why separate environment connections?
A promoted definition must not accidentally keep writing to development or production sources.
4. What does a database project represent?
A versioned declarative database schema development artifact.
5. What should follow deployment?
Validate permissions, connections, data and representative workloads in the target stage.