Databricks Certified Data Engineer Associate free question 8 / 10 · Domain 5: Implementing CI/CD
In Declarative Automation Bundles (formerly Databricks Asset Bundles), you wrote mode: development for the target dev, and wrote only the single line trigger_pause_status: UNPAUSED under presets of the same target. The definition of the job daily_sales has a schedule for 6:00 every morning and no pause_status. What happens to daily_sales when you deploy with databricks bundle deploy -t dev?
- The schedule stays paused, and [dev username] is prefixed to the job name
- The schedule stays paused, and nothing is prefixed to the job name
- The job runs on its schedule, and [dev username] is prefixed to the job name
- The job runs on its schedule, and nothing is prefixed to the job name
Show the answer and explanation
Answer: A
Why this is correct
Deploying with mode: development puts [dev username] at the start of resource names and pauses schedules and triggers. Many presets take precedence over the defaults of mode, but the configuration reference says of trigger_pause_status: "If mode is set to development, trigger_pause_status is always PAUSED." The schedule stays paused even if you write UNPAUSED. The name prefix was not changed in presets, so it is added by the development mode default.
Why the other options are wrong
"The job runs on its schedule, and [dev username] is prefixed to the job name" … The name prefix is right, but the schedule is wrong. The presets table of the configuration reference says that when mode is development, trigger_pause_status is always PAUSED. Even if you write UNPAUSED in presets, the deployed schedule is paused.
"The job runs on its schedule, and nothing is prefixed to the job name" … In development mode, the schedule is paused even if you write UNPAUSED in presets. The name prefix is also not changed by presets, so [dev username] is added as the development mode default.
"The schedule stays paused, and nothing is prefixed to the job name" … It is right that the schedule is paused. But what you wrote in presets is only trigger_pause_status, and the name prefix was not changed. As the development mode default, [dev username] is added to the names of deployed resources.
Key point
The deployment modes page says that when you write both mode and presets, presets take precedence over the defaults of mode, but it qualifies this with "Unless an exception is specified for a preset." Check the behavior of each preset in the presets table of the configuration reference.