Discuss Databricks Databricks Certified Data Engineer Associate Exam Topic 1 Question 42

An engineering manager uses a Databricks SQL query to monitor ingestion latency for each data source. The manager checks the results of the query every day, but they are manually rerunning the query each day and waiting for the results.

Which of the following approaches can the manager use to ensure the results of the query are updated each day?

AThey can schedule the query to refresh every 1 day from the SQL endpoint's page in Databricks SQL.

BThey can schedule the query to refresh every 12 hours from the SQL endpoint's page in Databricks SQL.

CThey can schedule the query to refresh every 1 day from the query's page in Databricks SQL.

DThey can schedule the query to run every 1 day from the Jobs UI.

EThey can schedule the query to run every 12 hours from the Jobs UI.

Suggested Answer: A

The SQL keyword that can be used to convert a table from a long format to a wide format isPIVOT.The PIVOT clause is used to rotate the rows of a table into columns of a new table1.The PIVOT clause can aggregate the values of a column based on the distinct values of another column, and use those values as the column names of the new table1.The PIVOT clause can be useful for transforming data from a long format, where each row represents an observation with multiple attributes, to a wide format, where each row represents an observation with a single attribute and multiple values2.For example, the PIVOT clause can be used to convert a table that contains the sales of different products by different regions into a table that contains the sales of each product by each region as separate columns1.

The other options are not suitable for converting a table from a long format to a wide format.CONVERT is a function that can be used to change the data type of an expression3.WHERE is a clause that can be used to filter the rows of a table based on a condition4.TRANSFORM is a keyword that can be used to apply a user-defined function to a group of rows in a table5. SUM is a function that can be used to calculate the total of a numeric column.

1:PIVOT | Databricks on AWS

2:Reshaping Data - Long vs Wide Format | Databricks on AWS

3:CONVERT | Databricks on AWS

4:WHERE | Databricks on AWS

5:TRANSFORM | Databricks on AWS

: [SUM | Databricks on AWS]

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

30 comments · newest first

Rupert 10 months ago

C seems like a solid option, but I’d double-check the settings.

Callie 11 months ago

Wait, can you really schedule it from the SQL endpoint? That’s new to me!

Carman 11 months ago

B sounds good too, but 12 hours might be overkill.

Evan 11 months ago

I think D is better since it uses the Jobs UI.

Hyun 11 months ago

A is the way to go for daily updates!

Christoper 12 months ago

I have a vague memory of the 12-hour refresh option being discussed, but I thought it was more common to set it for a full day.

Lashaunda 12 months ago

I feel like the SQL endpoint's page is where you can set refresh intervals, but I can't recall if it was specifically for daily updates.

Melvin 12 months ago

I think scheduling from the Jobs UI was mentioned in a practice question we did. It seems like a solid option for automation.

Melita 1 year ago

I remember we talked about scheduling queries in Databricks SQL, but I'm not sure if it was from the SQL endpoint or the query's page.

Berry 1 year ago

I'm a little confused by the options mentioning 12-hour schedules. Is that a valid option for this use case, or is the manager really just looking to refresh the data once per day? I'll need to think through the requirements carefully.

Ranee 1 year ago

Okay, I've got this! The manager can schedule the query to refresh every 1 day from the SQL endpoint's page in Databricks SQL. That's option A, and it seems like the most direct way to automate the daily refresh.

Lashunda 1 year ago

After reviewing the options again, I think the best approach is to schedule the query to refresh every 1 day from the SQL endpoint's page in Databricks SQL, as described in option A. That seems like the most straightforward way to automate the daily check.

Rosio 1 year ago

This seems like a straightforward question about scheduling a Databricks SQL query to run automatically. I think the key is to identify the correct way to schedule the query, whether it's from the SQL endpoint page or the Jobs UI.

Jerlene 1 year ago

As an engineer, I'd advise the manager to automate this process as much as possible. Option C or D are the way to go - no need to be manually running queries Jerlenery day!

Eveline 1 year ago

↳ replying to Jerlene

Definitely, manual reruns are a waste of time. Option D from the Jobs UI seems like a good solution too.

Paris 1 year ago

↳ replying to Jerlene

I agree, Option C is the most efficient way to ensure the results are updated daily.

Narcisa 1 year ago

↳ replying to Jerlene

Option C sounds like a good choice. Automating the query refresh will save time.

Veronica 1 year ago

I'm torn between Options B and E. 12 hours seems a bit excessive, but the manager might want the latest data as soon as possible. Hmm, tough call.

Alpha 1 year ago

Haha, looks like the manager has been doing some manual labor there. Option E is the way to go - 12 hours is the perfect balance between up-to-date data and not driving themselves crazy!

Maile 1 year ago

↳ replying to Alpha

User 3: Definitely, that way they don't have to manually run it every day.

Doyle 1 year ago

↳ replying to Alpha

User 2: Yeah, refreshing every 12 hours seems like a good balance.

Latonia 1 year ago

↳ replying to Alpha

User 1: I agree, option E sounds like the best choice.

Bea 1 year ago

I'd go with Option D. Using the Jobs UI gives you more flexibility and control over the scheduling, plus it's a bit more future-proof.

Lizette 1 year ago

↳ replying to Bea

Yeah, Option D definitely seems like the best approach for automating the query refresh.

Paz 1 year ago

↳ replying to Bea

I agree, the Jobs UI seems like the most efficient way to ensure the query is updated daily.

Rasheeda 1 year ago

↳ replying to Bea

Option D sounds like a good choice. It's always better to have more control over the scheduling.

Stevie 1 year ago

Option C seems like the most straightforward way to automate the query refresh. Scheduling it directly from the query page makes sense.

Jesse 2 years ago

But wouldn't it be easier to manage the scheduling directly from the SQL endpoint's page? Option A seems more straightforward to me.

Stefany 2 years ago

I disagree, I believe option D is more efficient. Scheduling the query to run every 1 day from the Jobs UI seems like a better approach.

Jesse 2 years ago

I think option A is the best choice. It makes sense to schedule the query to refresh every 1 day from the SQL endpoint's page.

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