Assuming previously unprocessed data exists and all definitions are valid, what is the expected outcome after clicking Start to update the pipeline?

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.

Assuming previously unprocessed data exists and all definitions are valid, what is the expected outcome after clicking Start to update the pipeline?
A . All datasets will be updated at set intervals until the pipeline is shut down. The compute resources will persist to allow for additional testing.
B . All datasets will be updated once and the pipeline will persist without any processing. The compute resources will persist but go unused.
C . All datasets will be updated at set intervals until the pipeline is shut down. The compute resources will be deployed for the update and terminated when the pipeline is stopped.
D . All datasets will be updated once and the pipeline will shut down. The compute resources will be terminated.
E . All datasets will be updated once and the pipeline will shut down. The compute resources will persist to allow for additional testing.

Answer: C

Explanation:

: In Production mode, the pipeline runs continuously and updates the output tables whenever new data is available in the input sources. The compute resources are allocated on demand and released when the pipeline is stopped. This mode is suitable for production workloads that require high availability and reliability.

Reference: Configure pipeline settings for Delta Live Tables, Tutorial: Run your first Delta Live Tables pipeline, Building Reliable Data Pipelines Using DataBricks’ Delta Live Tables

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments