Home / DE Associate practice test / Working with Lakeflow Jobs / Question

Databricks Data Engineer Associate · free practice question

A task occasionally fails due to a transient network timeout when calling an external API, but succeeds when re-run. Without adding external tooling, what is…

Exam-style question on Working with Lakeflow Jobs from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Working with Lakeflow Jobs

A task occasionally fails due to a transient network timeout when calling an external API, but succeeds when re-run. Without adding external tooling, what is the appropriate Lakeflow Jobs configuration to make the pipeline resilient to these intermittent failures?

  1. AIncrease the cluster size and the memory allocated to the task; the extra compute headroom then keeps the external service's network timeouts from occurring during the API call.
  2. BSet the task's run-if condition to ALL_DONE; the task then disregards upstream failures and reports a successful run, which keeps the transient network timeout from surfacing as an error.
  3. CSplit the task into ten identical parallel copies that run at the same time; the job then keeps the output of whichever copy succeeds and discards the outputs of the copies that time out.
  4. DDisable the task's checkpoint; on an error the task then restarts from the beginning on its next scheduled run, which gives the external API call a fresh state on each execution.
  5. EConfigure a retry policy on the task with a maximum number of retries and a retry interval; Lakeflow Jobs then re-runs the failed task until it succeeds or reaches the configured limit.
Answer & explanation

Correct answer: E

WHY E: A task retry policy re-runs the task automatically up to a configured limit with a set interval. It is the built-in mechanism for transient, self-resolving failures.

WHY NOT B: ALL_DONE is a run-if condition that controls whether a task runs after its upstream tasks finish; it does not retry the failing task, and masking a failure as success is wrong.

WHY NOT C: Running ten copies is wasteful, repeats the external API call ten times, and is not how job resilience is configured.

WHY NOT D: Checkpoints aid recovery; disabling them harms resilience rather than helping it, and nothing here re-runs the task within the same job run.

WHY NOT A: A larger cluster does not prevent an external service's network timeouts.

Take the full DE Associate practice test free →

Would you pass today?

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

Start the free test →