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 notebook permissions: Workspace, right-click notebook, Permissions. Add user/group with Can View, Can Run, Can Edit, or Can...
Why it matters: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams.
Databricks notebook permissions: Workspace, right-click notebook, Permissions. Add user/group with Can View, Can Run, Can Edit, or Can Manage. Use folders for bulk permissions. Best practice: use groups (not individual users); follow least privilege; separate dev/prod; use Repos for version control and CI/CD.
Scalability trade-offs: Partition/parallelism limits; single points of failure; horizontal vs vertical scaling. Cost implications: Sizing, spot vs reserved, optimization ROI.
Red Flag: Individual user permissions. Pro-Move: 'Groups; least privilege; Repos CI/CD.'
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.