DP-700 - Implement and Manage an Analytics Solution (34% of the exam) - Section 1.1

Configure Microsoft Fabric workspace settings, including Spark, domain, OneLake, and Dataflows Gen2 settings.

Configure Spark environments, domain, OneLake, and Dataflows Gen2 settings within a Microsoft Fabric workspace. Recognise how capacity assignment and each workspace setting scope impacts compute behaviour, data residency, and pipeline execution.

Spark workspace settings and environmentsdomain workspace settingsOneLake workspace settingsDataflows Gen2 workspace settingsFabric capacity assignment

Practice question for this objective

Free sampleImplement and Manage an Analytics Solutionmedium

A Microsoft Fabric workspace contains scheduled Dataflows Gen2 that refresh several Lakehouse tables overnight. The team reports that some refreshes intermittently fail with throttling errors during the busy window, and they suspect the workspace lacks enough compute. Before tuning each dataflow, which workspace-level setting most directly determines whether these Dataflows Gen2 refreshes have the compute they need?

AThe capacity assigned to the workspace, because Dataflows Gen2 refreshes consume compute from that capacity and an undersized or saturated capacity throttles them. Correct
BThe workspace Spark environment default, because Dataflows Gen2 execute on the same Spark pool as notebooks and inherit that pool's node count.
CThe OneLake workspace setting that controls the storage region, because refresh throttling is caused by the distance between the dataflow and the destination tables.
DThe domain assigned to the workspace, because the domain sets a refresh concurrency ceiling that the overnight dataflows are exceeding during the busy window.

Dataflows Gen2 refreshes draw compute from the workspace's assigned Fabric capacity, so capacity sizing governs whether refreshes are throttled. Throttling under load is a compute-availability symptom, and Dataflows Gen2 consume capacity units from the Fabric capacity the workspace is assigned to rather than the notebook Spark pool; sizing or reassigning the capacity is therefore the workspace-level setting that determines whether concurrent overnight refreshes succeed.

Why A is correct: Dataflows Gen2 run on the Fabric capacity backing the workspace, so the assigned capacity and its available compute units govern whether concurrent overnight refreshes are throttled, making the capacity the most direct workspace-level lever.

Why B is wrong: It is tempting to assume all compute is Spark, but Dataflows Gen2 use the dataflow engine on the capacity, not the notebook Spark pool, so changing the Spark environment does not address dataflow refresh throttling.

Why C is wrong: Region affects latency in some scenarios but throttling errors signal a compute limit, not a storage-region distance; adjusting OneLake region settings would not relieve the capacity pressure causing the failures.

Why D is wrong: Domains group workspaces for governance and do not allocate compute or set refresh concurrency limits, so changing the domain assignment has no effect on whether the dataflow refreshes have enough capacity.

See more DP-700 practice questions, answers explained.

Exam traps in Implement and Manage an Analytics Solution

Answers that look right on this material and are not. Each one is a distractor from a different question in the DP-700 bank for this domain.

The Spark pool autoscale range on the workspace, because the external cluster borrows executors from that pool when it reads through the OneLake path.
Why it is wrong: An external cluster runs on its own compute and never borrows the workspace Spark pool, so the autoscale range has no bearing on whether it can read OneLake data and changing it does not grant or block access.
Change the Fabric capacity SKU that backs the domain so every workspace in the finance domain is billed against a larger reserved compute allocation.
Why it is wrong: Capacity SKUs are purchased and assigned at the tenant and workspace level, not from domain settings, and a domain is not backed by a capacity, so a domain admin cannot resize compute from the domain configuration.
Export each item from the trial workspace and import it into a brand new workspace that was created directly on the F-series capacity from the start.
Why it is wrong: Recreating items in a new workspace would work but is unnecessary effort and the scenario explicitly rules out recreating items, so this ignores the simpler in-place reassignment Fabric provides.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.