Question 82

You maintain a single Databricks Asset Bundle that must deploy the same Lakeflow job to two environments that point at different all-purpose cluster IDs and different catalogs. You define a custom variable for the cluster ID and override it per target: ```yaml bundle: name: sales_pipeline variables: cluster_id: description: The all-purpose cluster used by the job default: 0000-000000-default targets: dev: default: true variables: cluster_id: 1234-567890-abcde123 prod: variables: cluster_id: 2345-678901-bcdef234 ``` In a CI pipeline you run the deploy for production as: ```bash BUNDLE_VAR_cluster_id=9999-111111-override databricks bundle deploy --target prod ``` Which `cluster_id` value does the Databricks CLI use for the production deployment, and why?

• A`2345-678901-bcdef234`, because per-target `variables` mappings always take precedence over environment variables.
• B`9999-111111-override`, because an environment variable prefixed with `BUNDLE_VAR_` has higher precedence than the value defined in the target's `variables` mapping.
• C`0000-000000-default`, because the presence of a `BUNDLE_VAR_` environment variable forces the CLI to ignore both target and command-line values and fall back to the declared default.
• DThe deploy fails with a conflict error because a variable cannot be set both in a `targets.variables` mapping and through a `BUNDLE_VAR_` environment variable.