Home / DE Associate practice test / Implementing CI/CD / Question

Databricks Data Engineer Associate · free practice question

A data engineer is initializing a new Databricks Asset Bundle project and must create the single required root configuration file that declares the bundle name…

Exam-style question on Implementing CI/CD from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Implementing CI/CD

A data engineer is initializing a new Databricks Asset Bundle project and must create the single required root configuration file that declares the bundle name and can include additional YAML files describing the jobs and pipelines deployed to each target. What is the name of that file?

  1. Abundle.yaml placed at the project root, the manifest that names the bundle and lists the deployment targets, automatically discovered by the Databricks CLI whenever a bundle command runs from that directory.
  2. Bconfig.yml stored in a hidden .databricks directory, the file that declares the bundle name and includes the resource YAML files describing the jobs and pipelines the CLI will deploy to each target workspace.
  3. Casset-bundle.json at the project root, the descriptor holding the bundle name plus references to the additional YAML files that define the jobs and pipelines, and it is read by the CLI whenever a command executes.
  4. Ddatabricks.config.yml alongside the notebooks, the root manifest defining the bundle name and importing the other resource YAML files that specify the jobs and pipelines promoted across the deployment targets.
  5. Edatabricks.yml at the project root, the main configuration file that declares the bundle name and can include additional YAML files describing the jobs and pipelines deployed to each configured target workspace.
Answer & explanation

Correct answer: E

WHY E: The required root file of a Databricks Asset Bundle is databricks.yml, which declares the bundle name and can include other YAML files that describe resources such as jobs and pipelines. WHY NOT A: bundle.yaml is not the recognized filename; the CLI looks specifically for databricks.yml at the project root. WHY NOT B: There is no config.yml inside a .databricks directory driving the bundle; that path and name are invented. WHY NOT C: Bundles are defined in YAML, not a JSON asset-bundle.json descriptor, so this filename and format are wrong. WHY NOT D: databricks.config.yml is not the bundle root file; the single required manifest is databricks.yml.

Take the full DE Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Engineer Associate practice test. Take it and get a section-by-section score.

Start the free test →