**Elastic Resize**: Add/remove nodes same type; data stays in place via leader node redistribution; ~2–5 min; no data copy. **Classic Resize**: Change node type or count; full data redistribution; hours for large clusters. **Why Elastic**: Quick scale for concurrency (e.g., holiday); same node type required. **Why Classic**: Migrate dc2 → ra3 (managed storage); major capacity change. **Scalability**: Elastic limited to 2× nodes; Classic supports full resize....
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 Capco. 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 SQL 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.