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?
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.