Azure Data Lake Storage Gen2: Hierarchical, ACLs & POSIX
Enterprise data lake with hierarchical namespace, POSIX ACLs, and high-performance analytics capabilities
ADLS Gen2 Architecture
ACL Configuration
Interview Questions
Q1: Explain the difference between POSIX ACLs and Azure RBAC for ADLS Gen2. A: POSIX ACLs provide file/directory-level permissions with fine-grained control (user, group, mask, other). Azure RBAC provides role-based access at the storage account, container, or directory level. Use POSIX for data lake workloads; RBAC for administrative access.
Q2: How do you implement a data lake zone architecture in ADLS Gen2? A: Create separate containers or directories for each zone (raw, curated, sandbox). Use lifecycle management to tier data. Implement ACLs per zone. Use Delta Lake format in curated zone for ACID transactions.
Q3: What are the performance best practices for ADLS Gen2? A: 1) Use hierarchical namespace for directory operations, 2) Avoid too many small files (aim for 1GB+ per file), 3) Use partitioning for query patterns, 4) Enable ADLS Gen2 API for Hadoop compatibility, 5) Use Parallel File System Operations for bulk uploads.