Databricks Data Engineer Associate · Free practice question 7 of 12
Job task timeout setting
A task in a job at Lochby Analytics sometimes hangs indefinitely while waiting on an external system. The team wants the task stopped and treated as failed if it runs for longer than 45 minutes. What should they configure?
- A.A retry policy with a 45-minute interval between retries
- B.A cron schedule that starts the job every 45 minutes
- C.A timeout of 45 minutes on the task
- D.An expectation with ON VIOLATION FAIL UPDATE
Show answer and explanation
Correct answer: C. A timeout of 45 minutes on the task
Why: A task timeout sets the maximum time a task may run; when it is exceeded, the task is terminated and its run is marked as timed out rather than succeeded. A retry interval controls the wait between attempts, a schedule controls how often the job starts, and expectations validate data in declarative pipelines rather than limiting task duration.
More free Databricks Data Engineer Associate questions
- Delta shallow vs deep clone
- Auto Loader schema hints
- Reading notebook task parameters
- collect_set vs collect_list aggregation
- Triggered vs continuous pipeline mode
- Job maximum concurrent runs
- SHOW GRANTS on Unity Catalog objects
- Transferring object ownership
- Compute policies for cluster governance
- ALTER TABLE ADD COLUMNS on Delta
- Spark lazy evaluation transformations vs actions