Black Friday50% off your first month on any monthly plan with EARLY50 See plans
All 33 lessons
  1. Start here: cloud and data basics

    1. 1. Start here: the exam, the plan and what you already know
    2. 2. Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits
    3. 3. Data basics: files, tables, formats and the lakehouse idea
    4. 4. A tour of Microsoft Fabric: OneLake, workspaces and items
    5. 5. The three languages: SQL, PySpark and KQL side by side
    6. 6. Getting data in: the map of Fabric tools
  2. Store, ingest and transform batch data (exam area 2, 30-35%)

    1. 7. Choosing a data store and a transformation tool
    2. 8. Shortcuts and mirroring: use data without copying it
    3. 9. Ingest data with pipelines and Copy job
    4. 10. Transform with PySpark and SQL: join, denormalize, aggregate
    5. 11. Messy data: duplicates, missing values and late arrivals
    6. 12. Full and incremental loads, and loading a star schema
  3. Orchestrate and stream (exam areas 1 and 2)

    1. 13. Pipeline or notebook? Choosing how to orchestrate
    2. 14. Schedules and event-based triggers
    3. 15. Parameters and dynamic expressions
    4. 16. Streaming in Fabric: Eventstreams, Spark streaming and KQL
    5. 17. KQL and windowing functions for real-time data
  4. Set up and secure a Fabric solution (exam area 1, 30-35%)

    1. 18. Workspace settings: Spark, domains, OneLake and data workflows
    2. 19. Version control with Git and database projects
    3. 20. Deployment pipelines: development, test and production
    4. 21. Who can see what: workspace roles and item permissions
    5. 22. Fine-grained security: rows, columns, objects, files and masking
    6. 23. Governance: sensitivity labels and endorsement
  5. Monitor, fix and optimize (exam area 3, 30-35%)

    1. 24. Monitoring hub, alerts and Activator
    2. 25. Fixing errors in pipelines, dataflows and notebooks
    3. 26. Fixing errors in Eventhouse, Eventstream and T-SQL
    4. 27. Optimize lakehouse tables: V-Order, OPTIMIZE, VACUUM and partitions
    5. 28. Optimize Spark, pipelines and warehouses
    6. 29. Optimize eventstreams, eventhouses and queries
  6. Exam practice and final review

    1. 30. Exam day: question types, timing and how to think
    2. 31. Mock exam 1
    3. 32. Mock exam 2
    4. 33. Final review: every decision on one page
See the leaderboard

14 min

Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits

Explain what the cloud is and why Fabric is a SaaS product, so later lessons make sense.

By the end of this lesson you can

  • Tell IaaS, PaaS and SaaS apart, with a Microsoft example of each
  • Explain why Fabric being SaaS means you never manage servers or clusters
  • Define tenant, capacity, F SKU and region, and how they fit together
  • Say what Microsoft Entra ID does when you sign in to Fabric

From earlier lessons · 1 of 3

Your DP-700 score report shows 700. Did you pass?

Pick one answer.

From earlier lessons · 2 of 3

How are DP-700's three skill areas weighted?

Pick one answer.

From earlier lessons · 3 of 3

During DP-700 you open Microsoft Learn to check a setting. What happens to the exam clock?

Pick one answer.

Northwind Rides' finance director stops by your desk. "IT says we need to order servers for this Fabric thing. How many, and who patches them?" You open the Fabric portal and look for a server to count. There isn't one.

[4]

Cloud computing: renting instead of owning

Exam depth: recognize it.

Cloud computing is the delivery of computing services over the internet. Those services include servers, storage, databases and networking.

The old way was to own the computers. You bought servers months ahead, sized for your busiest day, and kept them running all year. In the cloud you rent what you need when you need it. When a busy season starts, you add computing power. When it ends, you scale back and stop paying for it.

Microsoft's cloud is called Azure. Fabric runs on it.

[16]

IaaS, PaaS and SaaS: who runs what

Exam depth: recognize it.

Cloud services come in three models. They differ in how much the provider runs for you.

ModelWhat you manageMicrosoft example
IaaS, infrastructure as a serviceVirtual machines, their operating systems and your apps.Azure Virtual Machines.
PaaS, platform as a serviceYour app and its settings. No machines or operating systems.Azure SQL Database.
SaaS, software as a serviceOnly your data, users and settings. You use a finished app.Microsoft 365.

A virtual machine is a computer simulated in software, rented by the hour. An operating system is the base software it runs, such as Windows or Linux.

In every model, three things stay yours: your data, your users and your settings.

Decision rule: the more you want to control, the further toward IaaS you go. The less you want to run, the further toward SaaS.

[17][18]

Match

Match each Microsoft service to its cloud model

Pick an item on the left, then its match on the right.

[17]

Fabric is SaaS: no servers, no clusters

Exam depth: know it cold.

Fabric is delivered as SaaS, built on Azure. You sign in through a web browser and create things. Microsoft runs the machines underneath.

That changes your job as a data engineer:

  • You never install, patch or size a server.
  • You never build a cluster, a group of machines that share one big job. Fabric provides the engines, such as Spark, an engine that splits big jobs across many machines, and runs the machines under them.
  • Many security and compliance features are built in, with little or no setup.

Older data products were mostly PaaS. Each service needed its own setup for security and compliance. In Fabric, the services share one platform and one copy of your data.

What's still yours: your data, who can see it, and the settings of what you build.

[9][19]

[9]

You are a data engineer at Northwind Rides. The IT team is two people and can't take on server maintenance. The company needs a platform to store and analyze trip data. You need the option with the least infrastructure to manage. What should you choose?

Pick one answer.

[9][17]

Tenant, capacity and F SKUs: what you pay for

Exam depth: know it cold.

A tenant is your organization's single instance of Fabric. It's tied to your organization's sign-in directory, which Microsoft creates when you first get any Microsoft online service.

A capacity is a pool of compute inside the tenant. Compute is the processing power that runs queries and jobs. A tenant can have as many capacities as it needs.

You buy a capacity as an F SKU. A SKU is a product size. F SKUs run from F2 up to F8192. The number is its capacity units (CUs), Fabric's measure of compute: F64 has 64 CUs.

F capacities are bought through Azure and billed per second, with a one-minute minimum and no commitment. You can reserve one for a year to pay less.

A workspace is where a team builds its items. Each workspace runs on one capacity.

To try Fabric, a Fabric Trial gives 64 CUs for 60 days.

[10][21]

Rendering diagram…
One tenant, several capacities. Each workspace runs on exactly one capacity.

[10]

[10]

You are a data engineer at Northwind Rides. 300 station staff will view a Power BI report of fleet status. They have only Free Fabric licenses, and finance won't buy them Pro licenses. You need to choose the smallest capacity that lets them view it. What should you choose?

Pick one answer.

[10]

Regions and data residency

Exam depth: recognize it.

A region is a group of Microsoft datacenters in one area, such as East US or West Europe.

Your tenant has a home region. It's set when the tenant is created, from where the first user signed up. It's the default place your data is stored.

Data residency means rules about where data may be stored. For example: EU customers' data must stay in the EU.

To meet a rule like that, create a capacity in the region you need. Then assign the workspace to it. That workspace's data is stored and processed in the capacity's region. Some tenant-wide information stays in the home region, such as metadata: the names and settings of your items.

[14][15][24][25]

The About Microsoft Fabric window, opened from the Help pane. It lists service version and tenant URL, and a highlighted line reads "Your data is stored in" followed by the region.
Microsoft Learn, CC BY 4.0

[14]

You are a data engineer at Northwind Rides, whose Fabric home region is in the US. A new Paris office must keep its riders' trip data stored in the EU. You need to meet this rule with the least change to the rest of the setup. What should you do?

Pick one answer.

[15][24][25]

Microsoft Entra ID: who you are

Exam depth: recognize it.

Microsoft Entra ID is Microsoft's cloud service for identity and access. It checks who you are when you sign in. Its old name was Azure Active Directory.

Every sign-in to Fabric goes through Entra ID, and your Fabric tenant is tied to your organization's Entra tenant. Users and groups live in Entra ID. Fabric then decides what each of them may do, through roles and permissions you'll meet in lesson 21.

[20][21][26][27]

You asked for a capacity. You got compute. Nobody got a server. Picture: Three-panel comic strip, bright flat colors.

Exam-style practice

You are a data engineer at Northwind Rides. The development capacity, an F8, is used only on weekdays from 9 to 6. You need to cut its cost at nights and weekends without deleting any data. What should you do?

Pick one answer.

[22][23]

You are a data engineer at Northwind Rides. Heavy nightly jobs slow down the ops team's reports, which share the same capacity. You need to stop the jobs from affecting the reports. Users must keep one sign-in. What should you do?

Pick one answer.

[10][28]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 15

[9][10][14][16][17][21][22][26]

Worth keeping

  1. IaaS: you run the machines. PaaS: you run the app. SaaS: you just use it.
  2. Fabric is SaaS, so you never install, patch or size servers or clusters.
  3. One tenant holds many capacities; each workspace runs on one capacity.
  4. F64 and up lets Free-license viewers see Power BI content; PPU is not a capacity.
  5. A workspace's data lives in its capacity's region; Entra ID handles every sign-in.

You know where Northwind's data will live and what powers it. But that data comes as CSV files, JSON events and database tables. Next lesson: which format is fastest for analysis, and why Fabric stores every table as Delta.

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 (20)

Each fact in the lesson is marked with the number of the page it comes from.

  1. [4]Microsoft Learn: Study Guide for Exam DP-700
  2. [6]Microsoft Learn: Exam duration and exam experience
  3. [7]Microsoft Learn: Exam scoring and score reports
  4. [9]Microsoft Learn: What is Microsoft Fabric?
  5. [10]Microsoft Learn: Understand Microsoft Fabric licenses and capacity
  6. [14]Microsoft Learn: Find your Fabric home region
  7. [15]Microsoft Learn: Configure Multi-Geo support for Fabric
  8. [16]Microsoft Learn: What is cloud computing
  9. [17]Microsoft Learn: Shared responsibility in the cloud
  10. [18]Microsoft Learn: Describe Software as a Service
  11. [19]Microsoft Learn: Microsoft Fabric security fundamentals
  12. [20]Microsoft Learn: Security in Microsoft Fabric
  13. [21]Microsoft Learn: Fabric terminology
  14. [22]Microsoft Learn: Pause and resume your Fabric capacity
  15. [23]Microsoft Learn: Pause and resume in Fabric Data Warehouse
  16. [24]Microsoft Learn: Power BI implementation planning: Tenant setup
  17. [25]Microsoft Learn: Microsoft Fabric end-to-end security scenario
  18. [26]Microsoft Learn: What is Microsoft Entra?
  19. [27]Microsoft Learn: Microsoft Entra service description
  20. [28]Microsoft Learn: Evaluate and optimize your Microsoft Fabric capacity