zRS synchronously copies data across availability zones in one region. In this case, a low-cost test workload only needs copies within one datacenter. “Zone-redundant storage (ZRS) in a supported region” would not satisfy that requirement; the supported action is “Locally redundant storage (LRS)”. LRS maintains replicas within one physical location and does not protect against an entire datacenter loss.

gRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas. In this case, a low-cost test workload only needs copies within one datacenter. “Geo-redundant storage (GRS)” would not satisfy that requirement; the supported action is “Locally redundant storage (LRS)”. LRS maintains replicas within one physical location and does not protect against an entire datacenter loss.

read-access geo redundancy exposes the secondary endpoint for read scenarios while replication remains asynchronous. In this case, a low-cost test workload only needs copies within one datacenter. “Read-access geo-redundant storage such as RA-GRS” would not satisfy that requirement; the supported action is “Locally redundant storage (LRS)”. LRS maintains replicas within one physical location and does not protect against an entire datacenter loss.

LRS alone lacks paired-region geographic replication. In this case, a business requires asynchronous data replication to a paired region without secondary-read access or zone-level resiliency. “Locally redundant storage (LRS)” would not satisfy that requirement; the supported action is “Geo-redundant storage (GRS)”. GRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas.

ZRS protects zones within the primary region but not a secondary paired region. In this case, a business requires asynchronous data replication to a paired region without secondary-read access or zone-level resiliency. “Zone-redundant storage (ZRS)” would not satisfy that requirement; the supported action is “Geo-redundant storage (GRS)”. GRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas.

Blob versions are not an account-level secondary-region replication strategy. In this case, a business requires asynchronous data replication to a paired region without secondary-read access or zone-level resiliency. “Blob versioning without geo-redundant storage” would not satisfy that requirement; the supported action is “Geo-redundant storage (GRS)”. GRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas.

zRS synchronously copies data across availability zones in one region. In this case, a storage workload wants cross-zone protection in its primary region and a secondary-region copy. “Zone-redundant storage (ZRS) in a supported region” would not satisfy that requirement; the supported action is “Geo-zone-redundant storage (GZRS) where available”. GZRS combines primary-zone redundancy with asynchronous secondary-region replication.

gRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas. In this case, a storage workload wants cross-zone protection in its primary region and a secondary-region copy. “Geo-redundant storage (GRS)” would not satisfy that requirement; the supported action is “Geo-zone-redundant storage (GZRS) where available”. GZRS combines primary-zone redundancy with asynchronous secondary-region replication.

cross-region replication requires a geo-redundant option instead of ZRS alone. In this case, a storage workload wants cross-zone protection in its primary region and a secondary-region copy. “ZRS is zone redundancy within a single Azure region” would not satisfy that requirement; the supported action is “Geo-zone-redundant storage (GZRS) where available”. GZRS combines primary-zone redundancy with asynchronous secondary-region replication.

gRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas. In this case, an analytics service needs read access to secondary-region replicas without waiting for a disaster failover. “Geo-redundant storage (GRS)” would not satisfy that requirement; the supported action is “Read-access geo-redundant storage such as RA-GRS”. Read-access geo redundancy exposes the secondary endpoint for read scenarios while replication remains asynchronous.

gZRS combines primary-zone redundancy with asynchronous secondary-region replication. In this case, an analytics service needs read access to secondary-region replicas without waiting for a disaster failover. “Geo-zone-redundant storage (GZRS) where available” would not satisfy that requirement; the supported action is “Read-access geo-redundant storage such as RA-GRS”. Read-access geo redundancy exposes the secondary endpoint for read scenarios while replication remains asynchronous.

lRS maintains replicas within one physical location and does not protect against an entire datacenter loss. In this case, an analytics service needs read access to secondary-region replicas without waiting for a disaster failover. “Locally redundant storage (LRS)” would not satisfy that requirement; the supported action is “Read-access geo-redundant storage such as RA-GRS”. Read-access geo redundancy exposes the secondary endpoint for read scenarios while replication remains asynchronous.

gRS asynchronously replicates regional data to a secondary geography in addition to primary local replicas. In this case, a team's RPO requirement is zero for a full regional outage, and they propose ordinary GRS. “Geo-redundant storage (GRS)” would not satisfy that requirement; the supported action is “Asynchronous geo-replication can lose the latest unreplicated writes”. A regional failover to asynchronous secondary storage cannot guarantee zero data loss.

gZRS combines primary-zone redundancy with asynchronous secondary-region replication. In this case, a team's RPO requirement is zero for a full regional outage, and they propose ordinary GRS. “Geo-zone-redundant storage (GZRS) where available” would not satisfy that requirement; the supported action is “Asynchronous geo-replication can lose the latest unreplicated writes”. A regional failover to asynchronous secondary storage cannot guarantee zero data loss.

read-access geo redundancy exposes the secondary endpoint for read scenarios while replication remains asynchronous. In this case, a team's RPO requirement is zero for a full regional outage, and they propose ordinary GRS. “Read-access geo-redundant storage such as RA-GRS” would not satisfy that requirement; the supported action is “Asynchronous geo-replication can lose the latest unreplicated writes”. A regional failover to asynchronous secondary storage cannot guarantee zero data loss.

cross-region replication requires a geo-redundant option instead of ZRS alone. In this case, a workload needs predictable write latency and no regional disaster copy. “ZRS is zone redundancy within a single Azure region” would not satisfy that requirement; the supported action is “Use region-local redundancy sized to zone/downtime needs rather than defaulting to GRS”. Regional copies add resilience but do not necessarily improve primary write latency or match every workload's budget.

zRS synchronously copies data across availability zones in one region. In this case, a workload needs predictable write latency and no regional disaster copy. “Zone-redundant storage (ZRS) in a supported region” would not satisfy that requirement; the supported action is “Use region-local redundancy sized to zone/downtime needs rather than defaulting to GRS”. Regional copies add resilience but do not necessarily improve primary write latency or match every workload's budget.

gZRS combines primary-zone redundancy with asynchronous secondary-region replication. In this case, a workload needs predictable write latency and no regional disaster copy. “Geo-zone-redundant storage (GZRS) where available” would not satisfy that requirement; the supported action is “Use region-local redundancy sized to zone/downtime needs rather than defaulting to GRS”. Regional copies add resilience but do not necessarily improve primary write latency or match every workload's budget.

zRS synchronously copies data across availability zones in one region. In this case, an architect asks whether ZRS automatically creates a remote-region disaster copy. “Zone-redundant storage (ZRS) in a supported region” would not satisfy that requirement; the supported action is “ZRS is zone redundancy within a single Azure region”. Cross-region replication requires a geo-redundant option instead of ZRS alone.

regional copies add resilience but do not necessarily improve primary write latency or match every workload's budget. In this case, an architect asks whether ZRS automatically creates a remote-region disaster copy. “Use region-local redundancy sized to zone/downtime needs rather than defaulting to GRS” would not satisfy that requirement; the supported action is “ZRS is zone redundancy within a single Azure region”. Cross-region replication requires a geo-redundant option instead of ZRS alone.

read-access geo redundancy exposes the secondary endpoint for read scenarios while replication remains asynchronous. In this case, an architect asks whether ZRS automatically creates a remote-region disaster copy. “Read-access geo-redundant storage such as RA-GRS” would not satisfy that requirement; the supported action is “ZRS is zone redundancy within a single Azure region”. Cross-region replication requires a geo-redundant option instead of ZRS alone.

customer-managed encryption depends on access to the configured encryption key. In this case, a company needs customer-managed keys for supported storage encryption. “The storage identity's permissions to unwrap or use the active Key Vault key” would not satisfy that requirement; the supported action is “Azure Key Vault with suitable key access permissions”. Customer-managed storage encryption can use a key in Key Vault subject to identity and key permissions.

storage Explorer provides a graphical client for managing and transferring Azure Storage data. In this case, a company needs customer-managed keys for supported storage encryption. “Microsoft Azure Storage Explorer” would not satisfy that requirement; the supported action is “Azure Key Vault with suitable key access permissions”. Customer-managed storage encryption can use a key in Key Vault subject to identity and key permissions.

azure Storage encrypts data at rest and supports key-management choices based on service capabilities. In this case, a company needs customer-managed keys for supported storage encryption. “Storage service encryption at rest, configured with applicable key management” would not satisfy that requirement; the supported action is “Azure Key Vault with suitable key access permissions”. Customer-managed storage encryption can use a key in Key Vault subject to identity and key permissions.

available performance and redundancy choices vary by storage account and workload type. In this case, a storage account contains blobs that must be copied asynchronously into another account based on matching object rules. “The account's service type, performance tier and supported redundancy combination” would not satisfy that requirement; the supported action is “Blob object replication policies between supported accounts”. Object replication copies eligible block blob changes according to configured replication rules.

storage Explorer provides a graphical client for managing and transferring Azure Storage data. In this case, a storage account contains blobs that must be copied asynchronously into another account based on matching object rules. “Microsoft Azure Storage Explorer” would not satisfy that requirement; the supported action is “Blob object replication policies between supported accounts”. Object replication copies eligible block blob changes according to configured replication rules.

azure Storage encrypts data at rest and supports key-management choices based on service capabilities. In this case, a storage account contains blobs that must be copied asynchronously into another account based on matching object rules. “Storage service encryption at rest, configured with applicable key management” would not satisfy that requirement; the supported action is “Blob object replication policies between supported accounts”. Object replication copies eligible block blob changes according to configured replication rules.

storage Explorer provides a graphical client for managing and transferring Azure Storage data. In this case, a transfer engineer must upload many terabytes through a scripted, resumable copy process. “Microsoft Azure Storage Explorer” would not satisfy that requirement; the supported action is “AzCopy for supported Azure Storage bulk transfers”. AzCopy is designed for scalable command-line data transfer to and from Azure Storage services.

azure Storage encrypts data at rest and supports key-management choices based on service capabilities. In this case, a transfer engineer must upload many terabytes through a scripted, resumable copy process. “Storage service encryption at rest, configured with applicable key management” would not satisfy that requirement; the supported action is “AzCopy for supported Azure Storage bulk transfers”. AzCopy is designed for scalable command-line data transfer to and from Azure Storage services.

customer-managed storage encryption can use a key in Key Vault subject to identity and key permissions. In this case, a transfer engineer must upload many terabytes through a scripted, resumable copy process. “Azure Key Vault with suitable key access permissions” would not satisfy that requirement; the supported action is “AzCopy for supported Azure Storage bulk transfers”. AzCopy is designed for scalable command-line data transfer to and from Azure Storage services.

azCopy is designed for scalable command-line data transfer to and from Azure Storage services. In this case, a technician prefers GUI-based inspection and copying across storage resources. “AzCopy for supported Azure Storage bulk transfers” would not satisfy that requirement; the supported action is “Microsoft Azure Storage Explorer”. Storage Explorer provides a graphical client for managing and transferring Azure Storage data.

customer-managed storage encryption can use a key in Key Vault subject to identity and key permissions. In this case, a technician prefers GUI-based inspection and copying across storage resources. “Azure Key Vault with suitable key access permissions” would not satisfy that requirement; the supported action is “Microsoft Azure Storage Explorer”. Storage Explorer provides a graphical client for managing and transferring Azure Storage data.

customer-managed encryption depends on access to the configured encryption key. In this case, a technician prefers GUI-based inspection and copying across storage resources. “The storage identity's permissions to unwrap or use the active Key Vault key” would not satisfy that requirement; the supported action is “Microsoft Azure Storage Explorer”. Storage Explorer provides a graphical client for managing and transferring Azure Storage data.