Free Databricks Databricks-Certified-Data-Engineer-Associate Practice Exam with Questions & Answers | Set: 4

Databricks Asset Bundles are a Databricks CLI feature that lets teams define Databricks projects “as code” using YAML configuration files . In a bundle, metadata is expressed in YAML (for example, a required databricks.yml at the root), and the configuration can declare resources (such as Databricks Jobs/workflows and other supported assets), artifacts , and deployment targets . After defining these YAML manifests, teams use the Databricks CLI to validate, deploy, and run the bundle into a Databricks workspace, which matches the scenario described (YAML + CLI deployment). This approach standardizes how workflows and related resources are packaged and promoted across environments (dev/test/prod) while keeping definitions version-controlled and reproducible. GitHub is only a hosting/version-control platform (not the YAML deployment feature itself), Terraform is a separate IaC tool, and “DataOps” is a methodology rather than a specific Databricks feature. ( Databricks Documentation )

Databricks documentation for Unity Catalog lineage states that lineage is captured across queries run on Databricks , is supported for all languages , and is tracked down to the column level . It also explicitly says that lineage data includes related notebooks, jobs, and dashboards , and that the lineage can be visualized in Catalog Explorer in near real time as an interactive graph. This directly matches option D. The value of this feature is that it helps engineers understand where a table’s data came from, which upstream notebooks or jobs produced it, and which downstream assets, including dashboards, depend on it. Column-level lineage adds another layer of traceability by showing how specific fields are derived through transformations, which is especially useful for impact analysis, governance, and troubleshooting. Options A, B, and C each remove documented capabilities that Unity Catalog lineage actually supports. Therefore, the Databricks-documented answer is the full interactive graph across Delta tables and related assets, with column-level tracking included.

=========

databricks bundle validate should be run first because it checks whether the bundle configuration files are syntactically valid and reports configuration warnings. After validation succeeds, databricks bundle deploy creates or updates the bundle-defined resources and uploads the required artifacts to the selected workspace target. The final command, databricks bundle run, starts a deployed job or Lakeflow pipeline by using its resource key. bundle init creates a new project from a template and is not the validation step for an already developed bundle. bundle sync synchronizes files for development workflows but does not replace a complete deployment. The commands bundle execute, bundle check, bundle upload, and bundle start are not the appropriate command sequence. Therefore, option B is correct.

A data lakehouse is a data management architecture that combines the flexibility, cost-efficiency, and scale of data lakes with the data management and ACID transactions of data warehouses, enabling business intelligence (BI) and machine learning (ML) on all data12. One of the key features of a data lakehouse is that it supports ACID-compliant transactions, which means that it ensures data integrity, consistency, and isolation across concurrent read and write operations3. This feature results in improved data quality over a traditional data lake, which does not support transactions and may suffer from data corruption, duplication, or inconsistency due to concurrent or streaming data ingestion and processing . References: 1: What is a Data Lakehouse? - Databricks 2: What is a Data Lakehouse? Definition, features & benefits. - Qlik 3: ACID Transactions - Databricks : [Data Lake vs Data Warehouse: Key Differences] : [Data Lakehouse: The Future of Data Engineering]

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. References: Workspace access control, Manage Unity Catalog object ownership.

Databricks Asset Bundles use YAML configuration, and Databricks documentation specifies that bundle configuration is expressed in a root databricks.yml file. The resources mapping is used to define supported objects such as jobs , and job definitions include keys like name and tasks. Tasks in a job are defined under the tasks key, and a notebook task is represented with notebook_task and notebook_path. Option A is the only answer written in the correct general YAML bundle structure and matches the documented style of defining bundle resources. Options B and C use JSON- and Python-style syntax rather than bundle YAML. Option D uses Terraform/HCL-style syntax, which is not the Databricks Asset Bundle format. While a full production bundle often includes more top-level settings such as bundle, targets, or workspace, the question asks which format is valid, and only option A matches the documented Databricks Asset Bundles configuration model.

=========