AZ-104 domain - 20% of the exam

Implement and Manage Storage

Implement and Manage Storage is 20% of the AZ-104 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

47
Practice questions
3
Objectives
32
Medium
15
Hard

Where people go wrong

  • Treating key-signed SAS tokens as Entra-secured

    The wrong answers treat a service SAS or an account SAS as if Microsoft Entra credentials secured it. Both are signed with the storage account key, so the app needs that key to create them, and rotating the key revokes them. Only a user delegation SAS is secured with Microsoft Entra credentials, which is why it is the recommended type and why it keeps working after key rotation.

    See it in a sample question
  • Crediting a redundancy option with protection it lacks

    Each wrong answer gives a redundancy option protection it does not offer. LRS keeps every replica in one physical datacenter, so a fire or flood at that site can lose all of them. ZRS spreads copies across availability zones inside the primary region but has no secondary region, so it cannot offer secondary read access. Only the geo options replicate to a second region, and only the read-access geo options expose a secondary endpoint.

    See it in a sample question
  • Applying a protection feature to the wrong object or level

    Blob soft delete restores an individual blob, snapshot or version, so it cannot bring back a deleted container; that needs container soft delete, and versioning does not recover a container either. With versioning enabled, deleting a blob turns the current version into a previous version instead of starting the soft delete retention period. File share soft delete is set at the storage account level and applies to every share in the account.

    See it in a sample question
  • Attaching a retention figure to the wrong feature

    The wrong options swap numbers between unrelated settings. The archive tier has a minimum of 180 days, the cool tier 30 days and the cold tier 90 days, and these are early deletion thresholds. The figure of 365 days is the maximum soft delete retention period, not an archive minimum, and 180 days is not a soft delete ceiling.

    See it in a sample question
  • Crediting an AzCopy command with another command's job

    Each AzCopy command gets a job it does not do. Sync replicates the source to the destination so the destination matches it, yet it does not rename files, and AzCopy has no rename command. Copy transfers data without deleting destination items that are absent from the source. Make only creates a container or file share, and remove only deletes. Set-properties changes access tier, metadata and index tags, not file names.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleImplement and Manage Storagehard

An administrator regenerates the storage account access key that was used to sign a set of distributed SAS tokens. After rotation, which group of tokens keeps working without being regenerated?

  • AUser delegation SAS tokens secured by Entra ID Correct
  • BService SAS tokens signed with the rotated key
  • CAccount SAS tokens signed with the rotated key
  • DEvery SAS token created before the rotation event
Key rotation revokes account and service SAS, but user delegation SAS are unaffected because they are Entra-secured. The documentation says rotating access keys revokes SAS generated from that key, so account and service SAS must be regenerated, while user delegation SAS are secured with Microsoft Entra credentials and aren't affected by key rotation.

Why A is correct: Correct. The documentation says rotating access keys revokes SAS generated from that key, so account and service SAS must be regenerated, while user delegation SAS are secured with Microsoft Entra credentials and aren't affected by key rotation.

Why B is wrong: Rotating the key revokes SAS generated from that key, so service SAS must be regenerated.

Why C is wrong: Account SAS are signed with the account key and are revoked when that key rotates.

Why D is wrong: Key-signed tokens are revoked by rotation, so not all prior tokens survive.

Free sampleImplement and Manage Storagemedium

A finance team runs an analytics pipeline that must keep all data inside one Azure region for governance reasons, yet still survive the loss of an entire datacenter in that region. Which redundancy option meets both requirements at the lowest replication scope?

  • ALocally redundant storage, copying data within one datacenter
  • BZone-redundant storage, copying data across three or more zones Correct
  • CGeo-redundant storage, copying data to a distant second region
  • DRead-access geo-redundant storage, exposing the second region
ZRS gives intra-region datacenter resilience without crossing a regional boundary, unlike any geo-redundant option. Zone-redundant storage copies data synchronously across three or more availability zones inside the chosen primary region, so data remains durable and available if one datacenter or zone is lost while never leaving the region.

Why A is wrong: LRS keeps copies in a single physical datacenter, so a datacenter loss can make all replicas unavailable.

Why B is correct: Correct. Zone-redundant storage copies data synchronously across three or more availability zones inside the chosen primary region, so data remains durable and available if one datacenter or zone is lost while never leaving the region.

Why C is wrong: GRS replicates to a second geographic region, which violates the in-region governance requirement.

Why D is wrong: RA-GRS also copies to a second region and adds secondary read access, breaching the in-region rule.

Free sampleImplement and Manage Storagehard

A user accidentally deletes an entire container, and the contained blobs are now gone. Blob soft delete is already enabled on the account, but recovery of the container fails. Which protection feature must also be enabled to restore a deleted container and its contents?

  • ABlob versioning must be enabled on the storage account
  • BContainer soft delete must be enabled on the storage account Correct
  • CA longer blob soft delete retention period must be configured
  • DA resource lock must be placed on the storage account
Container soft delete, not blob soft delete, recovers a deleted container and its blobs. Blob soft delete restores only an individual blob, snapshot, or version. To restore a container and its contents, container soft delete must also be enabled for the storage account.

Why A is wrong: Versioning preserves prior blob states but cannot recover a deleted container.

Why B is correct: Correct. Blob soft delete restores only an individual blob, snapshot, or version.

Why C is wrong: Blob soft delete protects individual blobs and snapshots, not a deleted container.

Why D is wrong: A lock helps prevent deletion but does not restore a container that was already removed.

Free sampleImplement and Manage Storagemedium

You need to retain monthly compliance archives in a tier where the data is offline and a read or download requires rehydration that can take several hours to complete. Which minimum retention period applies before an early deletion charge would be avoided for blobs you place in that tier?

  • A90 days for blobs placed in the archive tier
  • B180 days for blobs placed in the archive tier Correct
  • C30 days for blobs placed in the archive tier
  • D365 days for blobs placed in the archive tier
Archive minimum is 180 days; cool is 30, cold is 90. The archive tier has the lowest storage cost and a documented minimum of 180 days. Data deleted or moved out before 180 days have elapsed is subject to a prorated early deletion charge.

Why A is wrong: 90 days is the documented minimum for the cold tier, not for archive.

Why B is correct: Correct. The archive tier has the lowest storage cost and a documented minimum of 180 days.

Why C is wrong: 30 days is the documented minimum for the cool tier, not for archive.

Why D is wrong: 365 days is the maximum soft delete retention period, not an archive tier minimum.

Free sampleImplement and Manage Storagemedium

A team has used AzCopy to upload files into an Azure file share and now wants to rename several files in place using AzCopy. What is the correct conclusion about this request?

  • AThe azcopy sync command renames files
  • BThe azcopy set-properties command renames
  • CThe azcopy make command renames shares
  • DAzCopy has no command to rename files Correct
AzCopy copies, syncs, lists, and removes, but it cannot rename files. The grounding explicitly states that AzCopy doesn't have a command to rename files.

Why A is wrong: Sync replicates the source location to the destination; it does not rename files, and AzCopy has no rename command.

Why B is wrong: Set-properties changes access tier, metadata, and index tags of blobs, not file names.

Why C is wrong: Make creates a container or file share; it does not rename existing files.

Why D is correct: Correct. The grounding explicitly states that AzCopy doesn't have a command to rename files.

Other domains in this exam

See also the AZ-104 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.