All 33 lessons
Start here: cloud and data 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. The three languages: SQL, PySpark and KQL side by side
- 6. Getting data in: the map of Fabric tools
Store, ingest and transform batch data (exam area 2, 30-35%)
- 7. Choosing a data store and a transformation tool
- 8. Shortcuts and mirroring: use data without copying it
- 9. Ingest data with pipelines and Copy job
- 10. Transform with PySpark and SQL: join, denormalize, aggregate
- 11. Messy data: duplicates, missing values and late arrivals
- 12. Full and incremental loads, and loading a star schema
Orchestrate and stream (exam areas 1 and 2)
Set up and secure a Fabric solution (exam area 1, 30-35%)
- 18. Workspace settings: Spark, domains, OneLake and data workflows
- 19. Version control with Git and database projects
- 20. Deployment pipelines: development, test and production
- 21. Who can see what: workspace roles and item permissions
- 22. Fine-grained security: rows, columns, objects, files and masking
- 23. Governance: sensitivity labels and endorsement
Monitor, fix and optimize (exam area 3, 30-35%)
- 24. Monitoring hub, alerts and Activator
- 25. Fixing errors in pipelines, dataflows and notebooks
- 26. Fixing errors in Eventhouse, Eventstream and T-SQL
- 27. Optimize lakehouse tables: V-Order, OPTIMIZE, VACUUM and partitions
- 28. Optimize Spark, pipelines and warehouses
- 29. Optimize eventstreams, eventhouses and queries
Exam practice and final review
18 min
Shortcuts and mirroring: use data without copying it
Reach data in other places with shortcuts and keep a live copy of a database with mirroring.
By the end of this lesson you can
- Tell an internal shortcut from an external one and pick where it goes
- Explain how shortcut security passes your identity to the source
- Name the sources mirroring supports and what it costs
- Choose a shortcut, mirroring or a copy for a scenario
From earlier lessons · 1 of 2
Northwind's station analysts know Power Query but not code. They must reshape station data every week. Which tool fits them?
Pick one answer.
From earlier lessons · 2 of 2
You try to run an INSERT through a Lakehouse's SQL analytics endpoint. What happens?
Pick one answer.
Northwind Rides' maintenance partner keeps its station logs in its own Amazon S3 bucket. Finance wants live payment numbers from the SQL Server database, without slowing down checkout. Your manager asks: "Can we use both in Fabric without writing a single copy pipeline?" You can, with two features.
What a shortcut is
Exam depth: know it cold.
A shortcut is an object in OneLake that points to data stored somewhere else. No data is copied. The place it points to is the target path. The place it shows up is the shortcut path.
A shortcut looks like an ordinary folder. Every engine that reads OneLake can use it: Spark, the SQL analytics endpoint, KQL and Power BI in Direct Lake mode.
You create shortcuts in a Lakehouse or a KQL database. Deleting a shortcut removes only the pointer. The source data stays where it was. But if you rename or delete the target, the shortcut breaks.
Internal and external shortcuts
Exam depth: know it cold.
An internal shortcut points to another place inside OneLake. An external shortcut points to storage outside OneLake.
| Internal shortcut | External shortcut | |
|---|---|---|
| Points to | Lakehouse, Warehouse, KQL database, mirrored database, SQL database, semantic model. | ADLS Gen2, Azure Blob Storage, Amazon S3, S3 compatible, Google Cloud Storage, Dataverse, OneDrive and SharePoint. |
| How it signs in | Your own identity by default (passthrough). | A saved cloud connection, such as a key or service principal. |
The item types don't need to match. A Lakehouse shortcut can point to a Warehouse table.
Reading other clouds costs egress fees, the charge a cloud adds when data leaves it. Shortcut caching keeps read files in OneLake for 1 to 28 days. You turn it on in Workspace settings, on the OneLake tab. It works for S3, S3 compatible, Google Cloud Storage and gateway shortcuts. Files over 1 GB aren't cached.
You are a data engineer at Northwind Rides. A partner keeps station logs in its own Amazon S3 bucket. You need the logs in your Lakehouse without copying them, and you want to cut repeat cross-cloud read fees. What should you do?
Pick one answer.
Tables or Files: where the shortcut lives
Exam depth: know it cold.
A Lakehouse has two top folders, and shortcuts behave differently in each.
| In Tables | In Files | |
|---|---|---|
| Where you can create it | Top level only. No subfolders. | Any level. |
| What it can point to | Data in a table format, such as Delta. | Data in any format. |
| Becomes a table? | Yes, if the target is Delta. Its schema stays in sync. | No. Spark reads it by path. |
| SQL analytics endpoint sees it? | Yes. | No. |
Rule: point a Tables shortcut at Delta data you want to query with SQL. Point a Files shortcut at raw files you'll process with Spark.
Who sees the data: shortcut security
Exam depth: know it cold.
To create a shortcut, you need Write permission on the item where it goes and Read access to the target.
To use one, both places count. You get the most restrictive of the two. Write access in your Lakehouse doesn't let you write to a target where you can only read.
There are two ways a shortcut signs in:
- Passthrough: the shortcut passes your identity to the target. You see only what you could see there. This is the default for internal shortcuts.
- Delegated: the shortcut uses a fixed credential, such as a service principal (an app identity) or a key. External shortcuts always work this way.
One exception: Power BI in Direct Lake over SQL mode, or T-SQL in Delegated identity mode, uses the item owner's identity instead of yours.
You are a data engineer at Northwind Rides. Ana has Write access in the ops Lakehouse. A shortcut there points to the finance Lakehouse, where Ana has Read access only. Ana runs a notebook that writes to the shortcut. What happens?
Pick one answer.
Mirroring: a live copy of a database
Exam depth: know it cold.
Mirroring keeps an outside database available in Fabric. The usual kind, database mirroring, continuously copies it into OneLake as Delta tables. You pick the whole database or chosen tables, and Fabric keeps them in sync. You build no ETL pipeline. (ETL means extract, transform, load: the usual copy-and-reshape jobs.)
It runs in near real time. A replicator engine merges source changes into Delta tables, as often as every 15 seconds.
You get a mirrored database item plus a SQL analytics endpoint to query it. The mirrored tables are read-only. You read them with SQL, Spark or Power BI, but you don't edit them in Fabric.
Database mirroring sources include Azure SQL Database, Azure SQL Managed Instance, SQL Server, Azure Cosmos DB, Azure Database for PostgreSQL, Snowflake, Oracle, Google BigQuery and SAP.
Exam depth: recognize it.
Mirroring comes in three types.
- Database mirroring copies the data itself. Most sources work this way.
- Metadata mirroring copies only the catalog: names of schemas and tables. The data stays put and is read through shortcuts. Azure Databricks works this way.
- Open mirroring is for sources Fabric has no connector for. Your own app, or a partner tool, writes change files into a landing zone, a folder in OneLake. Fabric merges the inserts, updates and deletes into Delta tables.
What mirroring costs
Exam depth: know it cold.
A capacity unit (CU) measures the size of your Fabric capacity. An F64 has 64 CUs. These rules apply to database and open mirroring.
- Replication compute is free. Copying changes into OneLake doesn't use your capacity.
- Storage is free up to a limit. You get 1 TB of mirroring storage per CU, so an F64 gets 64 TB.
- Querying is not free. SQL, Spark and Power BI reads use capacity at normal rates.
- The capacity must be running. If it's paused, nothing replicates and you pay for OneLake storage.
You are a data engineer at Northwind Rides on an F64 capacity. Finance mirrors a 2 TB payments database. To save money, an admin pauses the capacity every weekend. What happens to mirroring at the weekend?
Pick one answer.
Shortcut, mirroring or copy?
Exam depth: know it cold.
| Shortcut | Mirroring | Copy (pipeline or Copy job) | |
|---|---|---|---|
| Data moves? | No. It stays at the source. | Database mirroring: yes, into OneLake. Metadata mirroring: no. | Yes, into OneLake. |
| Best source | Files or Delta tables in storage. | An operational database. | Almost any source. |
| Freshness | Always current. | Near real time. | As of the last run. |
| Transform on the way? | No. | No. | Yes, some. |
| Your control | None needed. | Fixed behavior. | Your own schedule and settings. |
| Cost | No copy to store. | Free replication. | Not free. |
Decision rule: data already in a lake or Fabric item, use a shortcut. A database you need near real time with no ETL, use mirroring. Need a schedule, transforms or a writable target, copy it.
Try it in Fabric
A free Fabric trial is enough. You'll make an internal shortcut to a table in another Lakehouse.
- Open rides_lakehouse from lesson 4. If you skipped that, select New item, then Lakehouse, name it rides_lakehouse and select Create.
- Download the sample file at fabrictutorialdata.blob.core.windows.net/sampledata/Coffee/Dim_Products.csv.
- In the Lakehouse, select Get data > Upload files, pick the file and select Upload.
- Open Files. On the file's ... menu, select Load to Tables > New table. Name it dim_products and select Load.
- Create a second Lakehouse named ops_lakehouse.
- In it, open the ... menu on Tables and select New shortcut.
- Under Internal sources, select Microsoft OneLake. Pick rides_lakehouse and select Next.
- Expand Tables, select dim_products, select Next, then Create.
The table appears in ops_lakehouse with a small link icon. You can query it, yet no data was copied.
Exam-style practice
You are a data engineer at Northwind Rides. Finance needs payment data from an Azure SQL Database in Fabric within seconds of each change. Reports only read it. The team has no budget for extra compute and doesn't want to build ETL. What should you use?
Pick one answer.
You are a data engineer at Northwind Rides. The ops team's Lakehouse needs the customer Delta table that lives in the finance workspace's Lakehouse. Ops must query it with the SQL analytics endpoint. Data must not be duplicated. What should you create?
Pick one answer.
Worth keeping
- A shortcut points to data without copying it; internal stays in OneLake, external reaches other storage.
- Shortcuts in Tables to Delta become SQL-queryable tables; Files shortcuts take any format.
- Shortcut access is the stricter of the two locations' permissions.
- Mirroring keeps a read-only, near real-time Delta copy of a database, with free replication.
- Lake data: shortcut. Live database: mirroring. Schedule or transforms: copy.
On the job
Here's how Northwind Rides might wire this up.
The partner's S3 bucket gets an external shortcut in the Files folder of the raw Lakehouse. Caching is on, so the morning notebook rereads files from OneLake, not from AWS.
The SQL Server payments database is mirrored. Finance queries the mirrored database's SQL analytics endpoint during the day, and the checkout app never slows down.
The ops team works in its own workspace. Instead of copying the clean trip tables, it uses internal shortcuts in its Tables folder. When the engineering team fixes a bug in a table, ops sees the fix at once.
Shortcuts and mirroring cover data that already lives somewhere tidy. But the partner also emails CSV files that must land in a table every night, on a schedule. Next lesson you build that copy yourself.
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 (9)
Each fact in the lesson is marked with the number of the page it comes from.
- [4]Microsoft Learn: Study Guide for Exam DP-700
- [42]Microsoft Learn: What is Mirroring in Fabric?
- [69]Microsoft Learn: Microsoft Fabric decision guide: Choose a data movement strategy
- [72]Microsoft Learn: Unify data with OneLake shortcuts and mirroring
- [74]Microsoft Learn: OneLake shortcuts
- [75]Microsoft Learn: OneLake shortcut security
- [76]Microsoft Learn: Create a same-tenant OneLake shortcut
- [77]Microsoft Learn: Open mirroring in Microsoft Fabric
- [78]Microsoft Learn: Quickstart: Get data into OneLake