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

Databricks Data Engineer Associate · free practice question

A single Automation Bundle (formerly Databricks Asset Bundles) must deploy the same job to dev, staging, and prod, each using a different Unity Catalog catalog…

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 single Automation Bundle (formerly Databricks Asset Bundles) must deploy the same job to dev, staging, and prod, each using a different Unity Catalog catalog and cluster size, without duplicating the entire job definition per environment. Which bundle mechanism achieves this?

  1. ACopy the full job YAML three times, one file per environment, hardcoding each catalog and cluster size, then deploy dev, staging, and prod separately from their own independent job definition files.
  2. BHardcode the production catalog and cluster size in the single job definition, then manually edit those values back and forth each time you need to deploy to the dev or the staging environment instead.
  3. CDefine the job once using ${var.catalog} and ${var.workers} placeholders and override only those variables per target in databricks.yml, so a single definition promotes across all environments.
  4. DStore each environment's catalog and cluster values in DBFS and read them at deploy time with a shell script, because Automation Bundles cannot parameterize their resources per deployment target.
  5. EUse three separate Git repositories, one for each environment, each holding its own copy of the bundle with the catalog and cluster size baked in, and deploy each repository on its own to its target.
Answer & explanation

Correct answer: C

WHY C: Automation Bundles support variable substitution with per-target overrides — the job is defined once with ${var.*} placeholders and each targets block sets only the differing values, so a single definition promotes across dev/staging/prod. WHY NOT A: Duplicating the YAML per environment defeats the purpose and drifts over time. WHY NOT B: Manual editing of hardcoded values is error-prone and not reproducible. WHY NOT D: Bundles natively parameterize targets, so a DBFS/shell workaround is unnecessary and false. WHY NOT E: Separate repos per environment duplicate the bundle and cause drift, the opposite of a single promotable definition.

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 →