Data Engineering Associate with Databricks Practice Exam

What is a key limitation of using versioned notebooks compared to using Repos in Databricks?

1. Notebooks version control is always visible

2. Versioned notebooks can be easily audited

3. Notebooks version is lost upon deletion or export

4. Versioned notebooks support collaboration

The correct answer is: Notebooks version is lost upon deletion or export

Using versioned notebooks in Databricks has certain limitations compared to using Repos, and one significant limitation is that the version of a notebook can be lost if it is deleted or exported. When working with versioned notebooks, if a user deletes a notebook, regardless of the version history, once it is gone, that specific version and its contents cannot be recovered. In contrast, Repos provide a more robust version control mechanism similar to traditional version control systems, allowing for easier recovery of code and history through Git integration. Versioned notebooks are intended for ease of use within the Databricks environment but do not have the same level of persistence in version history that traditional version control systems offer. While auditing features and collaboration are enhanced in Repos, and the versioning aspect of notebooks can be insightful, they still lack the permanence found in repository systems where version history persists even after files are deleted or exported. This characteristic highlights the fragility inherent in using versioned notebooks, reinforcing the importance of understanding the appropriate context and tools for managing code versioning effectively.