Which features differentiate Azure Data Lake Storage Gen2 from standard Azure Blob Storage? (Select 3 answers)
- AHierarchical namespace giving atomic directory rename and delete. Correct
- BPOSIX access control lists at file and directory granularity. Correct
- CAzure Blob File System (ABFS) driver optimised for big-data analytics. Correct
- DNative NFS 3.0 protocol for Linux clients without any flag.
- ESeparate account type from Azure Blob Storage.
Why A is correct: Correct. Hierarchical namespace giving atomic directory rename and delete is one of the keyed answers. Enabling the hierarchical namespace on a Blob account turns it into ADLS Gen2 with atomic directory operations, POSIX ACLs at file and directory level, and the ABFS driver targeting the dfs.core.windows.net endpoint for Hadoop, Spark, and Presto.
Why B is correct: Correct. POSIX access control lists at file and directory granularity is one of the keyed answers. Enabling the hierarchical namespace on a Blob account turns it into ADLS Gen2 with atomic directory operations, POSIX ACLs at file and directory level, and the ABFS driver targeting the dfs.core.windows.net endpoint for Hadoop, Spark, and Presto.
Why C is correct: Correct. Azure Blob File System (ABFS) driver optimised for big-data analytics is one of the keyed answers. Enabling the hierarchical namespace on a Blob account turns it into ADLS Gen2 with atomic directory operations, POSIX ACLs at file and directory level, and the ABFS driver targeting the dfs.core.windows.net endpoint for Hadoop, Spark, and Presto.
Why D is wrong: NFS 3.0 access is a Blob Storage capability that requires explicit configuration and is not the defining ADLS Gen2 differentiator; ADLS Gen2 is distinguished by HNS, POSIX ACLs, and ABFS.
Why E is wrong: ADLS Gen2 is not a separate service or account type; it is a set of Blob Storage capabilities enabled by turning on the hierarchical namespace setting.