Databricks Data Engineer Professional · Free practice question 8 of 12
Bundle generate and deployment bind
Ludgate Analytics has a production job that was built in the UI, and it now wants to manage the job in a Declarative Automation Bundle (formerly called a Databricks Asset Bundle) without creating a duplicate job. Which approach fits?
- A.Use databricks bundle generate job with the existing job ID to create the configuration, then link the bundle resource to the existing job with databricks bundle deployment bind
- B.Export the job JSON and paste it into databricks.yml as a new job, then delete the original after the first deployment
- C.Run databricks bundle destroy and recreate the job from the bundle
- D.Clone the job in the UI and point the clone at the bundle folder
Show answer and explanation
Correct answer: A. Use databricks bundle generate job with the existing job ID to create the configuration, then link the bundle resource to the existing job with databricks bundle deployment bind
Why: bundle generate creates bundle configuration, and downloads referenced notebooks, from an existing job or pipeline, and bundle deployment bind links a bundle resource to that existing workspace object, so the next deployment updates it in place instead of creating a duplicate. Pasting definitions creates a new job with a new ID and run history, and destroying or cloning the job loses its continuity.
More free Databricks Data Engineer Professional questions
- Databricks SQL alerts with notifications
- Partitioning guidance for mid-size tables
- VACUUM retention duration safety check
- SQL warehouse sizing versus scaling
- BROWSE privilege for data discovery
- UNDROP TABLE for managed tables
- Workspace-catalog binding isolation
- Driver memory and toPandas
- Continuous job trigger for streaming
- Table update triggers for jobs
- Serverless environment dependencies