Describe considerations for working with non-relational data on Azure →mediumMultiple ChoiceObjective-mapped

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

Exhibit

{
  "storageAccount": {
    "name": "mystorageaccount",
    "kind": "StorageV2",
    "properties": {
      "accessTier": "Hot"
    }
  },
  "container": {
    "name": "data",
    "properties": {
      "accessTier": "Cool"
    }
  }
}

Refer to the exhibit. An administrator creates a storage account with the Hot tier and then creates a container with the Cool tier. Data is uploaded to the container. Which access tier applies to the uploaded blobs by default?

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

✓

Cool, because the container's default tier is Cool.

In Azure Blob Storage, when a container has a default access tier set, blobs uploaded without explicitly specifying a tier inherit the container's default tier. In the exhibit, the container's access tier is Cool, so blobs uploaded to that container will be Cool by default. Option A is incorrect because the container-level tier overrides the storage account tier for new blobs. Option B is incorrect because blobs are charged based on their assigned tier. Option C is incorrect because the Archive tier is not automatically applied; the container's default tier is Cool. Therefore, Option D is correct.

Answer analysis

Option-by-option breakdown

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

✗
Hot, because the storage account tier is Hot.
Why it's wrong here
The storage account's access tier is only the final fallback default. Container-level default tiers take precedence for blobs uploaded without an explicit blob-tier value. Since the container's default tier is Cool, a blob with no specified tier inherits Cool, even when the storage account itself is Hot. The Hot tier would apply only if both the blob and its container lacked a default tier.
✗
No tier; blobs are not charged until accessed.
Why it's wrong here
Every block blob is automatically assigned an access tier at creation—Hot, Cool, Cold, or Archive—either through explicit specification, container default, or account default. Storage charges depend on that assigned tier and begin immediately; they are not deferred until first access. Not accessing a blob does not waive storage costs. The blob in question inherits Cool, so it is billed at Cool's storage rate from the moment it is written.
✗
Archive, because no tier is set.
Why it's wrong here
The claim incorrectly assumes that an unspecified tier defaults to Archive. In Azure, the default is determined by the container's configured default access tier, not by a global fallback. This container's default tier is Cool, so blobs without an explicit tier are stored as Cool. Archive must be explicitly set on the blob or as the container default; it never appears spontaneously when no tier is specified.
✓
Cool, because the container's default tier is Cool.
Why this is correct
When a blob is uploaded without an explicit access tier, Azure applies the default access tier of its parent container. Here the container's default tier is Cool, so the blob inherits Cool regardless of the storage account's own tier setting. This inheritance ensures consistent billing for all blobs in the container that do not have a per-blob tier override. The blob's effective tier is Cool, making this answer correct.

Quick reference

Azure Blob Storage Tier Comparison

Tier	Storage Cost	Retrieval Cost	Latency	Use Case
Hot	Highest	Lowest	Immediate	Active data, frequent reads
Cool	Lower	Higher	Immediate	Data accessed < once / month
Cold	Lower still	Higher	Immediate	Data accessed < once / quarter
Archive	Lowest	Highest + rehydration delay	Hours	Long-term compliance retention

Go deeper

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

Exhibit

Why each option matters

Option-by-option breakdown

Azure Blob Storage Tier Comparison

Related to this question