MENU
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?
Suggested Answer: C
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
33 comments · newest first
FE
Felton
11 months ago
I disagree, matching SQL endpoints seems unnecessary.
DE
Delfina
11 months ago
Definitely need that serverless option for flexibility!
MA
Markus
12 months ago
Not sure about that, isn't it risky to change the cluster size?
NI
Nieves
12 months ago
I think reducing the cluster size could help too.
HI
Hillary
12 months ago
Auto Stop is a game changer for saving costs!
VE
Venita
1 year 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.
JO
Joseph
1 year 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.
YE
Yen
1 year 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.
BE
Belen
1 year 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.
MA
Matt
1 year 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.
MA
Mari
1 year 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.
LI
Linette
1 year 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.
LY
Lynna
1 year 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?
EV
Evangelina
1 year 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.
TO
Tony
1 year ago
C: Definitely, serverless will streamline the process and minimize running time.
BO
Bobbye
1 year ago
B: Agreed, keeping it simple with a serverless setup is the best approach.
MA
Margurite
1 year ago
A: I think Option E is the way to go, serverless sounds like the most efficient choice.
CO
Corrina
1 year 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.
MA
Macy
1 year 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.
FR
Francisca
1 year ago
Definitely, it would help minimize the total running time of the SQL endpoint.
FR
Frederick
1 year ago
That makes sense, the serverless approach would be more efficient.
KA
Kati
1 year ago
I think setting up the dashboard's SQL endpoint to be serverless is the way to go.
TH
Thurman
1 year ago
I agree, reducing the cluster size might not be the best idea.
DE
Delmy
1 year ago
Definitely, it would help minimize the total running time of the SQL endpoint.
GE
Genevive
1 year ago
That makes sense, the serverless approach would be more efficient.
LO
Louisa
1 year ago
I think setting up the dashboard's SQL endpoint to be serverless is the way to go.
CA
Cathern
1 year ago
I agree, reducing the cluster size might not be the best idea.
RO
Ronnie
1 year 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.
LE
Levi
1 year ago
User 2: Agreed! It's great to have that kind of efficiency in place.
SO
Son
1 year ago
User 1: Option E is definitely the best choice. Serverless SQL endpoints will save a lot of time.
SK
Skye
2 years ago
I see both points, but I think option C could also be effective. Reducing the cluster size may help optimize performance.
GA
Gail
2 years 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.
LO
Loreta
2 years ago
I think option A is the best choice. Auto Stop feature can help minimize running time.