Describe core data concepts →mediumMultiple ChoiceObjective-mapped

DP-900 Describe core data concepts Practice Question

Exhibit

Refer to the exhibit.
{
  "type": "Microsoft.Storage/storageAccounts",
  "apiVersion": "2023-01-01",
  "name": "[parameters('storageAccountName')]",
  "location": "[parameters('location')]",
  "sku": {
    "name": "Standard_LRS"
  },
  "kind": "StorageV2",
  "properties": {
    "minimumTlsVersion": "1.2",
    "supportsHttpsTrafficOnly": true
  }
}

Refer to the exhibit. You are reviewing an ARM template for a new storage account. The storage account will store data that must be accessible from any Azure region and must be highly durable. Which change should you make to the template?

⚠ Common exam trap

Microsoft often tests the misconception that changing the 'kind' (e.g., to BlobStorage) or disabling HTTPS affects durability or geo-accessibility, when in fact only the SKU name (replication strategy) controls these properties, and candidates confuse security settings with replication settings.

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

✓

Change the SKU name to Standard_GRS

Standard_GRS (Geo-Redundant Storage) is the correct SKU because it replicates data synchronously three times within a primary region and asynchronously to a secondary region hundreds of miles away, ensuring high durability (11 nines) and accessibility from any Azure region via read-access (RA-GRS). The requirement for data to be accessible from any Azure region and highly durable aligns with GRS's geo-replication, whereas LRS only replicates within a single datacenter and Premium_LRS is for low-latency workloads, not geo-accessibility.

Answer analysis

Option-by-option breakdown

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

✗
Set supportsHttpsTrafficOnly to false
Why it's wrong here
Setting supportsHttpsTrafficOnly to false disables the requirement for secure HTTPS connections, which exposes data to interception but does not alter how or where storage replicates data. Azure's data durability depends on the SKU's replication setting, not on transport encryption. Therefore this change would reduce security and fail to address the goal of improving cross-region durability.
✗
Change the SKU name to Premium_LRS
Why it's wrong here
Premium_LRS is a performance-tier SKU that delivers low-latency performance using solid-state drives, but it uses locally redundant storage, meaning copies are kept only within a single data center or region. It cannot provide geo-replication because Premium performance tiers are limited to LRS and do not support cross-region copies. Thus it is incorrect because the requirement is about durability across regions, not latency.
✓
Change the SKU name to Standard_GRS
Why this is correct
Changing the SKU name to Standard_GRS switches the storage account to geo-redundant storage, which synchronously copies your data three times within the primary region and then asynchronously copies it to a paired secondary region. If the primary region becomes unavailable, Azure can fail over to the secondary copy, so data survives a regional outage. This directly meets the ARM template requirement for higher durability across regions.
✗
Change the kind to BlobStorage
Why it's wrong here
Changing the kind to BlobStorage would convert the account to a legacy blob-only storage type that does not support tables, queues, or files, and it leaves the replication setting unchanged. The storage account kind determines which services and features are available, while replication is controlled separately by the SKU. Since BlobStorage still defaults to the same SKU-based replication, this option does not improve durability across regions.

Go deeper

DP-900 Describe core data concepts Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question