Associate-level certification covering implementing data engineering solutions using Microsoft Fabric: ingesting and transforming data, securing and managing an analytics solution, and monitoring and optimising it, with a worked explanation on every practice question.
Free sample questions
No account needed. Every question has a worked explanation, just like the full bank.
lock_openFree sampleImplement and Manage an Analytics Solutionmedium
A data engineering team runs many small notebook jobs in a Microsoft Fabric workspace. Each job currently waits several minutes before its Spark session is ready, and the delay dominates the short run times. The team wants new sessions to start in a few seconds without permanently reserving compute. Which Spark workspace setting should they configure to meet this requirement?
- AKeep the starter pool enabled so pre-warmed nodes back the workspace, letting Spark sessions begin in seconds without reserving a dedicated cluster.check_circle Correct
- BRaise the default node size on the starter pool so each session has more memory and processing power available the moment it begins running.
- CEnable high concurrency for the workspace so several notebooks share one Spark session and a new notebook reuses the already-running session.
- DCreate a custom Spark pool with autoscale disabled and a fixed minimum node count so the cluster is always sized and ready for incoming jobs.
The Microsoft Fabric starter pool provides pre-warmed nodes so Spark sessions start in seconds without reserving a dedicated cluster. Cold-start latency comes from provisioning new nodes; the starter pool keeps a set of nodes already running and attached to the capacity, so a notebook binds to a ready session in seconds and the nodes are reclaimed when idle, which a custom pool starting cold or a larger node size cannot match.
Why A is correct: The starter pool holds pre-allocated, pre-warmed nodes for the workspace, so a session attaches in a few seconds and the nodes are released when idle, which matches the need for fast starts without permanently reserved compute.
Why B is wrong: Larger nodes give each session more compute but do nothing about the cold-start delay; provisioning time is the stated problem, and bigger nodes can actually take longer to acquire rather than shortening startup.
Why C is wrong: High concurrency lets notebooks share a session and helps once a session exists, but the very first session in the workspace still pays the full provisioning cost, so it does not on its own deliver the few-second start the team wants.
Why D is wrong: A custom pool with a fixed floor would be ready, but a cold custom pool still provisions on demand and a permanent floor reserves compute continuously, which contradicts the requirement to avoid permanently reserving capacity.
lock_openFree sampleImplement and Manage an Analytics Solutionmedium
An organisation wants every data engineering team to reuse the same set of public Python libraries, a shared Spark configuration, and consistent runtime versions across all of their notebooks and Spark job definitions in a Microsoft Fabric workspace. They want to define this once and attach it rather than reconfiguring each item. Which Fabric construct should they create to satisfy this requirement?
- AAdd the libraries and Spark properties to each notebook with inline pip commands and session configuration cells so every notebook carries its own setup.
- BCreate a Fabric environment that bundles the runtime, Spark properties, and libraries, then attach it as the workspace default for notebooks and Spark job definitions.check_circle Correct
- CConfigure a custom Spark pool with the required node family and autoscale, since the pool definition also carries the runtime version and the attached library set.
- DPublish the libraries to a OneLake folder and reference that path from each notebook so the dependencies load from shared storage at session start.
A Microsoft Fabric environment packages runtime, Spark configuration, and libraries for reuse, and can be set as the workspace default for Spark items. Environments separate the reusable execution context from individual items: one environment defines the runtime, Spark properties, and library set, and setting it as the workspace default binds every notebook and Spark job definition to that context, whereas pools handle only compute and inline installs duplicate the setup per item.
Why A is wrong: Inline installs and session cells do work per notebook, but they must be repeated in every item and drift apart over time, which is exactly the per-item duplication the team is trying to avoid.
Why B is correct: A Fabric environment is the reusable container for runtime version, Spark configuration, and libraries; attaching it as the workspace default applies the same setup to every notebook and Spark job definition without per-item configuration.
Why C is wrong: A custom Spark pool controls compute sizing and scaling, but it does not hold libraries or runtime version; those belong to an environment, so the pool alone cannot standardise the shared library and runtime requirement.
Why D is wrong: OneLake stores data and files, not managed Spark library installs; pointing notebooks at a folder does not register packages in the Spark session, so this neither installs the libraries nor standardises runtime or Spark properties.
lock_openFree sampleImplement and Manage an Analytics Solutionmedium
A Fabric administrator is organising the tenant so that the finance, sales, and operations groups each manage their own set of workspaces, apply their own governance, and have a dedicated landing page that groups their content. The administrator wants a tenant-level grouping construct that workspaces are assigned to, rather than relying on workspace names alone. Which Microsoft Fabric feature should the administrator use?
- AAssign each group's workspaces to a separate Fabric capacity so the capacity boundary acts as the grouping that keeps each group's content together.
- BUse a OneLake shortcut from a parent workspace into each group's workspace so all of the group content appears under one shared catalogue view.
- CCreate a domain for each business group and assign that group's workspaces to its domain, with a domain admin governing the grouped content.check_circle Correct
- DCreate a workspace folder hierarchy inside one shared workspace and place each group's items in its own folder under that single workspace.
Microsoft Fabric domains group workspaces by business area at the tenant level with delegated governance, unlike capacities, shortcuts, or folders. Domains exist precisely to map data ownership onto business areas: an administrator assigns whole workspaces to a domain, delegates a domain admin, and applies domain-scoped settings, which capacity assignment, OneLake shortcuts, and within-workspace folders cannot do because they govern compute, data access, and intra-workspace layout respectively.
Why A is wrong: Capacity governs compute and billing, not logical content grouping; several unrelated groups can share one capacity and one group can span several capacities, so the capacity boundary does not provide the data-ownership grouping described.
Why B is wrong: A shortcut surfaces data items in place across workspaces, but it is a data-access mechanism, not a tenant grouping with delegated governance, so it cannot give each group its own managed boundary and landing page.
Why C is correct: Domains are the tenant-level construct for grouping workspaces by business area, with delegated domain admins, domain-scoped governance, and a domain landing experience, which is exactly the per-group ownership and grouping the administrator wants.
Why D is wrong: Folders organise items within a single workspace and do not provide separate, delegated governance per group across multiple workspaces; the requirement is a tenant-level grouping of whole workspaces, which folders cannot express.
Examworthy is not affiliated with or endorsed by Microsoft. All questions are original, blueprint-aligned practice material. We never reproduce live exam items. DP-700 and related marks belong to their respective owners.
