Key rotation has access and version lifecycle implications for encrypted storage. In this case, a storage account using CMK stops working after the key is disabled. “Use versioned key management and supported storage account CMK rotation behavior” would not satisfy that requirement; the supported action is “The service requires access to the configured active customer-managed key”. Disabling or removing key authorization can disrupt storage encryption operations.

Customer-managed encryption depends on authorized access to the external key. In this case, a storage account using CMK stops working after the key is disabled. “Grant the storage identity required key unwrap/wrap/get permissions per the chosen model” would not satisfy that requirement; the supported action is “The service requires access to the configured active customer-managed key”. Disabling or removing key authorization can disrupt storage encryption operations.

The read-access variant supports eligible secondary reads without completing failover. In this case, a storage account using CMK stops working after the key is disabled. “Read-access GZRS (RA-GZRS)” would not satisfy that requirement; the supported action is “The service requires access to the configured active customer-managed key”. Disabling or removing key authorization can disrupt storage encryption operations.

Disabling or removing key authorization can disrupt storage encryption operations. In this case, a compliance rule requires rotating the customer-managed key regularly. “The service requires access to the configured active customer-managed key” would not satisfy that requirement; the supported action is “Use versioned key management and supported storage account CMK rotation behavior”. Key rotation has access and version lifecycle implications for encrypted storage.

Customer-managed keys allow customer control of the encryption key lifecycle for supported storage services. In this case, a compliance rule requires rotating the customer-managed key regularly. “Configure a customer-managed key with supported Key Vault or managed HSM integration” would not satisfy that requirement; the supported action is “Use versioned key management and supported storage account CMK rotation behavior”. Key rotation has access and version lifecycle implications for encrypted storage.

AzCopy tracks transfer jobs so interrupted operations may be resumed. In this case, a compliance rule requires rotating the customer-managed key regularly. “Use supported job status and resume commands when applicable” would not satisfy that requirement; the supported action is “Use versioned key management and supported storage account CMK rotation behavior”. Key rotation has access and version lifecycle implications for encrypted storage.

Customer-managed keys allow customer control of the encryption key lifecycle for supported storage services. In this case, a storage account loses managed-identity permission to the key vault. “Configure a customer-managed key with supported Key Vault or managed HSM integration” would not satisfy that requirement; the supported action is “Grant the storage identity required key unwrap/wrap/get permissions per the chosen model”. Customer-managed encryption depends on authorized access to the external key.

Disabling or removing key authorization can disrupt storage encryption operations. In this case, a storage account loses managed-identity permission to the key vault. “The service requires access to the configured active customer-managed key” would not satisfy that requirement; the supported action is “Grant the storage identity required key unwrap/wrap/get permissions per the chosen model”. Customer-managed encryption depends on authorized access to the external key.

AzCopy optimizes bulk Azure Storage data transfer and supports authentication. In this case, a storage account loses managed-identity permission to the key vault. “AzCopy with appropriately scoped source and destination authorization” would not satisfy that requirement; the supported action is “Grant the storage identity required key unwrap/wrap/get permissions per the chosen model”. Customer-managed encryption depends on authorized access to the external key.

Repeatable bulk transfers are better served by scriptable tools than GUI clicks. In this case, a company needs to copy 15 TB between storage accounts with reliable parallel transfers. “Use AzCopy or an appropriate Azure CLI/SDK automation” would not satisfy that requirement; the supported action is “AzCopy with appropriately scoped source and destination authorization”. AzCopy optimizes bulk Azure Storage data transfer and supports authentication.

Customer-managed encryption depends on authorized access to the external key. In this case, a company needs to copy 15 TB between storage accounts with reliable parallel transfers. “Grant the storage identity required key unwrap/wrap/get permissions per the chosen model” would not satisfy that requirement; the supported action is “AzCopy with appropriately scoped source and destination authorization”. AzCopy optimizes bulk Azure Storage data transfer and supports authentication.

Storage Explorer offers interactive management of supported storage resources. In this case, a company needs to copy 15 TB between storage accounts with reliable parallel transfers. “Azure Storage Explorer” would not satisfy that requirement; the supported action is “AzCopy with appropriately scoped source and destination authorization”. AzCopy optimizes bulk Azure Storage data transfer and supports authentication.

Repeatable bulk transfers are better served by scriptable tools than GUI clicks. In this case, a transfer stops halfway and the admin starts an entirely new transfer unnecessarily. “Use AzCopy or an appropriate Azure CLI/SDK automation” would not satisfy that requirement; the supported action is “Use supported job status and resume commands when applicable”. AzCopy tracks transfer jobs so interrupted operations may be resumed.

Key rotation has access and version lifecycle implications for encrypted storage. In this case, a transfer stops halfway and the admin starts an entirely new transfer unnecessarily. “Use versioned key management and supported storage account CMK rotation behavior” would not satisfy that requirement; the supported action is “Use supported job status and resume commands when applicable”. AzCopy tracks transfer jobs so interrupted operations may be resumed.

Storage Explorer offers interactive management of supported storage resources. In this case, a transfer stops halfway and the admin starts an entirely new transfer unnecessarily. “Azure Storage Explorer” would not satisfy that requirement; the supported action is “Use supported job status and resume commands when applicable”. AzCopy tracks transfer jobs so interrupted operations may be resumed.

Storage Explorer is useful for interactive GUI exploration, but a manually operated session is not an unattended bulk-transfer workflow. The competing choice “Azure Storage Explorer used manually in a desktop GUI every night” does not meet the specific requirement: A storage administrator needs a scheduled unattended bulk transfer of blob data between Azure storage accounts, with logs and recoverable transfer jobs rather than interactive browsing. Which utility best fits. The supported action is “AzCopy with appropriately scoped authentication and automation”.

Lifecycle policies typically manage tiering and deletion of eligible blobs in their configured scope, not arbitrary account-to-account scripted copy operations. The competing choice “A blob lifecycle policy that automatically converts files between different storage accounts” does not meet the specific requirement: A storage administrator needs a scheduled unattended bulk transfer of blob data between Azure storage accounts, with logs and recoverable transfer jobs rather than interactive browsing. Which utility best fits. The supported action is “AzCopy with appropriately scoped authentication and automation”.

Enabling public anonymous access is not required for authenticated transfer and would unnecessarily expose customer data. The competing choice “An account-wide anonymous access setting that lets anyone copy every blob” does not meet the specific requirement: A storage administrator needs a scheduled unattended bulk transfer of blob data between Azure storage accounts, with logs and recoverable transfer jobs rather than interactive browsing. Which utility best fits. The supported action is “AzCopy with appropriately scoped authentication and automation”.

AzCopy tracks transfer jobs so interrupted operations may be resumed. In this case, an administrator must manage storage in a disconnected desktop script. “Use supported job status and resume commands when applicable” would not satisfy that requirement; the supported action is “Use AzCopy or an appropriate Azure CLI/SDK automation”. Repeatable bulk transfers are better served by scriptable tools than GUI clicks.

AzCopy optimizes bulk Azure Storage data transfer and supports authentication. In this case, an administrator must manage storage in a disconnected desktop script. “AzCopy with appropriately scoped source and destination authorization” would not satisfy that requirement; the supported action is “Use AzCopy or an appropriate Azure CLI/SDK automation”. Repeatable bulk transfers are better served by scriptable tools than GUI clicks.

Legal holds and retention policies protect data even from automatic management actions. In this case, an administrator must manage storage in a disconnected desktop script. “Immutability restrictions take precedence over ordinary lifecycle deletion” would not satisfy that requirement; the supported action is “Use AzCopy or an appropriate Azure CLI/SDK automation”. Repeatable bulk transfers are better served by scriptable tools than GUI clicks.

Blob object replication asynchronously copies eligible blob updates under configured policies. In this case, an application must publish an immutable archive copy so older versions cannot be altered during retention. “Object replication policy between compatible source and destination accounts” would not satisfy that requirement; the supported action is “A supported immutable blob policy for the retention requirement”. Blob immutability can enforce WORM-style retention on eligible containers or versions.

Storage services have distinct replication mechanisms and capabilities. In this case, an application must publish an immutable archive copy so older versions cannot be altered during retention. “Object replication targets eligible block blobs, not Azure Files shares” would not satisfy that requirement; the supported action is “A supported immutable blob policy for the retention requirement”. Blob immutability can enforce WORM-style retention on eligible containers or versions.

Storage Explorer offers interactive management of supported storage resources. In this case, an application must publish an immutable archive copy so older versions cannot be altered during retention. “Azure Storage Explorer” would not satisfy that requirement; the supported action is “A supported immutable blob policy for the retention requirement”. Blob immutability can enforce WORM-style retention on eligible containers or versions.

Storage services have distinct replication mechanisms and capabilities. In this case, a storage lifecycle rule tries to delete blobs during an active legal hold. “Object replication targets eligible block blobs, not Azure Files shares” would not satisfy that requirement; the supported action is “Immutability restrictions take precedence over ordinary lifecycle deletion”. Legal holds and retention policies protect data even from automatic management actions.

Storage Explorer offers interactive management of supported storage resources. In this case, a storage lifecycle rule tries to delete blobs during an active legal hold. “Azure Storage Explorer” would not satisfy that requirement; the supported action is “Immutability restrictions take precedence over ordinary lifecycle deletion”. Legal holds and retention policies protect data even from automatic management actions.

Repeatable bulk transfers are better served by scriptable tools than GUI clicks. In this case, a storage lifecycle rule tries to delete blobs during an active legal hold. “Use AzCopy or an appropriate Azure CLI/SDK automation” would not satisfy that requirement; the supported action is “Immutability restrictions take precedence over ordinary lifecycle deletion”. Legal holds and retention policies protect data even from automatic management actions.

Blob immutability can enforce WORM-style retention on eligible containers or versions. In this case, a business needs documents copied automatically from one Blob account to another. “A supported immutable blob policy for the retention requirement” would not satisfy that requirement; the supported action is “Object replication policy between compatible source and destination accounts”. Blob object replication asynchronously copies eligible blob updates under configured policies.

Archive is offline storage and imposes rehydration latency. In this case, a business needs documents copied automatically from one Blob account to another. “Archived blobs require rehydration before normal retrieval” would not satisfy that requirement; the supported action is “Object replication policy between compatible source and destination accounts”. Blob object replication asynchronously copies eligible blob updates under configured policies.

Cool maintains online access with different storage and transaction cost tradeoffs. In this case, a business needs documents copied automatically from one Blob account to another. “Cool access tier for infrequently accessed online blobs” would not satisfy that requirement; the supported action is “Object replication policy between compatible source and destination accounts”. Blob object replication asynchronously copies eligible blob updates under configured policies.

Cool maintains online access with different storage and transaction cost tradeoffs. In this case, a team enables object replication but expects Azure Files shares to copy too. “Cool access tier for infrequently accessed online blobs” would not satisfy that requirement; the supported action is “Object replication targets eligible block blobs, not Azure Files shares”. Storage services have distinct replication mechanisms and capabilities.

Archive is offline storage and imposes rehydration latency. In this case, a team enables object replication but expects Azure Files shares to copy too. “Archived blobs require rehydration before normal retrieval” would not satisfy that requirement; the supported action is “Object replication targets eligible block blobs, not Azure Files shares”. Storage services have distinct replication mechanisms and capabilities.

Blob immutability can enforce WORM-style retention on eligible containers or versions. In this case, a team enables object replication but expects Azure Files shares to copy too. “A supported immutable blob policy for the retention requirement” would not satisfy that requirement; the supported action is “Object replication targets eligible block blobs, not Azure Files shares”. Storage services have distinct replication mechanisms and capabilities.