A team owns one ETL codebase that runs in dev, test, and prod workspaces, and each workspace uses a different SQL warehouse for the job's SQL tasks. The bundle's task references a variable wherever the warehouse is used: ```yaml resources: jobs: nightly_orders: tasks: - task_key: load sql_task: warehouse_id: ${var.warehouse_id} ``` The rest of the bundle defines the variable and the targets (the test target follows the same pattern as prod): ```yaml variables: warehouse_id: default: "9d4e8f1a2b6c" description: SQL warehouse to use for SQL tasks targets: dev: default: true prod: variables: warehouse_id: "e2f1c9d4a7b3" ``` How does this design serve three environments from a single codebase?

1. A. Every databricks bundle deploy pauses and prompts the engineer to type the warehouse ID for the target being deployed 💬 A
2. B. The variable is resolved when the job runs, reading the correct warehouse from each workspace's environment configuration 💬 B
3. C. The team maintains three copies of this bundle, each hardcoding its own warehouse_id, and deploys the copy that matches the environment 💬 C
4. D. Variables resolve per target at deploy time — dev uses the default, prod uses its override, resources stay identical ✓ D

Reveal answer

Correct answer: Variables resolve per target at deploy time — dev uses the default, prod uses its override, resources stay identical

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