Question 740
A bundle deployment works in development but sends its production job to the dev catalog. The team deploys with `databricks bundle deploy --target prod`. What platform behavior caused the observed result?
Explanation
Correct Answer
A default catalog value can leak into production without environment-specific configuration. This is the most directly relevant technical explanation 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
A Git commit persists secrets beyond the intended live environment. Here the important technical distinction is that a default catalog value can leak into production without environment-specific configuration.
Repair-run overrides are not equivalent to changing the stored job definition. The reported failure instead depends on this fact: a default catalog value can leak into production without environment-specific configuration.
Pipeline completion and workflow dependency availability are distinct operational events. In this situation, a default catalog value can leak into production without environment-specific configuration.