Halloween Special 2026! Get Up to 25% OFF Practice Questions! Limited Time - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Databricks Certified Data Engineer Associate Exam - Topic 2 Question 60 Discussion

Posted by Rosalind on Mar 08, 2026 at 05:33 AM

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 queries on multiple datasets associated with it. The data that feeds the dashboard is automatically processed using a Databricks Job.

Which approach can the data engineer use to minimize the total running time of the SQL endpoint used in the refresh schedule of their dashboard?

Suggested Answer: B

To minimize the total running time of the SQL endpoint used in the refresh schedule of a dashboard in Databricks, the most effective approach is to utilize the Auto Stop feature. This feature allows the SQL endpoint to automatically stop after a period of inactivity, ensuring that it only runs when necessary, such as during the dashboard refresh or when actively queried. This minimizes resource usage and associated costs by ensuring the SQL endpoint is not running idle outside of these operations.

Reference: Databricks documentation on SQL endpoints: SQL Endpoints in Databricks


Get Premium Databricks Certified Data Engineer Associate Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
26 comments · newest first
EV
Eve 2 months ago
But D ensures all queries are optimized together. That’s important!
NO
Norah 2 months ago
Option C could work too. Serverless is efficient.
BI
Billi 2 months ago
I agree! It makes sense to only run when needed.
KA
Karol 2 months ago
I think option B is the best. Auto Stop saves resources.
OL
Olive 2 months ago
True, but matching SQL endpoints could optimize performance as well.
LE
Leigha 3 months ago
Reducing cluster size might not help much. Queries could lag.
PA
Patria 3 months ago
I agree, but option C sounds good too. Serverless is efficient.
MO
Mozell 3 months ago
I think option B is the best choice. Auto Stop saves resources.
DE
Desirae 3 months ago
I’m leaning towards B as well. Less running time is key!
HO
Holley 3 months ago
Option D could work, but it might complicate things.
TH
Thora 4 months ago
I agree, but option C sounds good too. Serverless is efficient.
OL
Oliva 4 months ago
I think option B is the best. Auto Stop saves resources.
AI
Ailene 4 months ago
I thought the SQL endpoint always needed to be running for dashboards.
GL
Glenn 4 months ago
Wait, can you really reduce the cluster size and still get good performance?
FE
Felix 6 months ago
Not sure if option D is necessary, seems a bit overkill.
YV
Yvette 6 months ago
I think option C is better, serverless is the way to go!
GA
Galen 6 months ago
Definitely go with option B, Auto Stop is a game changer!
EL
Elly 6 months ago
Reducing cluster size might not help much if queries are heavy.
DO
Dorcas 6 months ago
Wait, can you really set the SQL endpoint to be serverless? That sounds cool!
WI
Willard 6 months ago
Not sure about option D, seems like overkill for just a dashboard.
MA
Margery 7 months ago
I think option C is the best choice for cost efficiency.
LI
Lizbeth 7 months ago
Definitely go with option B, Auto Stop is a game changer!
GL
Glenn 7 months ago
I vaguely recall that matching SQL endpoints could help with efficiency, but I’m not sure if that’s the right approach for this specific scenario.
OL
Olga 7 months ago
I practiced a similar question where reducing cluster size was mentioned, but I feel like that might not be the best choice for performance.
BE
Bernardo 7 months ago
I think serverless SQL endpoints could be a good option since they scale automatically, but I’m not completely confident about how they work with scheduled refreshes.
IS
Isaiah 7 months ago
I remember something about the Auto Stop feature being useful for saving costs, but I'm not sure if it actually minimizes running time.
0/2000 characters

Save Cancel