Standing up an Airflow job runtime inside a workspace
Apache Airflow jobs in Microsoft Fabric provide a managed environment for running Airflow DAGs to orchestrate data pipelines and integrate with other Fabric items. Configuring the Airflow workspace settings involves managing environment settings, requirements/dependencies, and connections that control how DAGs execute within the workspace. Understanding these settings is essential for orchestrating complex workflows that span Fabric and external systems.
Must-know
- Apache Airflow job is a Fabric item type that must be enabled via the tenant/admin portal setting before it appears as an option to create in a workspace.
- Environment configuration for an Airflow job lets you specify additional Python packages via a requirements.txt-style file, which are installed into the Airflow environment.
- Airflow jobs support Git integration, allowing DAG files to be synced from a connected repository (e.g., Azure DevOps or GitHub) into the workspace item.
- Connections and variables used by DAGs (such as Airflow Connections and Variables) can be configured within the Airflow job settings, similar to standard Airflow configuration, and are used to authenticate to Fabric items (like Lakehouses, Pipelines, or Notebooks) or external services.
- Capacity assignment matters: an Airflow job consumes capacity resources from the workspace's assigned Fabric capacity while it is running, so appropriate capacity must be allocated.
- Role-based access in the workspace (Admin/Member/Contributor/Viewer) governs who can edit Airflow job settings, upload DAGs, or only view run status, following standard Fabric workspace permission model.
A data engineer configures an Apache Airflow job in Microsoft Fabric to orchestrate pipelines. Several DAGs require the apache-airflow-providers-snowflake package, which is not included in the default Airflow image. The engineer needs the package available to every DAG run without modifying individual DAG files. Which workspace setting should the engineer configure?
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.