Databricks Exam Databricks Certified Data Engineer Associate Topic 2 Question 36 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Associate exam

Question #: 36
Topic #: 2

[All Databricks Certified Data Engineer Associate Questions]

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?

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

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

CO They can set up the dashboard's SQL endpoint to be serverless.

D0 They can ensure the dashboard's SQL endpoint matches each of the queries' SQL endpoints.

Show Suggested Answer

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

by Cecil at Sep 13, 2024, 11:28 AM

Limited Time Offer

25%

Off

Get Premium Databricks Certified Data Engineer Associate Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Florinda

8 months ago

Matching the dashboard's SQL endpoint to the queries' SQL endpoints? Sounds like a lot of work, if you ask me. I'd go for the Auto Stop option - keep it simple!

upvoted 0 times

...

Valentine

8 months ago

Haha, I bet the data engineer wishes they could just snap their fingers and make the SQL endpoint disappear when it's not needed! Auto Stop is the way to go, for sure.

upvoted 0 times

Carman

8 months ago

C) They can set up the dashboard's SQL endpoint to be serverless.

upvoted 0 times

...

Jerry

8 months ago

B) They can turn on the Auto Stop feature for the SQL endpoint.

upvoted 0 times

...

Gladys

8 months ago

A) They can reduce the cluster size of the SQL endpoint.

upvoted 0 times

...

Barney

9 months ago

Serverless, all the way! That's the best approach to minimize the running time. No need to worry about cluster sizes or anything like that.

upvoted 0 times

...

James

9 months ago

Ooh, this is a tricky one! I think turning on the Auto Stop feature for the SQL endpoint is the way to go. That way, it only runs when it needs to, right?

upvoted 0 times

Timothy

8 months ago

C) They can set up the dashboard's SQL endpoint to be serverless.

upvoted 0 times

...

Gladys

8 months ago

That sounds like a good idea. It will help minimize the running time.

upvoted 0 times

...

Josefa

8 months ago

B) They can turn on the Auto Stop feature for the SQL endpoint.

upvoted 0 times

...

Honey

9 months ago

Serverless, huh? Sounds like something straight out of a sci-fi movie. Next thing you know, they'll be running the dashboard on a quantum computer or something.

upvoted 0 times

Hubert

8 months ago

User 3: I think setting up the dashboard's SQL endpoint to be serverless could be a good option in this case.

upvoted 0 times

...

Julene

8 months ago

User 2: Yeah, it's pretty cool. It can definitely help with optimizing running time.

upvoted 0 times

...

Alex

8 months ago

Serverless computing is actually a real thing now.

upvoted 0 times

...

Asuncion

10 months ago

Matching the SQL endpoints to the queries? Hmm, I don't know, that sounds like a lot of work. I'd rather just go with the Auto Stop option and let the system handle it.

upvoted 0 times

...

Luisa

10 months ago

That's a good point, Giovanna. Option C does sound like a good solution as well. It's all about optimizing the process.

upvoted 0 times

...

Glenn

10 months ago

Serverless is the way to go! No need to worry about cluster size or anything, it'll just scale up and down as needed.

upvoted 0 times

...

Giovanna

10 months ago

I disagree, I believe option C is more efficient. Setting up the SQL endpoint to be serverless will also help minimize running time.

upvoted 0 times

...

Joanna

10 months ago

The Auto Stop feature sounds like a great way to minimize the running time of the SQL endpoint. That way, it won't be wasting resources when it's not needed.

upvoted 0 times