A 311 Asset Bundle must point sandbox and production at different Unity Catalog catalogs without rewriting job logic. What should the team use?

A 311 Asset Bundle that must target different Unity Catalog catalogs for sandbox and production without rewriting job logic should use separate Asset Bundle target configurations for those environments. Bundle targets parameterize workspace and catalog bindings so the same jobs and notebooks promote cleanly: sandbox deploys resolve to the sandbox catalog, production deploys resolve to the production catalog, and transform code stays environment-agnostic. Using separate Asset Bundle variable assignments for sandbox and production Unity Catalog schemas fails because schemas live inside a catalog and do not establish the sandbox-versus-production catalog binding the question requires, so jobs would still resolve to the same catalog without separate targets. Using separate Asset Bundle deployment settings for sandbox and production Unity Catalog metastores fails because a metastore is the top-level container above catalogs, not the sandbox or production catalog itself, so metastore-level settings do not bind the bundle's jobs to different catalogs. Using separate Databricks SQL warehouse configurations for sandbox and production Unity Catalog catalogs fails because warehouses govern query execution, not Asset Bundle deployment targets or catalog binding for jobs and notebooks. Exam caveat: Asset Bundle targets are the intended multi-environment mechanism on the DP-750 deploy path—do not confuse them with ad-hoc string edits. Operational check: inspect sandbox and production target configs, deploy the same bundle revision to both, and confirm jobs bind to the correct Unity Catalog catalogs without notebook rewrites.