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 to Blob: (1) Mount—dbutils.fs.mount(source='wasbs://...', mount_point='/mnt/mymount'); (2) Service principal or SAS; (3)...
Why it matters: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams.
Databricks to Blob: (1) Mount—dbutils.fs.mount(source='wasbs://...', mount_point='/mnt/mymount'); (2) Service principal or SAS; (3) Access: spark.read.parquet('/mnt/mymount/path'). Or use spark.conf for account key. Best practice: use service principal; secure credentials in Secrets; use mount for convenience; validate access.
Scalability trade-offs: Partition/parallelism limits; single points of failure; horizontal vs vertical scaling. Cost implications: Sizing, spot vs reserved, optimization ROI.
Red Flag: Credentials in notebook. Pro-Move: 'Service principal; Secrets; mount for convenience.'
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.