Databricks Certified Data Engineer - Associate

Explanation

The correct answer is C - They can turn on the Auto Stop feature for the SQL endpoint.

Why this is correct:

1. Auto Stop Feature: This feature automatically stops the SQL endpoint after a period of inactivity, which is exactly what the data engineer needs. Since the dashboard only refreshes once per day, the SQL endpoint can be stopped when not in use, minimizing its running time.

2. How it works: When Auto Stop is enabled, the SQL endpoint will automatically shut down after a configurable period of inactivity (typically 10-30 minutes). When the scheduled refresh occurs, the endpoint will automatically start up, run the queries, and then stop again after the inactivity period.

Why other options are incorrect:

A. They can ensure the dashboard’s SQL endpoint matches each of the queries’ SQL endpoints.

• This ensures consistency but doesn't minimize running time. Matching endpoints doesn't control when the endpoint runs.

B. They can set up the dashboard’s SQL endpoint to be serverless.

• Serverless SQL endpoints are always running and billed by compute usage, not by minimizing running time. They don't automatically stop when not in use.

D. They can reduce the cluster size of the SQL endpoint.

• This reduces compute cost but doesn't minimize the total running time. A smaller cluster still runs continuously unless stopped.

E. They can ensure the dashboard’s SQL endpoint is not one of the included query’s SQL endpoint.

• This doesn't make sense in this context and wouldn't help minimize running time. It might actually cause inefficiencies if queries use different endpoints.

Best Practice:

For dashboards that refresh infrequently (like once per day), enabling Auto Stop is the most cost-effective approach as it ensures the SQL endpoint only runs when needed and automatically stops after completing the refresh, minimizing both running time and costs.