A team's Automation Bundle has grown into a single 600-line databricks.yml: two Lakeflow Jobs, one pipeline, and per-environment overrides for dev, test, and prod all live in one file that reviewers struggle to read. The engineers want resource definitions in their own files, with each target spelling out only what differs from the root definitions. How should the bundle be restructured?

1. A. Keep everything in one databricks.yml, because the bundle specification recommends keeping all resource definitions and targets together in a single configuration file 💬 A
2. B. Move the job and pipeline definitions into resource files listed in the include mapping; targets inherit root definitions and override only what changes ✓ B
3. C. Create a separate bundle per environment, duplicating the job and pipeline definitions in each one to keep the files short 💬 C
4. D. Give up on splitting the file: a bundle cannot reference other files, so the single databricks.yml must simply be reorganized internally 💬 D

Reveal answer

Correct answer: Move the job and pipeline definitions into resource files listed in the include mapping; targets inherit root definitions and override only what changes

Reference: https://docs.databricks.com/aws/en/dev-tools/bundles/