A data engineer has left the organization. The data team needs to transfer ownership of the data engineer's Delta tables to a new data engineer. The new data engineer is the lead engineer on the data team.
Assuming the original data engineer no longer has access, which of the following individuals must be the one to transfer ownership of the Delta tables in Data Explorer?
The workspace administrator is the only individual who can transfer ownership of the Delta tables in Data Explorer, assuming the original data engineer no longer has access. The workspace administrator has the highest level of permissions in the workspace and can manage all resources, users, and groups. The other options are either not possible or not sufficient to perform the ownership transfer. The Databricks account representative is not involved in the workspace management. The transfer is possible and not dependent on the original data engineer. The new lead data engineer may not have the necessary permissions to access or modify the Delta tables, unless granted by the workspace administrator or the original data engineer before leaving.Reference:Workspace access control,Manage Unity Catalog object ownership.
A Delta Live Table pipeline includes two datasets defined using streaming live table. Three datasets are defined against Delta Lake table sources using live table.
The table is configured to run in Production mode using the Continuous Pipeline Mode.
What is the expected outcome after clicking Start to update the pipeline assuming previously unprocessed data exists and all definitions are valid?
In Delta Live Tables (DLT), when configured to run in Continuous Pipeline Mode, particularly in a production environment, the system is designed to continuously process and update data as it becomes available. This mode keeps the compute resources active to handle ongoing data processing and automatically updates all datasets defined in the pipeline at predefined intervals. Once the pipeline is manually stopped, the compute resources are terminated to conserve resources and reduce costs. This mode is suitable for production environments where datasets need to be kept up-to-date with the latest data.
Reference: Databricks documentation on Delta Live Tables: Delta Live Tables Guide
A data engineer has been using a Databricks SQL dashboard to monitor the cleanliness of the input data to an ELT job. The ELT job has its Databricks SQL query that returns the number of input records containing unexpected NULL values. The data engineer wants their entire team to be notified via a messaging webhook whenever this value reaches 100.
Which of the following approaches can the data engineer use to notify their entire team via a messaging webhook whenever the number of NULL values reaches 100?
A webhook alert destination is a way to send notifications to external applications or services via HTTP requests. A data engineer can use a webhook alert destination to notify their entire team via a messaging webhook, such as Slack or Microsoft Teams, whenever the number of NULL values in the input data reaches 100. To set up a webhook alert destination, the data engineer needs to do the following steps:
In the Databricks SQL workspace, navigate to the Settings gear icon and select SQL Admin Console.
Click Alert Destinations and click Add New Alert Destination.
Select Webhook and enter the webhook URL and the optional custom template for the notification message.
Click Create to save the webhook alert destination.
In the Databricks SQL editor, create or open the query that returns the number of input records containing unexpected NULL values.
Click the Create Alert icon above the editor window and configure the alert criteria, such as the value column, the condition, and the threshold.
In the Notification section, select the webhook alert destination that was created earlier and click Create Alert.Reference:What are Databricks SQL alerts?,Monitor alerts,Monitoring Your Business with Alerts,Using Automation Runbook Webhooks To Alert on Databricks Status Updates.
A Delta Live Table pipeline includes two datasets defined using streaming live table. Three datasets are defined against Delta Lake table sources using live table.
The table is configured to run in Production mode using the Continuous Pipeline Mode.
What is the expected outcome after clicking Start to update the pipeline assuming previously unprocessed data exists and all definitions are valid?
In Delta Live Tables (DLT), when configured to run in Continuous Pipeline Mode, particularly in a production environment, the system is designed to continuously process and update data as it becomes available. This mode keeps the compute resources active to handle ongoing data processing and automatically updates all datasets defined in the pipeline at predefined intervals. Once the pipeline is manually stopped, the compute resources are terminated to conserve resources and reduce costs. This mode is suitable for production environments where datasets need to be kept up-to-date with the latest data.
Reference: Databricks documentation on Delta Live Tables: Delta Live Tables Guide
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?
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
Maria Lewis
3 days agoStephen Rivera
21 days agoRonald Martin
12 days agoJoshua Bell
4 days agoRachel Carter
13 hours agoElizabeth Anderson
15 days agoTamar
1 month agoClaudia
2 months agoCorrinne
2 months agoStephaine
2 months agoJina
2 months agoJavier
3 months agoAnnamae
3 months agoEvangelina
3 months agoAmira
3 months agoCarman
4 months agoCarin
4 months agoMillie
4 months agoRolande
4 months agoTeri
5 months agoSuzi
5 months agoKenda
5 months agoMarcos
5 months agoCory
6 months agoTori
6 months agoLashawnda
6 months agoLeota
6 months agoJerry
7 months agoVilma
7 months agoAlexis
7 months agoNana
7 months agoLottie
8 months agoGermaine
8 months agoTom
8 months agoDean
8 months agoFidelia
8 months agoLeah
8 months agoSerina
10 months agoCordelia
10 months agoClaudia
11 months agoAvery
11 months agoCeola
1 year agoJanella
1 year agoClarence
1 year agoVan
1 year agoLeontine
1 year agoCordie
1 year agoJudy
1 year agoLucina
1 year agoColetta
1 year agoRosalind
1 year agoMing
1 year agoFlo
1 year agoMalcom
1 year agoMargart
1 year agoSherita
1 year agoHui
1 year agoVeronica
1 year agoWayne
1 year agoLuisa
1 year agoSheridan
1 year agoBulah
2 years agoLaura
2 years agoMelvin
2 years agoBlondell
2 years agoEmily
2 years agoFelice
2 years agoToi
2 years agoWilda
2 years agoTegan
2 years agoCarolann
2 years agoRikki
2 years agoTambra
2 years agoIn
2 years agoJoaquin
2 years agoYoulanda
2 years agoShanice
2 years agoAretha
2 years agoRhea
2 years agoKandis
2 years agoKindra
2 years agoFrance
2 years agoArlene
2 years agoMoira
2 years agoDiego
2 years ago