A Databricks workspace team is choosing a CI/CD strategy. Option 1 is to use a production Git folder (updated via the Repos API on PR merge) to deploy notebook code into the workspace. Option 2 is to use Databricks Asset Bundles to define jobs, pipelines, and infrastructure in version-controlled YAML files and deploy them via the CLI. What does Databricks RECOMMEND as the primary CI/CD approach?
Answer & explanation
Correct answer: A
WHY A: Databricks documentation explicitly states: 'Databricks recommends Databricks Asset Bundles to package and deploy CI/CD workflows.' Bundles provide a full infrastructure-as-code approach covering jobs, pipelines, ML endpoints, and MLflow resources defined in YAML and deployed via the CLI. The documentation also notes that bundles and Git folders are complementary: you can 'Define resources such as jobs and pipelines in source using bundles, then create, deploy, and manage them in workspace Git folders'. Production Git folders remain a valid option when deploying only source code into the workspace, but bundles are the primary recommended strategy.
WHY NOT B: Production Git folders are a supported pattern for code-only deployments, but the documentation describes them as the alternative ('If you prefer to deploy only code into the workspace, you can use a production Git folder instead'), not the recommended primary approach. Git folders track code files (notebooks, Python scripts) but do not natively manage resource definitions such as job schedules, cluster configurations, or pipeline settings as first-class versioned objects the way bundles do.
WHY NOT C: Calling the Jobs REST API directly is a valid low-level approach, but it requires custom scripting for every resource type and lifecycle operation (create, update, delete, run). Databricks does not recommend it as the primary CI/CD mechanism; it recommends the higher-level abstraction of bundles, which wraps the REST API in a structured, validatable, version-controlled format.
WHY NOT D: Databricks does not recommend or document a split toolchain of Git folders for notebooks and bundles for everything else. The documented recommendation is bundles as the unified CI/CD tool for all resource types, with Git folders as a complementary code hosting mechanism within the workspace if desired.