Question 32
Domain 9: Debugging and DeployingYou want a bundle deployment to manage an already existing Databricks job instead of creating a duplicate job. What should you do?
Correct answer: A
Explanation
A bundle can manage an existing Databricks job by binding the bundle resource to that job instead of creating a new one. The deployment command is "databricks bundle deployment bind," which associates the bundle configuration with the existing resource so future deployments target it rather than duplicating it.
Why each option is right or wrong
A. Generate bundle configuration for the existing resource and use databricks bundle deployment bind
Databricks Bundles support adopting an already-created resource by binding the bundle’s declared resource to the existing job during deployment, rather than letting the deploy step create a second job. The relevant command is `databricks bundle deployment bind`, which attaches the bundle resource to the preexisting Databricks job so subsequent bundle deployments operate on that same job instead of duplicating it.
B. Rename the existing job to match the bundle name and hope Databricks merges them
Matching names does not reliably establish resource ownership or deployment state.
C. Delete the existing job and rebuild it manually in production first
Deleting production resources is unnecessary when the goal is to bring them under bundle management.
D. Move the job definition into a notebook comment block
Notebook comments are documentation only and do not define deployable bundle resources.