A data engineer wants to schedule their Databricks SQL dashboard to refresh every hour, but they only want the associated SQL endpoint to be running when it is necessary. The dashboard has multiple…

Question

Options

• AThey can turn on the Auto Stop feature for the SQL endpoint.
• BThey can ensure the dashboard's SQL endpoint is not one of the included query's SQL endpoint.
• CThey can reduce the cluster size of the SQL endpoint.
• DThey can ensure the dashboard's SQL endpoint matches each of the queries' SQL endpoints.
• EThey can set up the dashboard's SQL endpoint to be serverless.

• A
  89% (39)
• C
  2% (1)
• D
  7% (3)
• E
  2% (1)

Explanation

The Auto Stop feature on a Databricks SQL endpoint (warehouse) automatically terminates the endpoint after a configurable idle period, meaning it only runs when actually serving queries. Since the dashboard refreshes hourly, the endpoint will start on demand, serve the queries, then shut down automatically - minimizing total running time. Option B is incorrect because mismatching endpoints doesn't reduce run time. Option C (smaller cluster) reduces cost per hour but not total run time. Option D (matching endpoints) is about consistency, not run time. Option E (serverless) is a billing/scaling model, not a mechanism to stop the endpoint when idle.

No community discussion yet for this question.