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

Databricks Data Engineer Associate · free practice question

A team runs a nightly scheduled Lakeflow Job in production. It is currently attached to a shared all-purpose cluster that several analysts also use…

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 team runs a nightly scheduled Lakeflow Job in production. It is currently attached to a shared all-purpose cluster that several analysts also use interactively during the day. The team wants to lower cost and improve isolation for the scheduled run. Which change best meets both goals?

  1. AKeep the all-purpose cluster but let it autoscale to zero workers overnight, because an all-purpose cluster billed at interactive DBU rates becomes the cheapest available option once its worker count scales to a minimum.
  2. BMove the job to a serverless SQL warehouse, because a SQL warehouse can execute the notebook and Python tasks in this job while delivering the fastest startup and the lowest cost for scheduled production workloads.
  3. CLeave the shared all-purpose cluster in place and raise its maximum concurrency, since isolating a scheduled job from interactive analysts is achieved by increasing the cluster's number of allowed parallel tasks.
  4. DConfigure the job to use a job cluster that is created when the run starts and terminated automatically when it finishes, giving the scheduled run isolated and cheaper compute than the shared all-purpose cluster does.
  5. ESwitch the job to a continuous trigger on the same all-purpose cluster, because keeping the cluster permanently running removes provisioning warm-up and is therefore the most cost-efficient pattern for a nightly job.
Answer & explanation

Correct answer: D

WHY D: A job cluster is provisioned for the run and terminated when it finishes, so it is cheaper than an always-on all-purpose cluster and isolates the scheduled run from interactive users. WHY NOT A: An all-purpose cluster is billed at interactive rates and stays configured for shared use; it is not the cost-optimal choice for a scheduled job even when scaled down. WHY NOT B: A serverless SQL warehouse runs SQL only and cannot execute Python or notebook tasks, so it cannot host this job. WHY NOT C: Raising concurrency shares the cluster more, not less; it does not isolate the job and does not reduce cost. WHY NOT E: A continuous trigger keeps compute running constantly, which increases cost rather than reducing it for a once-nightly job.

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 →