Reviewed by Aditya Kumar · Last reviewed 2026-03-25
**Why it matters**: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams. Databricks layers: (1) Bronzeâraw ingestion, schema on read. (2) Silverâcleaned, deduplicated, validated. (3) Goldâaggregated,...
Why it matters: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams.
Databricks layers: (1) Bronzeâraw ingestion, schema on read. (2) Silverâcleaned, deduplicated, validated. (3) Goldâaggregated, business-ready. Medallion architecture enables incremental processing, auditability, and clear ownership. Best practice: One transformation per layer; use Delta throughout; enforce schema at silver; gold for consumption; document each layer.
Scalability trade-offs: Partition/parallelism limits; single points of failure; horizontal vs vertical scaling. Cost implications: Sizing, spot vs reserved, optimization ROI.
Red Flag: Skip layers. Pro-Move: 'Bronze raw; Silver validated; Gold consumption.'
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.