Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Job Clusters**: Run single workload; terminate when done. Cost-effective for batch ETL, scheduled jobs. Spin up, run, shut down. **Interactive**: Stay alive for ad-hoc queries, notebooks. Used by analysts. Use auto-termination (e.g., 30 min idle) to control cost. **Cost**:...
Job Clusters: Run single workload; terminate when done. Cost-effective for batch ETL, scheduled jobs. Spin up, run, shut down.
Interactive: Stay alive for ad-hoc queries, notebooks. Used by analysts. Use auto-termination (e.g., 30 min idle) to control cost.
Cost: Job = pay per run; interactive = pay for idle. Pool clusters for faster startup with many short jobs. At scale: Job for production; Interactive with strict idle timeout.
Pro-Move: 'We use pool clusters for job workloads—startup time dropped from 5 min to 30 sec.'
According to DataEngPrep.tech, this is one of the most frequently asked General/Other interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.