Home / DE Professional practice test / Debugging and Deploying / Question

Databricks Data Engineer Professional · free practice question

A Databricks job run fails because a job parameter `--env` was mistakenly set to `staging` when the code requires `production` to connect to the correct data…

Exam-style question on Debugging and Deploying from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Debugging and Deploying Easy

A Databricks job run fails because a job parameter --env was mistakenly set to staging when the code requires production to connect to the correct data source. The engineer needs to re-run only the failed tasks using --env=production, WITHOUT permanently modifying the original job definition. What is the CORRECT approach?

  1. AEdit the job definition to change the default value of --env to production, then trigger a new full run of the job.
  2. BClone the job, set --env to production in the cloned copy, run the clone once, and then delete the clone afterwards.
  3. CIn the Repair job run dialog, override --env to production for that repair run, leaving the job definition unchanged.
  4. DCancel the failed run, then submit a new run through the Jobs REST API run-now call with --env set to production.
Answer & explanation

Correct answer: C

WHY C: The Repair job run dialog in the Databricks UI supports parameter overrides for the repair run. When initiating a repair, engineers can add or change task parameters and job-level parameters that apply only to the repair execution; the original job definition remains unchanged. This is the designed workflow for remediating a failed run caused by a bad parameter value while preserving the job's original configuration and the results of tasks that already completed successfully.

WHY NOT A: Editing the job definition changes the permanent default parameter, which would affect future runs. It also requires triggering a completely new run from scratch, re-executing tasks that may have already completed successfully, which wastes compute and loses the efficiency benefit of the repair run mechanism.

WHY NOT B: Cloning the job is an unnecessarily complex workaround. It requires cleanup after the fact, does not use the built-in repair run functionality, and triggers a full new run that re-executes every task (including tasks that already succeeded) rather than just the failed ones.

WHY NOT D: Submitting a new run via the API with the corrected parameter is a valid workaround but creates an entirely new run rather than repairing the original. This wastes compute by re-running successful tasks and creates an additional run record, complicating run history tracking. It also does not preserve the original run's context for audit purposes.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →