Which is NOT a benefit of using the Starter Spark Pool in Microsoft Fabric?

Which is NOT a benefit of using the Starter Spark Pool in Microsoft Fabric?

• A. Full customization of Spark node size
• B. Uses prehydrated compute resources
• C. Fast startup time
• D. Automatically scaled based on workload

Answer: (A)

This question tests whether Starter Spark Pool supports full customization of Spark node size. Starter Spark Pool is designed to be ready to use with prehydrated compute resources, which helps jobs start quickly and reduces cold-start delays. It also benefits from fast startup times and the ability to scale automatically based on workload, making it convenient for bursty or uncertain demand. However, it does not provide full customization of Spark node size; the pool is preconfigured with fixed resources to streamline provisioning and speed up access. That’s why this option is not a benefit of the Starter Spark Pool.

This question tests whether Starter Spark Pool supports full customization of Spark node size. Starter Spark Pool is designed to be ready to use with prehydrated compute resources, which helps jobs start quickly and reduces cold-start delays. It also benefits from fast startup times and the ability to scale automatically based on workload, making it convenient for bursty or uncertain demand. However, it does not provide full customization of Spark node size; the pool is preconfigured with fixed resources to streamline provisioning and speed up access. That’s why this option is not a benefit of the Starter Spark Pool.