A workspace admin reviewing usage finds one all-purpose cluster accounted for a large share of last month's DBUs while its notebooks executed cells on roughly two days in that month. The cluster was created for a proof of concept, auto termination was switched off at creation, and no scheduled task is attached to it. The admin wants the underlying cause of the charge addressed rather than the symptom. What should the admin do?
- ASet an auto termination window on the cluster so that it shuts down after a defined idle period, which stops it billing through the stretches when nobody is running a cell. Correct
- BReduce the cluster's maximum worker count so that the same idle period consumes fewer DBUs, and ask the team to report any performance problem that follows.
- CEnable autoscaling on the cluster with a minimum of one worker, so that the cluster releases capacity by itself during the long stretches without activity.
- DMigrate the proof of concept notebooks to a serverless SQL warehouse with a short auto stop window, which removes the charge by retiring the cluster in favour of warehouse compute.
Why A is correct: All-purpose compute bills while it runs regardless of whether commands are executing, so the cause of the charge is a cluster left up with auto termination disabled, and restoring that setting stops the idle accrual.
Why B is wrong: A lower maximum trims the size of the bill without touching its cause: an idle cluster with fewer workers is still a running cluster billed at the all-purpose rate for weeks of doing nothing.
Why C is wrong: Autoscaling does release underutilised workers, which sounds like the fix, but it holds the minimum workers and the driver running indefinitely, so a cluster idle for most of a month keeps billing.
Why D is wrong: A serverless warehouse does stop when idle, but it runs SQL statements rather than proof of concept notebooks, so this replaces the workload's compute service instead of correcting the setting that caused the charge.