Question 240
A bundle deployment works in development but sends its production job to the dev catalog. The team deploys with `databricks bundle deploy --target prod`. How should the team correct this issue while preserving the required data contract?
Explanation
Correct Answer
Use target-specific bundle variable overrides and verify deployment resource resolution. This is the most directly relevant remediation because a default catalog value can leak into production without environment-specific configuration. A concrete acceptance check is: Bundle validation and a smoke run reference only the intended production catalog. To reduce recurrence: Review resolved bundle settings before release.
Incorrect Answers
Syntactic merge success does not prove intended data processing order. For the observed behavior, a default catalog value can leak into production without environment-specific configuration.
Checkpoints preserve incremental progress and state across cluster changes. Here the important technical distinction is that a default catalog value can leak into production without environment-specific configuration.
Runtime parameter overrides can redirect side effects even when job code is unchanged. The reported failure instead depends on this fact: a default catalog value can leak into production without environment-specific configuration.