New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Databricks Certified Data Engineer Associate Exam - Topic 1 Question 7 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Associate exam
Question #: 7
Topic #: 1
[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 of the following approaches can the data engineer use to minimize the total running time of the SQL endpoint used in the refresh schedule of their dashboard?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Felton
4 months ago
I disagree, matching SQL endpoints seems unnecessary.
upvoted 0 times
...
Delfina
4 months ago
Definitely need that serverless option for flexibility!
upvoted 0 times
...
Markus
4 months ago
Not sure about that, isn't it risky to change the cluster size?
upvoted 0 times
...
Nieves
4 months ago
I think reducing the cluster size could help too.
upvoted 0 times
...
Hillary
4 months ago
Auto Stop is a game changer for saving costs!
upvoted 0 times
...
Venita
5 months ago
Setting up a serverless SQL endpoint sounds familiar, and I think it could help with efficiency, but I need to double-check how it relates to the refresh schedule.
upvoted 0 times
...
Joseph
5 months ago
I feel like ensuring the SQL endpoints match is important for performance, but I can't recall if it helps with minimizing running time specifically.
upvoted 0 times
...
Yen
5 months ago
I think I practiced a question similar to this where reducing the cluster size was mentioned, but I'm not confident if that applies here.
upvoted 0 times
...
Belen
5 months ago
I remember something about the Auto Stop feature being useful for saving costs, but I'm not entirely sure if it directly minimizes running time.
upvoted 0 times
...
Matt
5 months ago
Okay, I think I've got this. The key is that the question says you would choose between the two, but not use both together. So the correct answer must be True - you wouldn't use an enterprise service bus and an orchestration product simultaneously in the same architecture.
upvoted 0 times
...
Mari
5 months ago
Hmm, this looks like a tricky one. I'll need to think carefully about the different configuration files and how they relate to repository performance.
upvoted 0 times
...
Linette
5 months ago
Okay, I've reviewed the question and the options. I believe the correct answer is Option C, since the cumulative effect of an inventory pricing change would be reported as an adjustment to retained earnings, not on the current year's income statement.
upvoted 0 times
...
Lynna
5 months ago
I thought 'Ctx' was for context, but I can't recall if it can be used interchangeably with 'Vrf'. Maybe option D is correct after all?
upvoted 0 times
...
Evangelina
10 months ago
Option D seems like it would just add more complexity. I agree with the others - go with the serverless option (Option E) for a simple and effective solution.
upvoted 0 times
Tony
9 months ago
C: Definitely, serverless will streamline the process and minimize running time.
upvoted 0 times
...
Bobbye
9 months ago
B: Agreed, keeping it simple with a serverless setup is the best approach.
upvoted 0 times
...
Margurite
9 months ago
A: I think Option E is the way to go, serverless sounds like the most efficient choice.
upvoted 0 times
...
...
Corrina
10 months ago
Haha, I bet the data engineer is wishing they had a magic wand to make this all work perfectly. Serverless SQL (Option E) seems like the most effortless way to go.
upvoted 0 times
...
Macy
10 months ago
Hmm, I'm not sure if reducing the cluster size (Option C) is the best idea. That might impact performance. I think the serverless approach (Option E) is the cleanest solution here.
upvoted 0 times
Francisca
8 months ago
Definitely, it would help minimize the total running time of the SQL endpoint.
upvoted 0 times
...
Frederick
8 months ago
That makes sense, the serverless approach would be more efficient.
upvoted 0 times
...
Kati
8 months ago
I think setting up the dashboard's SQL endpoint to be serverless is the way to go.
upvoted 0 times
...
Thurman
8 months ago
I agree, reducing the cluster size might not be the best idea.
upvoted 0 times
...
Delmy
8 months ago
Definitely, it would help minimize the total running time of the SQL endpoint.
upvoted 0 times
...
Genevive
9 months ago
That makes sense, the serverless approach would be more efficient.
upvoted 0 times
...
Louisa
9 months ago
I think setting up the dashboard's SQL endpoint to be serverless is the way to go.
upvoted 0 times
...
Cathern
10 months ago
I agree, reducing the cluster size might not be the best idea.
upvoted 0 times
...
...
Ronnie
10 months ago
Option E is the way to go! Serverless SQL endpoints will only run when needed, minimizing the total running time. I like that efficiency.
upvoted 0 times
Levi
9 months ago
User 2: Agreed! It's great to have that kind of efficiency in place.
upvoted 0 times
...
Son
10 months ago
User 1: Option E is definitely the best choice. Serverless SQL endpoints will save a lot of time.
upvoted 0 times
...
...
Skye
11 months ago
I see both points, but I think option C could also be effective. Reducing the cluster size may help optimize performance.
upvoted 0 times
...
Gail
11 months ago
I disagree, I believe option E is the way to go. Setting up the SQL endpoint to be serverless can also reduce running time.
upvoted 0 times
...
Loreta
11 months ago
I think option A is the best choice. Auto Stop feature can help minimize running time.
upvoted 0 times
...

Save Cancel