Secure, monitor, and optimize data storage and data processing →hardMultiple Choice

DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing

Exhibit

Refer to the exhibit.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2022-09-01",
      "name": "[parameters('storageAccountName')]",
      "location": "[resourceGroup().location]",
      "kind": "StorageV2",
      "sku": {
        "name": "Standard_LRS"
      },
      "properties": {
        "supportsHttpsTrafficOnly": false,
        "minimumTlsVersion": "TLS1_0",
        "isHnsEnabled": true
      }
    }
  ]
}

Refer to the exhibit. You are reviewing an ARM template for an Azure Data Lake Storage Gen2 account. Which of the following security best practices is violated in this template?

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

✓

The account allows HTTP traffic and uses an outdated TLS version

The template sets supportsHttpsTrafficOnly to false, allowing HTTP traffic, which is insecure. Additionally, minimumTlsVersion is set to TLS1_0, an outdated and insecure version. Option A is incorrect because the location uses resourceGroup().location, which is a common and acceptable practice for flexibility. Option B is incorrect because Standard_LRS is a valid SKU; Geo-redundant storage is not a security best practice requirement. Option C is incorrect because the template does enable hierarchical namespace (isHnsEnabled: true), so that is not a violation.

Answer analysis

Option-by-option breakdown

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

✗
The location should be fixed instead of using resourceGroup().location
Why it's wrong here
Using resourceGroup().location is a deployment portability convention, not a security control, so it cannot constitute the violated security best practice. Hardcoding a location is preferable only when resources must be pinned to a specific region for latency, residency, or paired-region requirements.
✗
The SKU should be Standard_GRS for disaster recovery
Why it's wrong here
SKU redundancy governs durability and availability of stored data, not security posture, so Standard_GRS addresses disaster recovery rather than the violated control. Choosing geo-redundant SKUs is correct when the requirement is regional failover or durability against datacentre loss, not when auditing an ARM template for security misconfiguration.
✗
The account does not enable hierarchical namespace (HNS)
Why it's wrong here
Hierarchical namespace is a functional capability enabling Data Lake Storage Gen2 directory semantics and POSIX ACLs; its absence is a design or feature gap, not the security best-practice violation the template exhibits. Enabling HNS is correct when workloads need directory-level operations or fine-grained ACL inheritance.
✓
The account allows HTTP traffic and uses an outdated TLS version
Why this is correct
Allowing HTTP traffic and an outdated TLS version violates Azure Data Lake Storage Gen2 security baselines, which require HTTPS-only and TLS 1.2 minimum. This exposes data in transit to interception and downgrade attacks, breaching the template's security best practise.

Go deeper

DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question