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
15 min
Schedules and event-based triggers
Run pipelines and notebooks on a schedule or when something happens.
By the end of this lesson you can
- Schedule a pipeline or notebook with the right repeat, time zone, start and end
- Set up an event-based trigger that starts a pipeline when a file lands in OneLake
- Explain what Activator does and how Real-Time hub feeds it events
- Choose a schedule or a trigger from the deciding word in a scenario
From earlier lessons · 1 of 2
A pipeline must run the same Copy activity once for each of 40 table names in an array. Which activity runs that loop?
Pick one answer.
From earlier lessons · 2 of 2
How does a pipeline run a Fabric notebook as one of its steps?
Pick one answer.
Northwind Rides' maintenance partner drops CSV files whenever a repair crew finishes, at any hour. Your pipeline loads them every night at 2 AM. A file that lands at 2:05 AM waits a full day to reach the ops report. The ops manager asks why a scooter fixed this morning still shows as broken.
Three ways a job starts
Exam depth: know it cold.
A job is one run of a Fabric item, such as one pipeline run or one notebook run. A job can start in three ways.
- On demand: you select Run. This is how you test.
- Scheduled: a schedule starts the job at set times, such as every night at 2 AM.
- Event-based: an event-based trigger starts the job when something happens, such as a new file landing in OneLake.
A schedule watches the clock. A trigger watches for events. The rest of this lesson is about those two.
Schedules: run on the clock
Exam depth: know it cold.
Items that run jobs, such as a Pipeline or a Notebook, share one built-in job scheduler. In a pipeline, select Schedule on the Home tab. For other items, open the item's ... menu in the workspace and select Schedule.
| Setting | What it controls |
|---|---|
| Repeat | Minute-based (every 1 to 720 minutes), hourly (1 to 72 hours), daily, weekly or monthly. |
| Interval or times | How often, or which clock times. Daily allows up to 10 times a day. |
| Start and end date and time | When the schedule is active. A pipeline schedule needs both. |
| Time zone | Which local clock the times follow. Daylight saving is handled for you. |
One pipeline can have up to 20 schedules, each with its own repeat and times. A schedule can also pass values to the pipeline's parameters, which you meet next lesson.
You are a data engineer at Northwind Rides. A notebook rebuilds the station status table. The ops team in Chicago needs it refreshed every 30 minutes, on Chicago time. You need the least effort. What should you do?
Pick one answer.
Event-based triggers: run when something happens
Exam depth: know it cold.
An event is a small message that says something just happened, such as "file created". Fabric publishes its own events, called Fabric events. You find them in the Real-Time hub, the one place per tenant that lists the streams and events you can use. Every tenant has it, with nothing to set up.
| Event group | Raised when | Example event type |
|---|---|---|
| OneLake events | A file or folder is created, deleted or renamed in OneLake. | Microsoft.Fabric.OneLake.FileCreated |
| Job events | A Fabric job is created, changes status, succeeds or fails. | Microsoft.Fabric.ItemJobFailed |
| Workspace item events | An item is created, updated or deleted. | Microsoft.Fabric.ItemCreateSucceeded |
| Azure Blob Storage events | A blob (a file in Azure storage) is created, replaced or deleted. | Microsoft.Storage.BlobCreated |
Each event has a subject: the path of the file or item it's about, such as /Files/maintenance/repair_0412.csv. Filter on the subject so the trigger fires only for the folder you care about.
Activator: the engine behind every trigger
Exam depth: know it cold.
Fabric Activator is a no-code engine that watches events and takes an action when a condition is met. Every event-based trigger is an Activator rule underneath. Older pages call it Data Activator.
A rule has three parts:
- Monitor: the events to watch, such as
FileCreatedin one Lakehouse folder. - Condition: when to fire. For a trigger, this is usually On each event.
- Action: what to do. Activator can run a pipeline, notebook, Spark job definition, dataflow, Copy job or User Data Function. It can also send an email or a Teams message, or start a Power Automate flow, Microsoft's no-code workflow tool.
When you add a trigger from the pipeline canvas, Fabric saves the rule in its own item. The workspace lists that item with the type Reflex.
Match
Match each Northwind Rides happening to the event group that reports it
Pick an item on the left, then its match on the right.
You are a data engineer at Northwind Rides. A pipeline loads raw trips, and a separate Dataflow Gen2 cleans them. The pipeline takes anywhere from 10 to 50 minutes. The dataflow must start as soon as the pipeline succeeds, and the two items must stay separate. What should you use?
Pick one answer.
Schedule or trigger?
Exam depth: know it cold.
| The scenario says | Pick |
|---|---|
| Run at fixed times, such as hourly or every weekday at 6 AM. | Schedule. |
| Run as soon as a file lands, at unpredictable times. | Trigger on OneLake or Blob Storage events. |
| Start one job right after another job succeeds. | Trigger on job events, or chain both in one pipeline. |
| Tell someone when a scheduled run fails. | Failure notifications on the schedule. |
| React to any failed job, including on-demand runs. | Activator rule on ItemJobFailed. |
Decision rule: if the scenario names a time, use a schedule; if it names something that happens, use a trigger.
You are a data engineer at Northwind Rides. Payment data must be in the Warehouse by 6 AM Eastern every weekday for a finance report. The source database is always available. You need the simplest setup. What should you use?
Pick one answer.
Try it in Fabric
A free Fabric trial is enough. You need a workspace with a Pipeline and a Lakehouse.
Add a schedule
- Open the pipeline. On the Home tab, select Schedule.
- Select Add schedule. Under Schedule type, keep Fixed.
- Set Repeat to By the minute and Interval to 15.
- Set the Start date and time, the End date and time and your Time zone.
- Optional: add your email under Failure notifications.
- Select Save. Turn the schedule off with its toggle when you're done.
Add a file trigger
- In the same pipeline, select Trigger on the Home tab. The Set alert pane opens.
- For the source, choose Select events, then pick OneLake events.
- For the event type, select Microsoft.Fabric.OneLake.FileCreated.
- Select Add a OneLake source, choose your Lakehouse, then a folder under Files.
- Choose the workspace that stores the trigger, name it, and select Create.
- Upload a small file to that folder and check that a new pipeline run appears.
Exam-style practice
You are a data engineer at Northwind Rides. The Lakehouse sits in a workspace on a West Europe capacity. A teammate builds an Activator rule on OneLake FileCreated events in a workspace on an East US capacity. Files land, but the rule never fires. What is the most likely cause?
Pick one answer.
You are a data engineer at Northwind Rides. A notebook must process each partner CSV as soon as it lands in the Lakehouse. You want no pipeline and no item running when no file arrives. What should you do?
Pick one answer.
You are a data engineer at Northwind Rides. A nightly pipeline has a schedule, with the ops mailbox under Failure notifications. During testing, a developer starts the pipeline with Run and it fails. Nobody gets an email. Why?
Pick one answer.
Worth keeping
- A job starts on demand, on a schedule, or from an event-based trigger.
- Schedules set repeat, interval, start and end, and time zone; pipelines need an end date.
- Real-Time hub lists Fabric events: OneLake, job, workspace item and Azure Blob Storage events.
- Every event-based trigger is an Activator rule: monitor, condition, action.
- A named time means a schedule; a named happening means a trigger.
On the job
Here's how Northwind Rides starts its jobs after a few weeks.
The payments copy from SQL Server runs on a schedule at 4 AM Eastern, weekdays only. Failure notifications go to the data team's shared mailbox.
The partner's maintenance CSVs arrive at random times. An Activator rule on FileCreated events, filtered to /Files/maintenance/, starts the load pipeline soon after each file lands. The pipeline reads the file's name with @pipeline()?.TriggerEvent?.FileName, so it loads only that file.
A second rule watches job events. When the load pipeline succeeds, it starts the notebook that rebuilds the station table. A third rule posts in the ops team's Teams channel whenever any of these jobs fails.
Nobody guesses at run times, and nothing runs with no work to do.
That trigger handed the pipeline a file name it couldn't know in advance. Next lesson you learn the expression language behind @pipeline(), and turn one pipeline into a loader for every table Northwind owns.
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 (12)
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
- [114]Microsoft Learn: Run, schedule, or use events to trigger a pipeline
- [115]Microsoft Learn: Job scheduler in Microsoft Fabric
- [116]Microsoft Learn: What is Fabric Activator?
- [117]Microsoft Learn: Introduction to Azure and Fabric events
- [118]Microsoft Learn: Introduction to Fabric Real-Time hub
- [119]Microsoft Learn: Explore OneLake events in Fabric Real-Time hub
- [120]Microsoft Learn: Explore Job events in Fabric Real-Time hub
- [121]Microsoft Learn: Explore Fabric workspace item events in Fabric Real-Time hub
- [122]Microsoft Learn: Tutorial: Orchestrate Fabric jobs with Job events
- [123]Microsoft Learn: Build event-driven Pipelines with OneLake events and Azure Blob Storage events
- [124]Microsoft Learn: What is Real-Time Intelligence?