**Transient Cluster**: Runs only during job execution; terminates when job completes. No idle time.
**When to Use**: Batch ETL, scheduled jobs, sporadic workloads. Pay only for job duration.
**Why vs. Long-Running**: Long-running = pay 24/7. Transient = pay for 2–8 hours. 60–80% cost savings for batch.
**Implementation**: Create cluster with Step; set "Action on Failure" to terminate. Cluster shuts down after last step.
**Scalability Trade-offs**: Startup time (5–10 min) adds to each run....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Persistent Systems. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.