Picking the right build tool among a dataflow, a pipeline, and a notebook
Microsoft Fabric offers three primary tools for data ingestion and transformation: Dataflow Gen2 for low-code visual ETL, Pipelines for orchestration and copy activities at scale, and Notebooks for code-first transformations using Spark. Choosing the right tool depends on the persona (citizen integrator vs. data engineer), the complexity of transformation logic, data volume, and whether orchestration versus transformation is the primary goal.
Must-know
- Dataflow Gen2 uses Power Query (M language) and is best suited for low-code, self-service data transformation by users comfortable with Power BI-style dataflows, but it can become slower and costlier than Spark for very large datasets.
- Pipelines are primarily for orchestration (scheduling, chaining activities, and moving data at scale via Copy Activity) rather than complex row-level transformations; they can invoke Dataflows, Notebooks, or other pipelines as steps.
- Notebooks (using PySpark, Scala, SQL, or R) provide the most flexibility and performance for complex, large-scale transformations and are the preferred choice for data engineers who need full control, version control (Git integration), and custom logic.
- A common gotcha: Dataflow Gen2 output can be consumed by a Pipeline (e.g., as a source for further orchestration) or triggered from within a Pipeline, so the tools are often combined rather than mutually exclusive.
- Notebooks scale better for very large or complex transformations because they leverage Spark's distributed compute, whereas Dataflow Gen2's Power Query engine can hit performance/cost limits at high volumes.
- For simple scheduled copy/move operations with minimal transformation, Pipelines with Copy Activity are the most efficient and lowest-maintenance choice compared to spinning up a Notebook or Dataflow Gen2.
A data engineer must build a transformation that calls a custom PySpark function to enrich streaming IoT sensor readings with results from an external REST API, and needs to develop the logic interactively, running individual cells and inspecting intermediate DataFrames before scheduling it for production. Which Fabric item should the engineer use to author this transformation?
What you have tried across DP-700's objectives, not a readiness score.
Implement and manage an analytics solution
- Tuning a workspace's Spark compute defaults and pool sizing
- Grouping and governing workspaces with a Fabric domain
- Setting per-workspace defaults for OneLake storage
- Standing up an Airflow job runtime inside a workspace
- Connecting a workspace to a Git repository
- Managing schema changes with a database project
- Promoting Fabric items across environments with a deployment pipeline
- Granting and restricting access at the workspace level
- Locking down who can open a single Fabric item
- Layering row, column, object, and file-level security rules
- Hiding sensitive column values behind a dynamic mask
- Classifying Fabric items with a sensitivity label
- Marking a trusted item as promoted or certified
- Reading a Fabric audit log to see who did what
- Securing data at the OneLake storage layer
- Picking the right build tool among a dataflow, a pipeline, and a notebook
- Kicking off a job on a schedule or in response to an event
- Chaining notebooks and pipelines together with parameters and dynamic expressions
Ingest and transform data
- Deciding between a full reload and an incremental load
- Shaping source data ahead of a dimensional-model load
- Landing a continuous stream of data into storage
- Matching a workload to the right Fabric data store
- Picking a transformation tool from dataflows, notebooks, KQL, or T-SQL
- Linking to external data without copying it via a OneLake shortcut
- Keeping a source database continuously replicated into Fabric
- Moving data into Fabric with a data pipeline
- Writing transform logic in PySpark, SQL, or KQL
- Flattening related tables into one wide, denormalized shape
- Rolling records up with group-by aggregations
- Dealing with duplicate rows, gaps, and data that arrives late
- Selecting the right engine for a real-time workload
- Weighing storage-in-place against a linked shortcut for a Real-Time Intelligence table
- Weighing an accelerated shortcut against a standard one for query speed
- Routing and reshaping live events with an Eventstream
- Handling a continuous flow of records with Spark's structured streaming
- Querying and reshaping event data with KQL
- Aggregating a stream over sliding or tumbling time windows
Monitor and optimize an analytics solution
- Watching an ingestion job's health and progress
- Watching a transformation job's health and progress
- Tracking whether a semantic model's refresh actually succeeded
- Setting up an alert to catch a failure early
- Tracking down why a pipeline run failed and fixing it
- Diagnosing why a dataflow run failed
- Debugging a notebook run that failed
- Troubleshooting a misbehaving Eventhouse
- Troubleshooting a misbehaving Eventstream
- Debugging a T-SQL statement that failed
- Fixing a broken or unreachable shortcut
- Speeding up a Lakehouse table with maintenance operations
- Making a slow pipeline run faster
- Tuning a Fabric warehouse for faster queries
- Improving throughput on real-time streaming components
- Tuning a Spark job to run faster and cheaper
- Making a slow query run faster
Coverage checked against the published exam guide on Aug 11, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.