You are configuring a Spark pool in Microsoft Fabric for a workload with highly variable data volumes. You want to ensure that the pool can handle peak loads without over-provisioning resources during quiet periods. Which setting should you adjust?
Autoscale allows you to define a minimum and maximum number of nodes for the Spark pool. The Fabric orchestrator automatically monitors the workload and scales the pool size within these boundaries. This ensures that resources are available for heavy processing while minimizing idle capacity and associated costs when the pool is quiet.
Why this answer
Autoscale on the Spark pool dynamically adjusts the number of nodes based on workload demand, allowing the pool to scale up for peak data volumes and scale down during quiet periods. This directly addresses the requirement to handle peaks without over-provisioning.
Exam trap
DP-700 often tests the confusion between Spark's dynamic allocation (executor-level, within fixed nodes) and Fabric's autoscale (node-level, adjusts pool size), leading candidates to pick the wrong scaling mechanism.
How to eliminate wrong answers
Option A is wrong because dynamic allocation of executors operates within the nodes already allocated to the pool; it does not add or remove nodes to match cluster-level demand, so it cannot handle peak loads that exceed the pool's node capacity. Option C is wrong because setting max memory per node is a static configuration that does not adapt to variable workloads and can cause over- or under-provisioning. Option D is wrong because the default Spark version is unrelated to resource scaling and does not affect capacity management.