AZ-104 practice by domain

AZ-104 Storage Practice Questions

Ten practice questions from the CramHQ AZ-104 bank for Implement and Manage Storage, with answers and explanations. No signup needed.

Question 1 of 10Implement and Manage Storage

CramHQ is creating storage for an alert-processing service in one Azure region. The service writes telemetry objects, sends dispatch messages through Azure Queue Storage, and must let analysts read a replicated copy if the primary region becomes unavailable, while also tolerating a zone outage in the primary region. Which storage account configuration should you recommend?

  1. A. Create a standard general-purpose v2 storage account with read-access geo-zone-redundant storage (RA-GZRS).
  2. B. Create a premium file shares storage account with zone-redundant storage (ZRS).
  3. C. Create a premium block blobs storage account with zone-redundant storage (ZRS).
  4. D. Create a standard general-purpose v2 storage account with geo-zone-redundant storage (GZRS).
Show answer and explanation

Answer: A

This supports the required object and queue workloads and provides zone redundancy in the primary region plus read access to replicated data in the secondary region.

If you picked B

Why it is tempting: The ZRS label matches the zone-outage part of the stem, and premium file shares sound like a high-capability storage option.

Why it is wrong: Premium file shares accounts are for Azure Files workloads, not for combining object storage with Azure Queue Storage.

If you picked C

Why it is tempting: Premium block blobs sounds appropriate for high-performance object storage, and ZRS matches the primary-region zone-resilience cue.

Why it is wrong: A storage account recommendation must support every required service, including Azure Queue Storage when queues are explicitly named.

If you picked D

Why it is tempting: GZRS combines zone redundancy in the primary region with geo-replication, so it matches most of the resiliency language.

Why it is wrong: Use read-access geo-redundant or read-access geo-zone-redundant storage when the requirement includes direct read access to the secondary region.

Question 2 of 10Implement and Manage Storage

CramHQ stores archived telemetry blobs for multiple missions in one storage account. Security requires a reversible emergency stop for a single mission that denies reads and writes without moving data or affecting other missions. Operators must trigger the stop from the central protection store used by the platform. Which recommendation best meets the requirement?

  1. A. Create one Azure Storage encryption scope per mission using Microsoft.KeyVault, grant the storage account managed identity key access, make it the container default, prevent override, and disable or revoke the mission key during an emergency stop.
  2. B. Require customer-provided keys on blob operations, store each mission key in Azure Key Vault, and have clients omit the key when a mission must be stopped.
  3. C. Configure the storage account encryption key with Microsoft.KeyVault, grant the storage account managed identity key access, and disable that key when a mission must be stopped.
  4. D. Create one Azure Storage encryption scope per mission using Microsoft.Storage, make it the container default, prevent override, and disable storage account shared key access during a stop.
Show answer and explanation

Answer: A

Azure Storage encryption scopes can be applied as an enforced container default. When the scope uses Microsoft.KeyVault, disabling or revoking that mission-specific key from Key Vault causes operations using that scope to fail without stopping other missions' scopes.

If you picked B

Why it is tempting: The option mentions per-mission keys and Key Vault, which sounds like centralized key management.

Why it is wrong: Customer-provided keys are supplied with individual blob requests; customer-managed keys are the Azure Storage encryption control that can be enforced through Key Vault.

If you picked C

Why it is tempting: Disabling a Key Vault key for storage encryption can deny access, so it appears to satisfy the emergency-stop requirement.

Why it is wrong: The selected storage security control must match the policy boundary; a single-mission stop needs a mission-scoped protection boundary, not an account-level one.

If you picked D

Why it is tempting: The encryption scope, container default, and prevent-override settings resemble the correct pattern.

Why it is wrong: Use a storage encryption control backed by the required protection store when the policy calls for data-protection revocation; disabling Shared Key access changes an authentication method.

Question 3 of 10Implement and Manage Storage

CramHQ lets regional telemetry contractors push daily grid snapshots into one storage container for a 10-day maintenance window. If a contractor workstation is compromised, security must stop that contractor's future uploads without replacing keys used by unrelated processes. Contractors must not inspect existing snapshots. Which shared access signature configuration should you recommend?

  1. A. Create a service SAS for the container with read, write, create, and list permissions and a signed expiry at the end of the window.
  2. B. Create a service SAS for the container that references a stored access policy with create and write permissions and a policy expiry at the end of the window.
  3. C. Create an account SAS for Blob service object access with create and write permissions and a signed expiry at the end of the window.
  4. D. Create a user delegation SAS for the container with create and write permissions, then renew it for the remaining days when the first token expires.
Show answer and explanation

Answer: B

A service SAS can be tied to a stored access policy on the container. Updating or deleting that policy revokes issued signatures without rotating account keys, and create/write permits uploads without read or list access.

If you picked A

Why it is tempting: The choice uses a service SAS and expires at the end of the maintenance window, so it looks controlled.

Why it is wrong: Limit a SAS to the exact operations needed; upload-only access should use create and write without read or list.

If you picked C

Why it is tempting: The choice narrows the service, resource type, permissions, and expiry, which sounds like least privilege.

Why it is wrong: Match the SAS type to the control boundary; account SAS is not the right fit when stored-access-policy revocation is required.

If you picked D

Why it is tempting: User delegation SAS is often preferred because it uses Microsoft Entra credentials instead of account keys.

Why it is wrong: Use user delegation SAS only when its access model fits the requirement; it cannot reference a stored access policy for targeted revocation.

Show all 10 practice questions
Question 4 of 10Implement and Manage Storage

CramHQ stores airline booking manifests in an Azure storage account. An analytics subnet in the same region is already permitted through the account's restricted network settings. Analysts at a branch office connected to the hub virtual network by site-to-site VPN must run AzCopy from their laptops without opening the account to all public networks; their traffic is required to stay on the VPN path. Which recommendation is best?

  1. A. Add an IP network rule for the branch office public NAT address, allow the storage account public endpoint, and force AzCopy traffic to bypass the VPN.
  2. B. Create a private endpoint for the required storage subresource in the hub virtual network, configure private DNS for branch clients, and keep public network access restricted.
  3. C. Add an IP network rule for the branch office private address range, route AzCopy traffic over the site-to-site VPN, and keep the storage account set to selected networks.
  4. D. Enable the Microsoft.Storage service endpoint on the GatewaySubnet, add a virtual network rule for that subnet, and keep the storage account set to selected networks.
Show answer and explanation

Answer: B

This aligns the client path with documented behavior: branch clients resolve the storage name to a private address reachable through the VPN, and the storage firewall does not need a public rule for that traffic.

If you picked A

Why it is tempting: Storage accounts can allow specific public IP ranges, so a branch public NAT address sounds like a narrow exception.

Why it is wrong: A public IP network rule still uses the storage account public endpoint. Private-path requirements call for private endpoint connectivity and matching DNS resolution.

If you picked C

Why it is tempting: The option keeps traffic on the VPN and uses selected networks, so it appears to preserve the required path.

Why it is wrong: Storage IP network rules for the public endpoint use public IPv4 source ranges. A private branch range over VPN does not authorize those requests.

If you picked D

Why it is tempting: The branch connects through the hub virtual network, and service endpoints plus virtual network rules are valid for Azure subnets.

Why it is wrong: A storage virtual network rule applies to traffic from the authorized subnet using the service endpoint. Remote VPN clients do not become requests from the GatewaySubnet merely by traversing it.

Question 5 of 10Implement and Manage Storage

CramHQ ingests satellite telemetry into blob containers and Azure queues in a region where all listed choices are available. A failure of one availability zone in that region must not stop normal writes. If the whole region is unavailable, operators must still be able to review whatever telemetry has already been copied elsewhere before deciding whether to make the account writable in another region. Which new account configuration should you deploy?

  1. A. Standard general-purpose v2 account with geo-zone-redundant storage (GZRS).
  2. B. Standard general-purpose v2 account with read-access geo-zone-redundant storage (RA-GZRS).
  3. C. Standard general-purpose v2 account with read-access geo-redundant storage (RA-GRS).
  4. D. Standard general-purpose v2 account with zone-redundant storage (ZRS).
Show answer and explanation

Answer: B

RA-GZRS combines synchronous copies across availability zones in the primary region with asynchronous copying to a paired region and a readable secondary endpoint before failover. Standard general-purpose v2 also supports blobs and queues.

If you picked A

Why it is tempting: This choice matches the zone-failure requirement and includes geo-replication, so it looks like it covers both outage scopes.

Why it is wrong: Use read-access geo-zone-redundant storage when the workload needs primary-region zone resilience and readable secondary data before failover.

If you picked C

Why it is tempting: This choice directly matches the need to review copied data elsewhere before failover.

Why it is wrong: A requirement for normal writes after one availability zone fails requires a zone-redundant primary-region design, not only read-access geo-redundancy.

If you picked D

Why it is tempting: This choice is strong for keeping data available in the primary region when one zone becomes unavailable.

Why it is wrong: Use a geo-redundant option when the scenario requires data copied to another region for regional outage handling.

Question 6 of 10Implement and Manage Storage

CramHQ is moving department shares from Windows file servers to SMB Azure file shares. Analysts sign in with AD DS accounts synced to Microsoft Entra ID. Several Azure VMs that need the shares are Microsoft Entra joined and will not have reliable connectivity to on-premises domain controllers at access time. Existing folder ACLs must continue to decide departmental access. Which configuration should you recommend?

  1. A. Enable Microsoft Entra Domain Services authentication; join the Azure VMs to the managed domain; assign Azure RBAC share roles to synced groups; keep the Windows ACLs.
  2. B. Enable on-premises AD DS authentication for the storage account; assign Azure RBAC share roles to synced AD DS groups; keep the Windows ACLs on folders.
  3. C. Enable Microsoft Entra Kerberos for the storage account; assign Azure RBAC share roles to groups created only in Microsoft Entra ID; recreate matching Windows ACL entries on the folders.
  4. D. Enable Microsoft Entra Kerberos for the storage account; assign Azure RBAC share roles to AD DS groups synced to Microsoft Entra ID; keep the Windows ACLs on folders.
Show answer and explanation

Answer: D

Microsoft Entra Kerberos supports hybrid identities from Microsoft Entra joined clients without requiring client line-of-sight to AD DS during access. Share roles can target synced groups, and folder ACLs continue to apply to the corresponding AD DS identities.

If you picked A

Why it is tempting: It mentions synced groups and keeps Windows ACLs, so it appears to preserve the existing authorization model.

Why it is wrong: Choose an Azure Files SMB identity source that fits the clients as stated; Microsoft Entra joined clients without reliable domain-controller connectivity point to Microsoft Entra Kerberos.

If you picked B

Why it is tempting: On-premises AD DS authentication closely resembles the existing file server model and keeps familiar group and ACL behavior.

Why it is wrong: On-premises AD DS authentication is a fit when clients are domain joined or have uninterrupted domain-controller connectivity; Microsoft Entra Kerberos removes that access-time controller dependency for supported joined clients.

If you picked C

Why it is tempting: Microsoft Entra Kerberos is the right authentication direction, and cloud-only Microsoft Entra groups can look like a natural Azure RBAC target.

Why it is wrong: For hybrid Azure Files authorization, assign share-level roles to synced principals and let Windows ACLs continue to apply to the corresponding AD DS identities.

Question 7 of 10Implement and Manage Storage

CramHQ must rotate secrets for a storage account used by live game servers. Several services still use connection strings with key1, while maintenance windows are unavailable during a tournament. Security wants both account keys refreshed without interrupting writes. Which recommendation best supports the rotation?

  1. A. Use Azure Storage account access keys: update all connection strings using key1 to key2, regenerate key1, verify access, then move workloads to key1 and regenerate key2.
  2. B. Use Azure Storage account access keys: regenerate key2, update key1 connection strings to key2, then regenerate key1 after all services report healthy writes.
  3. C. Use Azure Storage account access keys: update only new deployments to key2, regenerate key2, and leave existing key1 connection strings unchanged until the next release.
  4. D. Use Azure Storage account access keys: regenerate key1 first, update failed services to key2, then regenerate key2 after the failed services recover.
Show answer and explanation

Answer: A

Azure Storage provides two account access keys so applications can continue using one valid key while the other is regenerated. Moving consumers before each regeneration avoids breaking live connections and refreshes both keys.

If you picked B

Why it is tempting: It keeps services on key1 while key2 is regenerated and waits for healthy writes before changing key1, so it appears outage-aware.

Why it is wrong: A complete staged rotation moves workloads away from the active key, regenerates it, moves workloads to the refreshed key, and then regenerates the remaining key.

If you picked C

Why it is tempting: Updating only new deployments looks low risk during a tournament because existing services keep using their current connection strings.

Why it is wrong: Key rotation must account for all dependent consumers, not only new deployments, when the requirement is to refresh both account keys.

If you picked D

Why it is tempting: It eventually moves failed services to the other key, so it can look like a reactive way to discover dependencies.

Why it is wrong: Move consumers off a storage account key before regenerating that key; regeneration immediately invalidates connection strings that use it.

Question 8 of 10Implement and Manage Storage

CramHQ stores satellite telemetry files in an Azure Storage account used by automated jobs and analysts. A recent review found one container was briefly readable without credentials after an operator change. Management wants an account-level guardrail that prevents that class of mistake while preserving existing authenticated access paths and network design. What should you configure?

  1. A. Set every blob container Public access level to Private; use periodic reviews to detect future changes.
  2. B. Set Secure transfer required to Enabled and Minimum TLS version to TLS 1.2; leave authorization settings unchanged.
  3. C. Set Public network access to Disabled on the storage account; keep private endpoint access and existing role assignments unchanged.
  4. D. Set Allow Blob anonymous access to Disabled on the storage account; leave container public access levels and existing role assignments unchanged.
Show answer and explanation

Answer: D

This enforces the decision at the account boundary. Anonymous requests are rejected even if a container is configured for anonymous access, while authenticated requests continue subject to their existing permissions and network rules.

If you picked A

Why it is tempting: Setting containers to Private directly addresses the container that became readable without credentials.

Why it is wrong: Use an account-level control when the requirement is to prevent future lower-scope changes from allowing anonymous blob reads.

If you picked B

Why it is tempting: Secure transfer and TLS settings are real storage account security controls.

Why it is wrong: Transport settings control how clients connect; anonymous access settings control whether credential-free blob reads are allowed.

If you picked C

Why it is tempting: Disabling public network access can reduce public exposure and may seem like the strongest security option.

Why it is wrong: Network controls decide which paths can reach the account; anonymous access controls decide whether a reached blob request without credentials is accepted.

Question 9 of 10Implement and Manage Storage

CramHQ stores raw drive logs and reviewed simulation outputs as block blobs in the same container. Only the reviewed outputs should be copied to a second region for compute jobs, and the raw logs must stay local to avoid unnecessary transfer cost. Which recommendation should you implement?

  1. A. Configure an object replication policy with separate replication rules for the same source container, using different destination containers for raw logs and reviewed outputs.
  2. B. Configure an object replication policy with one replication rule for the container and omit filters.prefixMatch from the rule.
  3. C. Configure an object replication policy with one replication rule for the container and set filters.minCreationTime to the first reviewed output creation time.
  4. D. Configure an object replication policy with one replication rule for the container and set filters.prefixMatch to the reviewed output path.
Show answer and explanation

Answer: D

This matches the requirement because an object replication rule can include a prefixMatch filter. Only block blobs whose names match that path are copied to the destination container.

If you picked A

Why it is tempting: Using different destination containers sounds like it could separate raw logs from reviewed outputs after replication.

Why it is wrong: Use the replication rule's blob-name prefix filter when the selected data set is a subset inside the same source container.

If you picked B

Why it is tempting: A single rule for the container matches the source location, so it can look like the normal object replication setup.

Why it is wrong: Add prefixMatch when only blob names under a specific path or prefix should be replicated.

If you picked C

Why it is tempting: Starting replication from the first reviewed output time sounds like it avoids older raw logs.

Why it is wrong: Use a prefixMatch filter when the selection is based on blob path or name; a creation-time filter only narrows by when blobs were created.

Question 10 of 10Implement and Manage Storage

CramHQ must move 6 TB of tenant export blobs between two storage accounts. Both accounts reject traffic from the public internet and are reachable only from a peered operations VNet. Administrator workstations are not connected to that peered operations VNet. The operations team is not allowed to receive account keys or shared access signatures. Which recommendation should you make?

  1. A. Use Azure Storage Explorer from an administrator workstation and sign in with Microsoft Entra ID after granting Storage Blob Data Contributor on both accounts.
  2. B. Use the Azure portal upload and copy experience from an administrator workstation signed in with Microsoft Entra ID.
  3. C. Run AzCopy on an operations VNet VM and sign in with Microsoft Entra ID after granting Storage Blob Data Contributor on both accounts.
  4. D. Run AzCopy on an operations VNet VM and authenticate with a user delegation SAS generated by a storage administrator.
Show answer and explanation

Answer: C

AzCopy can run from a host that has the permitted private path and can authorize blob data operations with Microsoft Entra ID when the identity has the required data-plane role.

If you picked A

Why it is tempting: Storage Explorer can use Microsoft Entra sign-in, and Storage Blob Data Contributor is the right kind of data-plane role.

Why it is wrong: The storage data operation must originate from a source allowed by the storage account network rules and use permitted authorization.

If you picked B

Why it is tempting: The portal is an Azure service interface, so it can seem separate from the workstation's network path.

Why it is wrong: Interactive portal access does not remove the need for the data-plane operation to satisfy the storage account's network restrictions.

If you picked D

Why it is tempting: Running AzCopy on the operations VNet VM satisfies the network-path requirement, and a user delegation SAS can be used for blob access in other scenarios.

Why it is wrong: When the scenario forbids account keys and shared access signatures, use direct identity-based authorization instead of distributing a SAS.

CramHQ links wrong answers to the mistake behind them. The free diagnostic finds yours, then your Pass Plan works on them.