AZ-104 Implement and Manage Storage Practice Question

Answer analysis

Option-by-option breakdown

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

• ✓

  Create a blob lifecycle management rule.

  Why this is correct

  A blob lifecycle management rule is a policy you define on a storage account that automatically executes actions—such as tiering or deleting—based on rules like age, size, or blob type. It runs daily and evaluates new uploads, making it ideal for monthly reports because you can enforce cost-saving transitions without manual intervention. The rule is the correct starting point because it is the actual Azure feature designed for automated storage-tier governance.

• ✓

  Configure the rule to transition blobs from Hot to Cool after 90 days.

  Why this is correct

  Configuring the rule to move blobs from the Hot tier to the Cool tier after 90 days optimally balances cost and accessibility: Cool offers lower storage prices while keeping data fully online with low latency, which matches the requirement that reports remain readily available. Lifecycle rules enforce this transition based on the modification time, and Cool has a 30-day minimum retention period before it can move again, so 90 days is a valid schedule. This is the right action because it reduces costs without the operational overhead of rehydrating archived data.

• ✗

  Transition the blobs to Archive after 90 days so they cost less than Cool.

  Why it's wrong here

  Although Archive has the lowest storage price, it stores data offline, meaning that reading the reports would first require a rehydration operation that can take up to 15 hours. That delay directly violates the stated requirement that reports remain accessible, unlike Cool which offers immediate retrieval. Assuming Archive is 'better' because its storage cost is lower ignores the significant access and rehydration costs, making this choice incorrect for this scenario.

  When this WOULD be correct

  In a scenario where the compliance team wants to minimize storage costs for data that is rarely accessed and can tolerate several hours of retrieval time (e.g., regulatory archives with access latency up to 15 hours), transitioning to Archive after 90 days would be correct.

• ✗

  Use file share snapshots because lifecycle rules do not apply to blobs.

  Why it's wrong here

  File share snapshots belong to Azure Files, a different storage service from Azure Blob Storage, and they provide read-only point-in-time copies of the files in a file share. They cannot manage blob access tiers or automate transitions within a storage account. Moreover, the premise is false: Azure Blob Storage fully supports lifecycle management rules, so using file share snapshots is both the wrong service and an ineffective approach for this requirement.

  When this WOULD be correct

  If the question asked for a method to preserve previous versions of files in Azure Files for rollback or recovery purposes, enabling file share snapshots would be the correct answer.

• ✗

  Enable soft delete on the container to change access tiers automatically.

  Why it's wrong here

  Soft delete on a blob container is a data-protection feature that preserves deleted blobs for a configurable retention period, letting you recover them after accidental deletion. It does not affect access tiers, nor does it trigger any transition between Hot, Cool, or Archive. To automate tiering you need a lifecycle management rule; soft delete is an entirely separate mechanism and, in fact, if you enable it without lifecycle management, your data stays in its original tier indefinitely.

  When this WOULD be correct

  If the question asked for a feature to recover accidentally deleted blobs or to retain deleted blobs for a specified period, enabling soft delete on the container would be correct.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question