Question 33
Domain 9: Debugging and DeployingWhy should a Databricks Asset Bundle define targets such as dev, staging, and prod in the same bundle?
Correct answer: A
Explanation
Databricks Asset Bundles use targets to let one bundle hold multiple environment configurations, so settings like cluster size, paths, or permissions can differ by environment. This avoids duplicating the entire project definition while still allowing "dev, staging, and prod" to be managed from the same bundle.
Why each option is right or wrong
A. So environment-specific settings can vary without duplicating the whole project definition
Databricks Asset Bundles support multiple deployment targets within a single bundle so the same project definition can be reused while overriding only environment-specific values such as workspace paths, cluster/job settings, variables, and permissions. In practice, this lets a bundle keep one canonical configuration and apply different target-specific settings for dev, staging, and prod instead of maintaining separate copies of the entire project.
B. So the same resource names are guaranteed to overwrite each other across all workspaces
Targets separate environment deployments; they do not exist to force cross-workspace overwrites of resource names.
C. Because targets automatically grant admin privileges in production
Targets describe deployment environments, not automatic privilege escalation or production admin access.
D. Because a bundle can only contain one job per target
A target is an environment configuration scope, not a one-job limit for bundle contents.