**Managed**: Engine owns data. DROP TABLE deletes data. Default CREATE TABLE.
**External**: Data in external location (S3, HDFS). DROP TABLE removes only metadata. CREATE EXTERNAL TABLE ... LOCATION.
**When Which**: Managed for engine-controlled, transient. External for data lakes, multi-engine, retention.
**Scalability Trade-offs**: Same. Choice is governance and lifecycle.
**Cost Implications**: External = data survives table drop. Managed = clean drop....
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 Infosys. 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.