Answer: They can turn on the Auto Stop feature for the SQL endpoint.

## Explanation The correct answer is **A** because the Auto Stop feature automatically stops the SQL endpoint after a period of inactivity, which directly addresses the requirement to minimize total running time while only running when necessary. ### Analysis of each option: **A. Turn on the Auto Stop feature for the SQL endpoint** - ✅ **CORRECT** - Auto Stop automatically stops the SQL endpoint after a specified period of inactivity - This ensures the endpoint only runs when queries are being executed - When the dashboard refreshes hourly, the endpoint will start, execute queries, and then stop after the idle timeout - This minimizes total running time while maintaining functionality **B. Ensure the dashboard's SQL endpoint is not one of the included query's SQL endpoint** - ❌ **INCORRECT** - This would create configuration issues and likely prevent the dashboard from working properly - Dashboards need to use the same SQL endpoint as their queries to execute correctly - This approach doesn't address minimizing running time **C. Reduce the cluster size of the SQL endpoint** - ❌ **INCORRECT** - Reducing cluster size affects performance and capacity, not running time - A smaller cluster still runs continuously if not stopped - This doesn't address the requirement to only run when necessary **D. Ensure the dashboard's SQL endpoint matches each of the queries' SQL endpoints** - ❌ **INCORRECT** - This is a configuration requirement for dashboards to work properly - While necessary for functionality, it doesn't minimize running time - Matching endpoints ensures queries execute but doesn't control when the endpoint runs **E. Set up the dashboard's SQL endpoint to be serverless** - ❌ **INCORRECT** - Serverless SQL endpoints provide automatic scaling and management - However, they still consume resources and run when queries are executed - Serverless doesn't specifically minimize total running time compared to Auto Stop - Auto Stop is more directly targeted at the requirement to only run when necessary ### Key Concept: The **Auto Stop** feature in Databricks SQL endpoints allows administrators to configure an idle timeout period. When the endpoint has been idle (no queries running) for the specified time, it automatically stops. This is the most direct solution for minimizing total running time while ensuring the endpoint is available when needed for scheduled dashboard refreshes.

Author: Keng Suppaseth