Study Databricks DE-PRO Asset Bundles and CI/CD: key concepts, common traps, and exam decision cues.
Deployment questions become easier when you separate source control from deployment packaging. Databricks treats both as important, but they are not the same tool.
| Requirement | Better first instinct |
|---|---|
| package and deploy Databricks resources across environments | Databricks Asset Bundles |
| keep workspace source integrated with Git workflows | Git folders |
| build repeatable CI/CD flow | combine explicit package structure with promotion-aware automation |
| Concern | Stronger first tool |
|---|---|
| source integration and collaborative development | Git folders |
| target-aware packaging and deployment | Asset Bundles |
| repeatable environment promotion | CI/CD flow built around explicit package structure |
This split is the core of the lesson.
| If the stem says… | Strong reading |
|---|---|
| “build and deploy Databricks resources” | Asset Bundles |
| “integrate with Git-based CI/CD workflows” | Git folders plus deployment workflow, not Git alone |
| “notebook and code deployment” | separate authoring workflow from promotion mechanics |
Bundles are not just another way to store source. They answer deployment questions like:
If the answer stops at “put it in Git,” it is usually incomplete for DE-PRO.
| Trap | Better rule |
|---|---|
| treating Git folders as a deployment package | they are source integration, not the whole promotion story |
| treating bundles as just source control | bundles are packaging and target-aware deployment |
| hard-coding environment differences | professional promotion paths should be explicit and repeatable |
| Scenario clue | Stronger answer shape |
|---|---|
| “package and deploy resources across environments” | Asset Bundles |
| “developers need Git-linked workspace source” | Git folders |
| “same code must promote with explicit target differences” | Bundles plus CI/CD |
| “question is about deployment, not version history” | do not stop at Git alone |
Deployment questions usually test whether Git integration is enough by itself. Git folders help source integration, but repeatable multi-environment deployment points to Asset Bundles and a real promotion design. DE-PRO tends to reward packaging and target-aware deployment flow over “it lives in Git, so deployment is solved.”