Skip to main content

Technical Lab: Configure Storage Tiers

Questions​

Question 1 — Multiple Choice​

An engineering team stores audit logs in Azure Blob Storage. Logs from the last 30 days are accessed daily by monitoring tools. Logs between 31 and 90 days are accessed sporadically for investigations. After 90 days, logs are never accessed again but must be retained for 7 years due to regulatory requirements.

Which tier combination represents the most cost-effective strategy for this lifecycle?

A) Hot for the first 30 days, Cool for 31 to 90 days, Archive after 90 days

B) Hot for the first 30 days, Cool for 31 to 90 days, Cold after 90 days

C) Cool for the first 30 days, Archive for 31 to 90 days, Cold after 90 days

D) Hot for the first 30 days, Cold for 31 to 90 days, Archive after 90 days

Question 2 — Technical Scenario​

A developer configures the following lifecycle rule for a storage account:

{
  "rules": [
    {
      "name": "moverParaArchive",
      "type": "Lifecycle",
      "definition": {
        "filters": {
          "blobTypes": ["blockBlob"]
        },
        "actions": {
          "baseBlob": {
            "tierToArchive": {
              "daysAfterModificationGreaterThan": 1
            }
          }
        }
      }
    }
  ]
}

The day after creating a blob, the developer tries to read its content and receives an error. What is the most likely cause?

A) The lifecycle rule was applied and the blob is in Archive tier, which doesn't allow direct reading without rehydration

B) The lifecycle rule failed because newly created blobs cannot be moved to Archive

C) The blockBlob type is not supported by Archive tier, causing silent rule failure

D) The rule requires the blob to be in Cool tier first before transitioning to Archive

Question 3 — Multiple Choice​

When comparing the Cool and Cold tiers for blobs in Azure Blob Storage, which statement correctly describes a difference between them?

A) Cold tier offers lower storage cost per GB than Cool, but with higher access cost per operation

B) Cool tier allows immediate data access, while Cold requires a rehydration process before reading

C) Cold tier is only available in StorageV1 type storage accounts

D) Cool tier applies a minimum retention charge of 180 days, while Cold applies 90 days

Question 4 — Technical Scenario​

An organization needs to recover a blob that is in Archive tier. The blob is 10 GB and the team needs the content within 2 hours maximum. The administrator initiates a rehydration operation.

Which configuration ensures the deadline is met with the highest probability?

A) Set rehydration priority as Standard, as it's the default and processes all blobs equally

B) Set rehydration priority as High, as blobs up to 10 GB with this priority are usually completed in less than 1 hour

C) Copy the blob to a new blob in Hot tier using Copy Blob, without requiring prior rehydration

D) Change the blob tier directly to Hot via Azure portal; the change is immediate for blobs under 50 GB

Question 5 — True or False​

A blob that was moved to Archive tier by a lifecycle rule can be rehydrated directly to Cool tier without needing to go through Hot tier.

Answer Key and Explanations​

Answer Key — Question 1​

Answer: A

The Archive tier is the only one indicated for data that will never be accessed again but needs to be retained long-term. Its storage cost per GB is the lowest of all tiers, making it ideal for 7-year regulatory retention without access.

The main misconception that the distractors represent is the confusion between Cold and Archive: Cold still assumes occasional access and has higher storage cost than Archive. Using Cold for never-accessed data wastes cost without any operational benefit.

Alternative D would be inadequate because Cold, positioned between Cool and Archive, adds no value in the 31 to 90-day interval described: Cool already covers this sporadic access pattern with lower recovery cost.

Answer Key — Question 2​

Answer: A

When a lifecycle rule transitions a blob to Archive tier, the blob becomes offline. This means any direct read operation returns an error until the blob is rehydrated to an online tier (Cool, Cold, or Hot).

The central conceptual error of the distractors is assuming that Archive functions like other tiers in terms of access. In practice, Archive removes the blob from the accessible data plane. There's no restriction on newly created blobs transitioning to Archive, and blockBlob is a fully supported type. The rule also doesn't require prior passage through Cool.

Choosing alternative B or C would lead the administrator to investigate the rule instead of handling rehydration, wasting time and delaying incident resolution.

Answer Key — Question 3​

Answer: A

The Cold tier was introduced to fill the gap between Cool and Archive. It offers lower storage cost than Cool, but with higher access cost per operation. Both tiers, Cool and Cold, allow immediate online access without rehydration, unlike Archive.

The most common error is believing that Cold functions like Archive and requires rehydration (alternative B). This is incorrect: Cold is an online tier.

Alternative D reverses the values: it's Cool that has a 30-day minimum retention and Cold that has a 90-day minimum retention. Confusing these values leads to incorrect lifecycle decisions and unexpected charges for early deletion.

Answer Key — Question 4​

Answer: B

Rehydration with High priority is processed before Standard requests and, for blobs up to 10 GB, the process is usually completed in less than 1 hour, meeting the 2-hour deadline requirement.

The central error of alternative A is that Standard priority can take up to 15 hours, making the deadline impossible. Alternative C is a relevant technical misconception: the Copy Blob operation from an Archive blob doesn't read the original content; the source blob is still offline and the resulting copy won't have the data until rehydration is completed. Alternative D is incorrect because the tier change from Archive to Hot is never immediate, regardless of blob size.

Answer Key — Question 5​

Answer: True

Rehydration of a blob in Archive can be done directly to Cool, Cold, or Hot, with no obligation to go through Hot tier as an intermediate step. The administrator chooses the destination tier at the time of rehydration, either via Set Blob Tier operation or via Copy Blob to a new blob in the desired tier.

The common misconception is imagining there's a mandatory sequential hierarchy for transitions (Archive → Hot → Cool). This incorrect assumption would lead to unnecessary Hot storage costs for data that will be consulted rarely, plus an extra transition step later.