Implement and manage an analytics solution Study Guide — DP-700

Implement and Manage an Analytics Solution

This domain covers the operational and governance layer of Microsoft Fabric: how you configure workspaces, enforce security, manage the lifecycle of artifacts, and orchestrate data movement. Microsoft publishes all three DP-700 domains at 30–35% each (not exact point values) — this domain is roughly tied with the other two, not the largest. Expect questions that test your ability to choose the right security model, select the correct orchestration tool, configure deployment pipelines, and apply governance controls—often by eliminating options that work in Power BI but not Fabric, or that apply to the wrong tier or scope.

Spark, Domain, OneLake, and Dataflows Gen2 Workspace Settings

Spark Workspace Settings

Spark compute in Fabric is governed at the workspace level. Key settings you must know:

The Environment item (a Fabric artifact) pins library dependencies and Spark configuration to a reusable object. Attaching an Environment to a notebook or Spark job definition overrides workspace-level pool settings for that item.

Domain Settings

A Fabric domain is an administrative grouping of workspaces aligned to business units. Domains are configured in the Fabric Admin Portal, not in individual workspace settings.

• A workspace can belong to exactly one domain.
• Domain admins can override tenant-level settings for their domain (e.g., default storage format, export controls).
• Delegated tenant settings allow domain admins to enable/disable features that the tenant admin has made delegatable.

OneLake Workspace Settings

OneLake is the single logical data lake underlying all Fabric items. Workspace-level OneLake settings include:

• Default storage format: Delta (default) or Parquet without transaction log. Delta is required for Lakehouse table operations.
• OneLake data access roles (preview): grant read access to specific OneLake folders without granting workspace membership.
• Disaster recovery: geo-redundant storage toggle per workspace (requires Premium/Fabric capacity).

Dataflows Gen2 Workspace Settings

Dataflows Gen2 (not to be confused with Dataflows Gen1 / Power Query Online dataflows) stage data through an internal staging lakehouse before writing to the destination. Workspace settings relevant to Dataflows Gen2:

• Staging lakehouse: auto-created per workspace; cannot be shared across workspaces.
• Fast Copy: uses copy activity engine for large tables instead of Power Query mashup engine; enabled per dataflow or per step.
• Gateway assignment: set at workspace level for on-premises or VNET data sources.

Common traps

• Confusing Dataflows Gen1 (Power BI service, writes to Power BI datasets) with Dataflows Gen2 (Fabric, writes to any Fabric destination including Lakehouse, Warehouse, Azure Data Lake).
• Assuming the Starter pool supports autoscale — it does not; only custom pools autoscale.
• Thinking Environment items are workspace-wide by default — they must be explicitly attached to each notebook or job.
• Domain settings are in the Admin Portal, not workspace settings.

Version Control, Database Projects, and Deployment Pipelines

Git Integration (Version Control)

Fabric workspaces support Git integration with Azure DevOps and GitHub. Key facts:

Each supported item is serialized as a folder in the repo containing a .platform metadata file and item-specific definition files (e.g., .ipynb for notebooks, .json for pipeline definitions).

Database Projects

A Database project (SQL Database Project) in Fabric Warehouse enables schema-as-code workflows:

• Stored in a .sqlproj file in Git.
• Supports dacpac-style deployments: schema comparison, incremental publish.
• Integrated with the Fabric workspace Git sync — schema changes committed to Git can be published back to the warehouse.
• Does not move data — only DDL (tables, views, stored procedures, functions).

Deployment Pipelines

Deployment pipelines automate promotion of Fabric items across Development → Test → Production stages.

Deployment pipeline promotion flow showing how deployment rules override workspace-specific settings at each stage.

Key facts about deployment pipelines:

Deployment rules are the mechanism for environment-specific configuration. Without them, a pipeline would deploy the same connection string to both test and production.

Common traps

• Git integration does not replace deployment pipelines — Git is for version control; pipelines are for environment promotion.
• You need contributor rights in both source and target workspaces to deploy.
• Database projects move schema only, not data.
• Deployment pipelines require Premium or Fabric capacity on the target workspace, not necessarily the source.