Databricks-DA-Assoc Executing Queries with Databricks SQL Practice Question
Which option is recommended to ensure that a SQL Warehouse automatically terminates when no queries are being executed, thereby minimizing unnecessary costs?
⚠ Common exam trap
Candidates often suggest manually stopping the warehouse or using cluster termination, overlooking the specific 'Auto-stop' configuration designed for SQL Warehouses to manage costs.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Setting 'Auto-stop' in the Warehouse configuration.
Auto-stop is a fundamental cost-management feature for Databricks SQL. By configuring a reasonable auto-stop period, analysts can ensure that compute resources are released when idle. This is a critical best practice for maintaining a cost-efficient data platform, particularly for development or staging environments where queries may be sporadic. Proper use of auto-stop directly impacts the overall cloud bill and is an essential configuration step for every SQL Warehouse instance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manual shutdown via the CLI.
Why it's wrong here
Manual shutdown is inefficient and prone to human error, as users often forget to stop the warehouse after their work. Automation via the built-in 'Auto-stop' feature is the recommended industry approach for managing compute resource lifecycle and controlling cloud spending without requiring constant manual intervention from the team.
- ✓
Setting 'Auto-stop' in the Warehouse configuration.
Why this is correct
The 'Auto-stop' setting is specifically designed to terminate inactive SQL Warehouses after a set period of idle time. This feature is the most efficient and reliable method to ensure compute costs are minimized, as it automates the shutdown process without needing any manual action from the end-user.
- ✗
Using a Cron job to delete the warehouse.
Why it's wrong here
Deleting a warehouse via a Cron job is destructive and unnecessary. Once deleted, the warehouse must be completely re-provisioned, which is a slow and complex process. Auto-stop handles the temporary suspension of resources while keeping the warehouse definition intact, which is the correct way to manage compute resources.
- ✗
Reducing the cluster size to zero.
Why it's wrong here
You cannot set a cluster size to zero; the minimum size is constrained by the warehouse configuration. Furthermore, changing the size does not handle idle-state termination. The correct method for cost-effective resource management in Databricks SQL is utilizing the 'Auto-stop' feature provided within the warehouse's own settings interface.
About these practice questions
This Databricks-DA-Assoc question is part of Courseiva's 291-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DA-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DA-Assoc exam.