All 35 lessons
Start here: cloud, data, Fabric and Power BI basics
- 1. Start here: the exam, the plan and what you already know
- 2. Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits
- 3. Data basics: files, tables, formats and the lakehouse idea
- 4. A tour of Microsoft Fabric: OneLake, workspaces and items
- 5. Power BI in plain words: semantic models, reports and DAX
Prepare data: get data in (exam area 2, 45-50%)
- 6. Connect to data and find it: connections, gateways, OneLake catalog and Real-Time hub
- 7. Choosing a data store: lakehouse, warehouse or eventhouse
- 8. Use data without copying: shortcuts, mirroring and OneLake integration
- 9. Ingest data: Dataflow Gen2, pipelines, Copy job and notebooks
- 10. Power Query in Dataflow Gen2: filter, data types, merge and new columns
- 11. Messy data: duplicates, missing values and nulls
Prepare data: transform and query (exam area 2)
Design and build semantic models (exam area 3, 25-30%)
- 18. Choose a storage mode: Import, DirectQuery, Direct Lake and Dual
- 19. Relationships: star schemas, bridge tables and many-to-many
- 20. DAX foundations: measures, filter context, CALCULATE and variables
- 21. DAX functions the exam tests: iterators, table filters, windows and information functions
- 22. Calculation groups, dynamic format strings and field parameters
- 23. Composite models and large semantic model storage format
Optimize models, then secure them (exam areas 3 and 1)
- 24. Direct Lake in depth: fallback, refresh and the two flavors
- 25. Incremental refresh for semantic models
- 26. Faster reports and DAX: finding and fixing slow queries
- 27. Who can see what: workspace roles and item permissions
- 28. Fine-grained security: rows, columns, objects and files
- 29. Governance: sensitivity labels and endorsement
Lifecycle, then exam practice (exam area 1)
18 min
Data basics: files, tables, formats and the lakehouse idea
Tell files from tables, pick the right format, and see why Fabric stores tables as Delta.
By the end of this lesson you can
- Choose between CSV, JSON, Parquet and Delta for a given need
- Explain what Delta Lake adds to Parquet: ACID and time travel
- Tell a data warehouse, a data lake and a lakehouse apart, and OLTP from OLAP
- Name the fact and dimension tables of a star schema and state its grain
From earlier lessons · 1 of 3
Which cloud model is Microsoft Fabric?
Pick one answer.
From earlier lessons · 2 of 3
On an F64 capacity, what do store managers who only view reports need?
Pick one answer.
From earlier lessons · 3 of 3
Where is a workspace's data stored?
Pick one answer.
Juniper Coffee's first data has arrived. Suppliers email CSV price lists. The loyalty app sends JSON events all day. Till sales sit in database tables. Your manager asks: "Can't we just keep it all in CSV? Everyone can open those."
Structured, semi-structured and unstructured data
Exam depth: recognize it.
- Structured data follows a fixed schema, a set list of columns and their types. Every row has the same fields. Juniper's till sales table is structured.
- Semi-structured data has some structure, but fields can vary from record to record. A loyalty-app event in JSON (JavaScript Object Notation) may carry an offer field that another event lacks.
- Unstructured data has no set structure: photos of café displays, PDF supplier contracts, audio.
Fabric stores all three. Tables hold structured data. Files hold the rest until you shape them into tables.
File formats: CSV, JSON, Parquet and Delta
Exam depth: know it cold.
| Format | How it stores data | Good for |
|---|---|---|
| CSV | Plain text, one row per line, commas between fields. | Swapping simple tables between any tools, like supplier price lists. |
| JSON | Plain text with nested fields that can vary. | Events and app data, such as loyalty-app messages. |
| Parquet | Compressed binary, columnar: each column's values sit together. | Fast analytics on large data. |
| Delta | Parquet files plus a transaction log of every change. | Reliable tables you update. Fabric's default. |
CSV and JSON are easy for people to read but slow to scan at scale. Parquet is built for machines.
Decision rule: receive data in whatever format it comes in, then store it for analysis as Delta tables.
Predict, then reveal
Juniper's sales table has 60 columns and 500 million rows. Finance asks for total sales by region. Predict why this runs much faster on Parquet than on CSV.
Delta Lake: Parquet plus a transaction log
Exam depth: know it cold.
Delta Lake is an open table format. A Delta table is a folder of Parquet files plus a transaction log, a record of every change made to the table.
The log gives you two things plain Parquet can't.
ACID transactions. Each change is all-or-nothing and leaves the data valid:
- Atomic: a change succeeds completely or not at all.
- Consistent: data moves from one valid state to another.
- Isolated: two jobs writing at once don't see each other's half-done work.
- Durable: once saved, a change stays saved.
Time travel. Every saved change creates a new table version. You can query the table as it was at an earlier version or time.
When you load data into Fabric, it's stored as Delta tables by default. Every Fabric engine reads them, including Power BI's Direct Lake mode.
-- See which versions existDESCRIBE HISTORY sales;-- Read the table as it was at version 5SELECT * FROM sales VERSION AS OF 5;-- Read the table as it was on a dateSELECT * FROM sales TIMESTAMP AS OF '2026-11-01';
You are an analytics engineer at Juniper Coffee. A faulty load ran this morning and overwrote the Delta table of supplier prices with wrong values. Before anyone fixes it, you need to see exactly what the table held yesterday. You must not change the table yet. What should you use?
Pick one answer.
Data warehouse, data lake, lakehouse
Exam depth: know it cold.
| Store | What it is | Strength |
|---|---|---|
| Data warehouse | Tables in a relational schema, queried with SQL. | Fast, trusted reporting on structured data. |
| Data lake | Cheap storage for huge numbers of files in any format. | Holds everything, including raw and unstructured data. |
| Lakehouse | A data lake with tables on top of its files. | Lake storage with warehouse-style queries. |
A relational schema is a set of tables linked by key columns.
Fabric has an item for each idea. A Lakehouse holds files and Delta tables. A Warehouse gives full T-SQL, Microsoft's version of SQL, including writes. You'll meet both properly in lesson 4, and choose between them in lesson 7.
OLTP vs OLAP, batch vs streaming
Exam depth: recognize it.
| OLTP | OLAP | |
|---|---|---|
| Stands for | Online transaction processing. | Online analytical processing. |
| Work | Many small reads and writes as things happen. | Big reads that summarize history. |
| Example | Recording each coffee sold at the till. | Sales by region by month. |
Juniper's till database is OLTP: it runs the cafés. Your Fabric solution is the OLAP side. You copy data out and reshape it, so reports don't slow the tills down.
Batch processing collects records and processes them together, such as every night. Stream processing handles each record as it arrives, with latency (the delay before a result is ready) in seconds.
Decision rule: near real-time or as it happens means streaming. If a nightly or hourly result is fine, batch is simpler.
Match
Match each Juniper Coffee workload to the kind of processing it is
Pick an item on the left, then its match on the right.
A first look at the star schema
Exam depth: recognize it. Lesson 13 builds one in a lakehouse or warehouse, and lesson 19 in a semantic model.
A star schema is the standard table design for analysis, and the shape Power BI semantic models work best with. It has two kinds of table:
- A fact table stores measurements of events: each item sold, with its quantity and amount. Those number columns are measures.
- Dimension tables describe the things involved: cafés, products, dates. Their text columns are what you filter and group by.
The fact table sits in the middle and the dimensions around it, like the points of a star.
The grain is what one fact row means. For Juniper: one row per product per receipt. Decide the grain first.
Each dimension row gets a surrogate key, a single-column ID the warehouse generates. The source system's own ID is the natural key.
Exam-style practice
You are an analytics engineer at Juniper Coffee. Sales data must be fast to query from SQL and Power BI. Nightly loads update rows in it, and two loads sometimes write at once. Reports must never read half-written data. You need to choose the storage format. What should you use?
Pick one answer.
You are an analytics engineer at Juniper Coffee. Finance wants to analyze which products sell together on the same receipt. You are designing the sales fact table. You need to choose its grain. What should you choose?
Pick one answer.
You are an analytics engineer at Juniper Coffee. Marketing wants a screen showing loyalty-app offer redemptions in each region, updated within seconds. You need to choose how to process the app events. What should you use?
Pick one answer.
Worth keeping
- CSV and JSON are for moving data; Parquet is columnar and fast for analytics.
- Delta = Parquet + a transaction log, giving ACID and time travel. It's Fabric's default.
- A lakehouse is a lake with tables on top; a warehouse is relational tables with SQL.
- OLTP runs the tills; OLAP answers questions. Streaming means seconds; batch means hours.
- A star schema has a fact table at a stated grain, ringed by dimension tables.
Files, Delta tables, a lake, a warehouse, streaming events: that sounds like five separate systems to run. In Fabric it's one. Next lesson you open OneLake, the single lake every Fabric item writes to, and see where the semantic model sits.
Leaderboard
Loading…
50 XP for each lesson you finish, 10 for each right answer. Names show only for learners who turn on Show me on leaderboards.
Sources for this lesson (16)
Each fact in the lesson is marked with the number of the page it comes from.
- [2]Microsoft Learn: Fabric terminology
- [6]Microsoft Learn: Study guide for Exam DP-600: Implementing Analytics Solutions Using Microsoft Fabric
- [9]Microsoft Learn: Understand Microsoft Fabric licenses and capacity
- [10]Microsoft Learn: Explore file storage
- [11]Microsoft Learn: Dimensional modeling in Fabric Data Warehouse
- [14]Microsoft Learn: Shared responsibility in the cloud
- [19]Microsoft Learn: Configure Multi-Geo support for Fabric
- [27]Microsoft Learn: Identify data formats
- [28]Microsoft Learn: Delta Lake overview
- [29]Microsoft Learn: Explore transactional data processing
- [30]Microsoft Learn: Query Delta tables with time travel
- [31]Microsoft Learn: Explore analytical data processing
- [32]Microsoft Learn: Understand batch and stream processing
- [33]Microsoft Learn: Understand star schema and the importance for Power BI
- [34]Microsoft Learn: Dimensional modeling in Microsoft Fabric Warehouse: Dimension tables
- [35]Microsoft Learn: Dimensional modeling in Microsoft Fabric Warehouse: Fact tables