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

Refer to the exhibit.

```json
{
  "version": "2019-12-12",
  "rules": [
    {
      "name": "rule1",
      "enabled": true,
      "type": "Lifecycle",
      "definition": {
        "filters": {
          "blobTypes": ["blockBlob"],
          "prefixMatch": ["logs/"]
        },
        "actions": {
          "baseBlob": {
            "tierToCool": {
              "daysAfterModificationGreaterThan": 30
            },
            "tierToArchive": {
              "daysAfterModificationGreaterThan": 90
            },
            "delete": {
              "daysAfterModificationGreaterThan": 365
            }
          }
        }
      }
    }
  ]
}
```

You have applied the lifecycle management policy shown in the exhibit to an Azure Storage account. A blob named 'logs/error.log' was last modified 200 days ago. In which tier is the blob currently stored?

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

✓

Archive tier

The policy moves blobs to Cool after 30 days and to Archive after 90 days. Since the blob was modified 200 days ago, it has already been moved to Archive after 90 days. The delete action occurs after 365 days, so it has not been deleted yet. Therefore, the blob is in the Archive tier.

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 tier
Why it's wrong here
At 200 days, the lifecycle policy has already executed two transitions: after 30 days from the blob's last modification, it moved from Hot to Cool, and after 90 days it moved from Cool to Archive. Since the policy uses age thresholds and 200 days exceeds 90, the blob's tier is Archive, not Hot. Hot is only the initial tier or for data with frequent access; it is not the tier for a blob that has been subject to this policy for this duration.
✗
The blob has been deleted
Why it's wrong here
The lifecycle policy includes a deletion action that is configured to remove the blob 365 days after its last modification, but at day 200 that future rule has not yet taken effect. Deletion and tiering are separate actions; all tier transitions happen first, and deletion occurs only after the specified age is reached. Therefore, the blob still exists and, because it has been archived at day 90, it resides in the Archive tier.
✗
Cool tier
Why it's wrong here
The policy moves blobs to Cool at 30 days, but it does not stay there indefinitely: the next rule transitions the blob to Archive after 90 days from last modification. Because 200 days is well past the 90-day threshold, the blob has already been moved out of Cool into Archive. Cool tier supports moderate access frequencies, but the lifecycle configuration in this scenario is set to archive older data, so Cool is only a temporary staging tier.
✓
Archive tier
Why this is correct
Given the lifecycle policy, the blob is moved to Archive tier once it is 90 days old, and no further tier changes are defined before the 365-day deletion. At 200 days after last modification, the blob has securely been sitting in Archive tier for 110 days. Archive offers the lowest storage cost but requires a rehydration step before reading, which is appropriate for this blob's age and access pattern.

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

1 more way this is tested on DP-900

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company stores backup files in Azure Blob Storage. The backup files are accessed frequently for the first 30 days, then only rarely for the next six months. After one year, the files must be retained for compliance but are never accessed. The company wants to minimize storage costs. Which solution should they use?

medium

A.Manually move files between storage accounts
✓ B.Use Azure Blob Storage lifecycle management policies
C.Use Azure File Sync
D.Use Azure NetApp Files

Why B: Azure Blob Storage lifecycle management policies allow you to automatically transition blobs to cooler tiers (e.g., from Hot to Cool after 30 days, then to Archive after one year) and delete blobs after a specified period, all without manual intervention. This directly matches the access pattern: frequent access for 30 days, rare access for six months, and never accessed after one year, minimizing storage costs by using the most cost-effective tier for each phase.

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This DP-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-900 exam.