Databricks Certified Data Engineer Associate Exam - 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

Arthur

3 months ago

Matching SQL endpoints is just common sense!

upvoted 0 times

...

Aron

3 months ago

Wait, can the SQL endpoint really auto-stop? Sounds too good to be true.

upvoted 0 times

...

Van

3 months ago

Serverless SQL endpoints are the way to go!

upvoted 0 times

...

Truman

4 months ago

Reducing the cluster size might not be enough.

upvoted 0 times

...

Tess

4 months ago

I think turning on the Auto Stop feature is a smart move.

upvoted 0 times

...

Pete

4 months ago

I feel like ensuring the dashboard's SQL endpoint matches the queries' endpoints might help, but I can't recall if that was the best approach for efficiency.

upvoted 0 times

...

Bonita

4 months ago

Reducing the cluster size sounds like it could save resources, but I wonder if that would slow down the queries too much during the refresh.

upvoted 0 times

...

Willard

4 months ago

I remember practicing a similar question where we discussed serverless SQL endpoints. That might help with minimizing costs, but does it really affect running time?

upvoted 0 times

...

Bronwyn

5 months ago

I think turning on the Auto Stop feature for the SQL endpoint could be a good option, but I'm not entirely sure how it impacts performance during refreshes.

upvoted 0 times

...

Shannan

5 months ago

Option D seems like it could be a good approach, ensuring the dashboard's SQL endpoint matches each of the queries' SQL endpoints. That way, you're not running any unnecessary resources. But I'm not sure if that's the most efficient solution overall.

upvoted 0 times

...

Malcolm

5 months ago

I'm a bit confused by this question. It seems like there are a few different approaches we could take, but I'm not sure which one would be the most effective. I'll have to think through the pros and cons of each option.

upvoted 0 times

...

Johnetta

5 months ago

I think the key here is to minimize the total running time of the SQL endpoint. Option B, turning on the Auto Stop feature, seems like a good way to do that since it will automatically stop the endpoint when it's not in use.

upvoted 0 times

...

Denise

5 months ago

Hmm, I'm leaning towards option C, setting up the dashboard's SQL endpoint to be serverless. That way, it will only be running when it's needed, which should help minimize the total running time. But I'll need to double-check the details on how serverless endpoints work.

upvoted 0 times

...

Jutta

5 months ago

Hmm, I'm a bit unsure about this. I think Rapid PVST+ and MST are both good choices, but I'm not sure which one is better. And I'm not sure if VTP or DTP is the better way to propagate VLAN information.

upvoted 0 times

...

Florinda

1 year 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

1 year 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

1 year ago

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

upvoted 0 times

...

Jerry

1 year ago

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

upvoted 0 times

...

Gladys

1 year ago

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

upvoted 0 times

...

Barney

1 year 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

1 year 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

1 year ago

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

upvoted 0 times

...

Gladys

1 year ago

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

upvoted 0 times

...

Josefa

1 year ago

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

upvoted 0 times

...

Honey

1 year 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

1 year 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

1 year ago

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

upvoted 0 times

...

Alex

1 year ago

Serverless computing is actually a real thing now.

upvoted 0 times

...

Asuncion

1 year 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

1 year 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

1 year 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

1 year 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

1 year 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