2.2 — Ingest, Copy and Schedule Data
DP-600 Domain 2 · Skill 2.2
What You Need to Know
Fabric has five ways to bring data in. The exam asks you to pick the right one from the source, volume, transformation needs and team skills, and then to schedule and orchestrate it.
Pick an ingestion method
| Method | Code | Best for |
|---|---|---|
| Pipeline Copy activity | No code | Large, fast copies from 50+ connectors into a lakehouse, warehouse or files; light mapping and format conversion; orchestrated with other steps |
| Copy job | No code | Simple copies of one or many tables with built-in incremental (watermark or CDC) and merge, without building a pipeline |
| Dataflow Gen2 | Low code (Power Query) | Ingest and transform with 300+ transformations; analysts' skill set; writes to lakehouse, warehouse, SQL database and other destinations |
| Notebook | PySpark / Spark SQL | Complex logic, APIs, very large volumes, data science |
| Shortcut | None | Use data in place (ADLS, S3, GCS, Dataverse, other Fabric items). Nothing is copied |
Copying between Fabric items
| Scenario | Good choice |
|---|---|
| Lakehouse table → warehouse table in the same workspace | T-SQL INSERT ... SELECT or CTAS with three-part names (the lakehouse is read through its SQL endpoint) |
| Warehouse → lakehouse | A pipeline Copy activity, or a shortcut to the warehouse table if a copy isn't needed |
| Many tables, incremental, minimal setup | Copy job |
| Data needs reshaping on the way | Dataflow Gen2 or a notebook |
Shortcuts in practice
- Create them in a lakehouse: under Tables at the top level for Delta tables (recognized as tables automatically) or anywhere under Files.
- The target can be in another workspace (the reader needs permission on the target), or external storage reached through a connection.
- Deleting a shortcut doesn't delete the target data.
Orchestrate and schedule
- Pipelines combine activities: Copy, Dataflow, Notebook, Stored procedure, Script, Semantic model refresh, plus control flow (ForEach, If Condition) and dependency conditions (On success, On fail, On completion).
- Schedules: pipelines, dataflows, notebooks and semantic models each have their own scheduler (frequency, times and time zone, with multiple schedules per item). For a chain of dependent steps, schedule one pipeline rather than several items at guessed times.
- Event triggers: start a pipeline when a file lands (OneLake or Blob Storage events through Activator).
Key Concept: Power Query skills point to Dataflow Gen2. Python skills or heavy logic point to a notebook. Moving data with no code points to Copy (activity or job). Not copying at all means a shortcut. Then wire the steps into one scheduled pipeline.
Exam Traps
- Copying data that a shortcut could reference in place
- Scheduling a dataflow and a dependent stored procedure separately at fixed times instead of chaining them in a pipeline
- Using a dataflow to move a billion rows with no transformation
- Creating Tables shortcuts in a subfolder of Tables
Check your understanding
Practice Scenario
🔒 This practice scenario is part of Skillmarked Pro
The lessons stay free. Pro unlocks the other 17 DP-600 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.
Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.
Cancel anytime. Or €199 a year, which saves 17%.
Not sure yet? Try 10 free mock exam questions.
Already Pro? Log in.
Sources
- Fabric decision guide: copy activity, Copy job, dataflow, Eventstream, or Spark, Microsoft Learn
- What is Copy job in Data Factory, Microsoft Learn
- OneLake shortcuts, Microsoft Learn
- Ingest data into the Warehouse, Microsoft Learn
- Run, schedule, or use events to trigger a pipeline, Microsoft Learn