Describe core data concepts →easyMultiple ChoiceObjective-mapped

DP-900 Describe core data concepts Practice Question

Exhibit

{
  "identity": {
    "type": "UserAssigned",
    "userAssignedIdentities": {
      "/subscriptions/12345/resourceGroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/id1": {}
    }
  },
  "properties": {
    "isHnsEnabled": true,
    "encryption": {
      "keySource": "Microsoft.Storage"
    }
  }
}

Refer to the exhibit. You are deploying an Azure Storage account. The JSON snippet represents a template parameter. What does the 'isHnsEnabled' property enable?

⚠ Common exam trap

Many candidates confuse 'isHnsEnabled' with blob-level features like versioning or soft delete, because all three are related to data management, but only the hierarchical namespace fundamentally changes the storage account's architecture to support file system semantics.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Hierarchical namespace for the storage account

The 'isHnsEnabled' property enables the hierarchical namespace for the storage account, which is a core feature of Azure Data Lake Storage Gen2. When set to true, it allows the storage account to organize blobs into a directory hierarchy, enabling POSIX-like access control lists (ACLs) and file system semantics. This is essential for big data analytics workloads that require a file system structure rather than a flat blob storage model.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Blob versioning
Why it's wrong here
Blob versioning preserves a history of blob states so you can restore earlier copies if files are overwritten or corrupted, but it is a data-protection setting toggled on the storage account after deployment, not a property set at creation. It does not alter the fundamental storage architecture or any Data Lake capabilities, and it is controlled by the account's 'Data Protection' blade and the Microsoft.Storage APIs, making it unrelated to the question.
✗
Soft delete for blobs
Why it's wrong here
Soft delete for blobs is a post-deployment data recovery mechanism that retains deleted blobs for a configurable retention period, letting you recover them after accidental deletion. It is enabled through the storage account's data protection settings, not through properties declared during provisioning. This feature is independent of the account's namespace and replication, so although it is valuable, it is not the deployment-time attribute that determines the account's base functionality.
✗
Geo-redundant storage
Why it's wrong here
Geo-redundant storage (GRS) defines the replication scope, ensuring your data is synchronously copied to a secondary region for disaster recovery, but this is decided by the storage account's SKU, such as Standard_GRS or Premium_LRS. The SKU must be selected when creating the account, yet it is a performance and availability choice, not a feature that enables hierarchical folders or ADLS Gen2 semantics. Therefore, it fails as the correct answer because it does not affect how the namespace is organized.
✓
Hierarchical namespace for the storage account
Why this is correct
The hierarchical namespace is a creation-time flag that organizes blobs into directories and nested folder structures, enabling Azure Data Lake Storage Gen2 features like POSIX-like ACLs, atomic directory renames, and higher-throughput analytics workloads. This property cannot be changed after the storage account is provisioned, so it must be set during deployment. Unlike versioning or soft delete, which are optional post-creation protections, this namespace fundamentally changes the account's data model, making it the correct capability referenced in the exhibit.

Visual reference

Go deeper

DP-900 Describe core data concepts Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question