SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
AZ-104 · Domain 2

Implement and manage storage practice questions

Implement and manage storage is worth 19% of the AZ-104 exam — the 3rd-heaviest of the 5 domains. Storage access control, storage account configuration, and Azure Files and Blob Storage. Official weighting 15–20%. 6 fully worked examples are further down this page, answers included.

Exam weight
19%
the 3rd-heaviest of the 5 domains
Questions
114
across 3 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 5 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Implement and manage storage questions, fully explained

Questions from the AZ-104 bank mapped to domain 2, with the answer key and the reasoning behind every option. None of them repeat the examples on the main AZ-104 practice page.

Question 1Implement and manage storage

A partner's reporting job needs to read one blob, sales-2026.csv, in the exports container for the next 24 hours. The exports container also holds files for other partners. Your security team requires that storage account keys are not used to sign anything handed to partners. Which SAS should you issue?

Choose one.

  • a
    An account SAS for the Blob service with read permission and a 24-hour expiry

    An account SAS is signed with an account key, which the security team rules out, and it reaches every container in the Blob service.

  • b
    A service SAS for the blob with read permission and a 24-hour expiry, signed with key1

    The scope and permission are right, but a service SAS is signed with an account key, which breaks the security requirement.

  • c
    A user delegation SAS for the exports container with read and list permission for 24 hours

    This avoids account keys, but container scope with list permission exposes the other partners' files in the same container.

  • d
    A user delegation SAS for that one blob with read permission and a 24-hour expiry Correct

    Correct. It is signed with an Entra-issued user delegation key, and blob scope with read-only permission gives the partner exactly the one file for the required window.

The concept

Least-privilege SAS design combines two choices: what signs the token (account key versus Entra user delegation key) and what the token covers (signed resource, permissions and expiry).

Why that’s the answer

The user delegation SAS on the single blob satisfies both constraints: no account key is involved, and the token can read only sales-2026.csv for 24 hours. The service SAS has the right scope but the wrong signer. The container-scoped user delegation SAS has the right signer but the wrong scope, because the container holds other partners' data. The account SAS fails on both counts.

How to reason it out
  1. Apply the signing constraint first: rule out the account SAS and the key-signed service SAS.
  2. Compare the remaining user delegation SAS options by signed resource.
  3. Container scope with list permission exposes other partners' blobs, so reject it.
  4. Choose blob scope, read permission and a 24-hour expiry.

Exam tip: Pick the signer from the key policy, then shrink the signed resource and permissions to exactly what the caller needs.

Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.

Question 2Implement and manage storage

You issued several service SAS tokens for the invoices container, and each token references a stored access policy named partner-read on that container. A contract has ended and those tokens must stop working within the next minute. SAS tokens issued for other containers in the account must keep working. What should you do?

Choose one.

  • a
    Regenerate the account key that signed the invoices container's partner-read tokens

    Regenerating the signing key does revoke the invoices tokens, but every other account SAS and service SAS signed with that key also breaks, including the other containers' tokens.

  • b
    Revoke the user delegation keys that grant access to the storage account

    Revoking user delegation keys invalidates only user delegation SAS tokens; these are key-signed service SAS tokens and keep working.

  • c
    Delete the partner-read access policy from the invoices container Correct

    Correct. A service SAS that references a stored access policy is checked against that policy on each request, so deleting it revokes exactly the tokens bound to it.

  • d
    Apply a SAS expiration policy with Block to the invoices container's account

    The SAS expiration action does not apply to service SAS tokens that use a stored access policy, and an account-wide policy would also hit other containers' tokens.

The concept

A stored access policy moves a service SAS token's permissions and expiry to the server, on the container (or share, queue or table). Deleting, renaming or expiring the policy revokes every SAS bound to it; the change can take up to 30 seconds to take effect.

Why that’s the answer

Deleting the partner-read policy revokes only the tokens that reference it, which is exactly the required blast radius. Regenerating the signing key also revokes them, but it breaks every other SAS signed with that key across the account. Revoking user delegation keys affects a different SAS type. A SAS expiration policy is account-wide and its Block action does not apply to service SAS tokens bound to a stored access policy.

How to reason it out
  1. Identify the SAS type: key-signed service SAS bound to a stored access policy.
  2. Find the narrowest revocation lever: the policy itself.
  3. Reject key regeneration because it breaks other containers' tokens.
  4. Reject user delegation key revocation and SAS expiration policies because they do not target these tokens.

Exam tip: To revoke a group of service SAS tokens surgically, delete or expire the stored access policy they reference; key regeneration is the account-wide sledgehammer.

Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.

Question 3Implement and manage storage

Applications use ad hoc service SAS tokens that were generated with key1 of a storage account and expire next month. As part of a scheduled rotation, an administrator regenerates key1 today. Key2 is not changed. What happens to the existing tokens?

Choose one.

  • a
    They keep working until their expiry time next month

    The expiry is only checked if the signature validates; once key1 is regenerated, the signature no longer matches and the token is rejected.

  • b
    Azure re-signs them with key2 and they keep working

    Azure does not re-sign issued tokens; a SAS is a signed string held by the client, and the service can only validate or reject it.

  • c
    They stop working as soon as key1 has been regenerated Correct

    Correct. The signature was computed with the old key1 value; after regeneration it no longer validates, so every request using those tokens fails regardless of expiry.

  • d
    They stop working once key2 is also regenerated

    Key2 plays no part in validating a token signed with key1; regenerating key1 alone is enough to invalidate them.

The concept

A key-signed SAS (account SAS or ad hoc service SAS) is valid only while the key that signed it still has the same value. Regenerating that key invalidates every such token at once.

Why that’s the answer

Because the token's signature is an HMAC computed with key1, a new key1 value makes every signature fail. Expiry, the other key and Azure itself cannot rescue the token. This is why rotation runbooks first move clients to the other key and reissue SAS tokens before regenerating.

How to reason it out
  1. Identify which key signed the tokens: key1.
  2. Recall that validation recomputes the signature with the current key value.
  3. Regenerating key1 changes that value, so the signatures fail.
  4. Conclude that the tokens fail immediately, independent of their expiry and of key2.

Exam tip: Regenerating a key kills every SAS it signed; reissue tokens with the other key before you rotate.

Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.

Question 4Implement and manage storage

A data analyst signs in with their Microsoft Entra ID account to download reports that are stored as blobs in a storage account. The analyst must not be able to change or delete any data. Following the principle of LEAST privilege, which built-in role should you assign?

Choose one.

  • a
    Reader and Data Access

    Reader and Data Access lets the holder list the account's access keys, and a key gives full read, write and delete access to all data, which breaks the no-change requirement and least privilege.

  • b
    Storage Blob Data Contributor

    Storage Blob Data Contributor allows reading, writing, and deleting blobs, which exceeds the read-only requirement and violates least privilege.

  • c
    Storage Blob Delegator

    Storage Blob Delegator only allows requesting a user delegation key to sign SAS tokens; it includes no action to read blob data.

  • d
    Storage Blob Data Reader Correct

    Correct. Storage Blob Data Reader grants data-plane read access to blob containers and data and nothing more, which is exactly what a read-only analyst needs.

The concept

Azure separates control-plane roles (managing the storage account resource) from data-plane roles (accessing the data inside it). Reading blob data with an Entra identity requires a data-plane role such as Storage Blob Data Reader.

Why that’s the answer

Storage Blob Data Reader is the narrowest built-in role that lets an Entra identity read blob data and nothing more. Reader and Data Access is the tempting trap: it reaches the data only by listing account keys, and a key is full access. Storage Blob Delegator sounds blob-specific but only lets the holder get a user delegation key. Storage Blob Data Contributor adds write and delete, which the analyst must not have.

How to reason it out
  1. Determine whether the requirement is control-plane (manage the account) or data-plane (read the data); here it is data-plane read with an Entra identity.
  2. Reject roles that reach data only through account keys, such as Reader and Data Access, because a key grants full access.
  3. Reject roles with no data actions, such as Storage Blob Delegator.
  4. Apply least privilege among the blob data roles and pick the read-only one, Storage Blob Data Reader.

Exam tip: Entra-based read-only blob access = Storage Blob Data Reader; roles that list keys grant full access, and Delegator grants none.

Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.

Question 5Implement and manage storage

An automation service principal must upload and overwrite blobs in one container of a Data Lake Storage account by using Microsoft Entra ID authorization. It must not be able to set POSIX access control lists on the data, take ownership of it or manage the storage account. Which role assignment meets the requirement with LEAST privilege?

Choose one.

  • a
    Storage Blob Data Owner scoped to the container

    Storage Blob Data Owner adds full control including setting POSIX ACLs and ownership, which the principal must not have, even at container scope.

  • b
    Contributor scoped to the storage account's resource group

    Contributor is a control-plane role that can manage the account (and everything else in the resource group) and list its access keys; it grants management rights the principal must not have.

  • c
    Storage Blob Data Contributor scoped to the container Correct

    Correct. This data-plane role allows read, write, and delete on blob data, which covers uploads and overwrites, and scoping it to the single container keeps the grant as narrow as possible.

  • d
    Storage Blob Delegator scoped to the storage account

    Storage Blob Delegator only allows requesting a user delegation key; it has no blob data actions, so nothing could be uploaded.

The concept

Least privilege in Azure Storage means picking the narrowest data-plane role that covers the required operations and assigning it at the narrowest scope, which can be a single container.

Why that’s the answer

Uploading and overwriting are writes on blob data, so the principal needs Storage Blob Data Contributor, and container scope limits it to the one container. Storage Blob Data Owner is the near-twin: same data access plus POSIX ACL management and ownership, which the stem forbids. Contributor manages the account and can list keys. Storage Blob Delegator can only obtain a user delegation key and cannot write data.

How to reason it out
  1. List the operations required: create and overwrite blobs, which are data-plane writes.
  2. List what is forbidden: POSIX ACLs and ownership (Data Owner) and account management (Contributor).
  3. Match the smallest built-in role that writes data without those rights: Storage Blob Data Contributor.
  4. Assign it at container scope.

Exam tip: Match the smallest data-plane role to the operations needed and assign it at the narrowest scope, down to a single container.

Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.

Question 6Implement and manage storage

You set AllowSharedKeyAccess to false on a storage account to disallow Shared Key authorization. Which of the following access methods will continue to work?

Choose one.

  • a
    An account SAS

    An account SAS is signed with an account access key, and disabling Shared Key authorization rejects any request authorized via those keys, including key-signed SAS.

  • b
    A service SAS signed with an access key

    A service SAS is also signed with an account access key, so it is blocked once Shared Key authorization is disabled.

  • c
    A user delegation SAS Correct

    Correct. A user delegation SAS is signed with an Entra-issued user delegation key, not an account access key, so disabling Shared Key authorization does not affect it.

  • d
    Direct requests authorized with the account access key

    This is exactly the authorization method being disabled; requests presenting the account key are rejected.

The concept

Disabling Shared Key authorization (AllowSharedKeyAccess = false) forces all requests to be authorized with Microsoft Entra ID. Anything whose validity chains back to an account access key stops working, including account SAS and service SAS.

Why that’s the answer

The user delegation SAS survives because its signature comes from a user delegation key obtained with Entra ID credentials, keeping it within the Entra authorization chain. The account SAS, the service SAS, and raw key auth all fail because each is validated against a storage account access key, which is precisely the mechanism that was turned off. This setting is how organizations enforce an Entra-only access posture.

How to reason it out
  1. Understand that AllowSharedKeyAccess = false blocks every request whose authorization derives from the account access keys.
  2. Classify each SAS type by its signing mechanism: account and service SAS use account keys; user delegation SAS uses an Entra-issued key.
  3. Conclude that only Entra-based methods keep working: direct Entra tokens with RBAC roles and user delegation SAS.
  4. Before flipping the setting in production, audit workloads for key or key-signed SAS usage to avoid outages.

Exam tip: Disabling Shared Key authorization kills account SAS and service SAS along with direct key access; only Entra ID tokens and user delegation SAS keep working.

Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.

What AZ-104 domain 2 tests, topic by topic

The official exam guide breaks Implement and manage storage into 3 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published AZ-104 practice questions per topic in Implement and manage storage
TopicWhat it coversQuestions
Configure access to storageSkills outline section (AZ-104, as of April 17, 2026). Configuring Azure Storage firewalls and virtual networks; creating and using shared access signature (SAS) tokens; configuring stored access policies; managing access keys; configuring identity-based access for Azure Files.38
Configure and manage storage accountsSkills outline section (AZ-104, as of April 17, 2026). Creating and configuring storage accounts; configuring Azure Storage redundancy; configuring object replication; configuring storage account encryption; managing data by using Azure Storage Explorer and AzCopy.38
Configure Azure Files and Azure Blob StorageSkills outline section (AZ-104, as of April 17, 2026). Creating and configuring a file share in Azure Files and a container in Azure Blob Storage; configuring storage tiers; configuring soft delete for blobs and containers; configuring snapshots and soft delete for Azure Files; configuring blob lifecycle management and blob versioning.38
Total114

Revise Implement and manage storage before you drill it

Other AZ-104 domains

Implement and manage storage: your questions

Implement and manage storage is domain 2 of the AZ-104 exam guide and carries 19% of the scored content — the 3rd-heaviest of the 5 domains. On a 50-question paper that works out to roughly 10 questions, though Microsoft Azure does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official AZ-104 exam guide.