Topic 05 Practice Test 1 covers Storage Accounts and Data Movement for Microsoft Azure Administrator AZ-104 and maps to the objective: Configure and manage storage accounts. For broader exam preparation, review the Microsoft AZ-104 Exam Dumps. Every option includes focused technical reasoning explaining both the Azure concept and its fit to the scenario.
Question 1
Contoso is building a general application platform that needs blobs, SMB file shares, queues, and tables in the same standard storage account. Which account type should the administrator create? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium FileStorage account
- Create a premium BlockBlobStorage account
- Use locally redundant storage (LRS)
Correct Answer: A
Correct Answer
Answer A is correct because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. The technical fit for Contoso is direct because the requirement is: one account must support the standard Blob, Files, Queue, and Table services.
Incorrect Answers
Answer B is incorrect because The Contoso design calls for this outcome: one account must support the standard Blob, Files, Queue, and Table services. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. This choice addresses another concern.
Answer C is incorrect because A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. That feature is valid Azure functionality, but The requirement for Contoso is: one account must support the standard Blob, Files, Queue, and Table services.
Answer D is incorrect because For Contoso, the required behavior is: one account must support the standard Blob, Files, Queue, and Table services. LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. That is not the behavior this scenario calls for.
Question 2
Fabrikam has a legacy general-purpose v1 account and wants current Azure Storage features while continuing to use multiple storage services. What should the administrator migrate to? Choose ONE.
- Create a premium FileStorage account
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium BlockBlobStorage account
- Use locally redundant storage (LRS)
Correct Answer: B
Correct Answer
Answer B is correct because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. For Fabrikam, that directly matches the stated requirement: one account must support the standard Blob, Files, Queue, and Table services.
Incorrect Answers
Answer A is incorrect because A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. It is not the appropriate selection for Fabrikam; the scenario requires: one account must support the standard Blob, Files, Queue, and Table services.
Answer C is incorrect because For Fabrikam, the deciding constraint is: one account must support the standard Blob, Files, Queue, and Table services. A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. This solves a different operational need.
Answer D is incorrect because LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. Even though the feature can be useful, it does not provide The required outcome for Fabrikam: one account must support the standard Blob, Files, Queue, and Table services.
Question 3
Northwind Traders needs a broadly supported standard storage account for application data without a premium-service-specific performance requirement. Which account kind is appropriate? Choose ONE.
- Create a premium FileStorage account
- Create a premium BlockBlobStorage account
- Create a standard general-purpose v2 (StorageV2) account
- Use locally redundant storage (LRS)
Correct Answer: C
Correct Answer
Answer C is correct because The required outcome for Northwind Traders is: one account must support the standard Blob, Files, Queue, and Table services. A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. This option provides that capability.
Incorrect Answers
Answer A is incorrect because A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. For Northwind Traders, however, that does not meet the stated requirement: one account must support the standard Blob, Files, Queue, and Table services.
Answer B is incorrect because A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. It misses the key condition in the Northwind Traders case: one account must support the standard Blob, Files, Queue, and Table services.
Answer D is incorrect because Northwind Traders must satisfy this condition: one account must support the standard Blob, Files, Queue, and Table services. LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. This option is aimed at another design goal.
Question 4
Adventure Works is standardizing new storage deployments and requires one account type that supports the mainstream Azure Storage services and modern feature set. What should it use? Choose ONE.
- Create a premium FileStorage account
- Create a premium BlockBlobStorage account
- Use locally redundant storage (LRS)
- Create a standard general-purpose v2 (StorageV2) account
Correct Answer: D
Correct Answer
Answer D is correct because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. The deciding condition in The Adventure Works scenario is: one account must support the standard Blob, Files, Queue, and Table services. This option fits that condition.
Incorrect Answers
Answer A is incorrect because The required outcome for Adventure Works is: one account must support the standard Blob, Files, Queue, and Table services. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. This capability does not satisfy that condition.
Answer B is incorrect because The requirement for Adventure Works is: one account must support the standard Blob, Files, Queue, and Table services. A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. The option therefore targets a different Azure capability.
Answer C is incorrect because LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. The mismatch for Adventure Works is the stated requirement: one account must support the standard Blob, Files, Queue, and Table services.
Question 5
Tailspin Toys runs a latency-sensitive line-of-business application over Azure Files and requires premium SSD-backed file shares. Which storage account type should it select? Choose ONE.
- Create a premium FileStorage account
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium BlockBlobStorage account
- Use zone-redundant storage (ZRS)
Correct Answer: A
Correct Answer
Answer A is correct because The key requirement for Tailspin Toys is: the workload specifically needs premium SSD-backed Azure file shares. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance.
Incorrect Answers
Answer B is incorrect because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. The Tailspin Toys scenario instead calls for this outcome: the workload specifically needs premium SSD-backed Azure file shares.
Answer C is incorrect because A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. This would not resolve the stated requirement for Tailspin Toys: the workload specifically needs premium SSD-backed Azure file shares.
Answer D is incorrect because In the Tailspin Toys case, the required result is: the workload specifically needs premium SSD-backed Azure file shares. ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. Selecting this would solve a neighboring problem instead.
Question 6
Woodgrove Bank is moving a high-IOPS SMB workload to Azure Files and the design calls for the premium file-share performance tier. What account type should be created? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium FileStorage account
- Create a premium BlockBlobStorage account
- Use zone-redundant storage (ZRS)
Correct Answer: B
Correct Answer
Answer B is correct because A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. This aligns with The Woodgrove Bank scenario, whose requirement is: the workload specifically needs premium SSD-backed Azure file shares.
Incorrect Answers
Answer A is incorrect because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. That feature is valid Azure functionality, but The requirement for Woodgrove Bank is: the workload specifically needs premium SSD-backed Azure file shares.
Answer C is incorrect because For Woodgrove Bank, the required behavior is: the workload specifically needs premium SSD-backed Azure file shares. A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. That is not the behavior this scenario calls for.
Answer D is incorrect because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. That does not line up with the stated constraint for Woodgrove Bank: the workload specifically needs premium SSD-backed Azure file shares.
Question 7
Proseware needs dedicated premium Azure Files performance rather than a general-purpose multi-service account. Which account type best matches the requirement? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium BlockBlobStorage account
- Create a premium FileStorage account
- Use zone-redundant storage (ZRS)
Correct Answer: C
Correct Answer
Answer C is correct because For Proseware, the technical constraint is: the workload specifically needs premium SSD-backed Azure file shares. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance.
Incorrect Answers
Answer A is incorrect because For Proseware, the deciding constraint is: the workload specifically needs premium SSD-backed Azure file shares. A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. This solves a different operational need.
Answer B is incorrect because A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. Even though the feature can be useful, it does not provide The required outcome for Proseware: the workload specifically needs premium SSD-backed Azure file shares.
Answer D is incorrect because The Proseware scenario is testing this requirement: the workload specifically needs premium SSD-backed Azure file shares. ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. This option does not provide that result.
Question 8
Litware is provisioning an NFS/SMB file workload whose storage design explicitly requires premium Azure Files. What storage account type should the administrator deploy? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium BlockBlobStorage account
- Use zone-redundant storage (ZRS)
- Create a premium FileStorage account
Correct Answer: D
Correct Answer
Answer D is correct because The Litware scenario turns on this requirement: the workload specifically needs premium SSD-backed Azure file shares. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. That makes this the appropriate choice.
Incorrect Answers
Answer A is incorrect because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. It misses the key condition in the Litware case: the workload specifically needs premium SSD-backed Azure file shares.
Answer B is incorrect because Litware must satisfy this condition: the workload specifically needs premium SSD-backed Azure file shares. A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. This option is aimed at another design goal.
Answer C is incorrect because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. Litware needs a different capability; the required result is: the workload specifically needs premium SSD-backed Azure file shares.
Question 9
Wingtip Toys has a transaction-heavy application that stores only block blobs and requires premium, consistently low storage latency. Which account type should it use? Choose ONE.
- Create a premium BlockBlobStorage account
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium FileStorage account
- Use locally redundant storage (LRS)
Correct Answer: A
Correct Answer
Answer A is correct because A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. The capability is relevant to Wingtip Toys because the required outcome is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Incorrect Answers
Answer B is incorrect because The requirement for Wingtip Toys is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. The option therefore targets a different Azure capability.
Answer C is incorrect because A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. The mismatch for Wingtip Toys is the stated requirement: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Answer D is incorrect because The Wingtip Toys design calls for this outcome: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. This choice addresses another concern.
Question 10
- Datum is designing a premium object-storage workload centered on block blobs with no Azure Files requirement. Which specialized account type is appropriate? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium BlockBlobStorage account
- Create a premium FileStorage account
- Use locally redundant storage (LRS)
Correct Answer: B
Correct Answer
Answer B is correct because The scenario for A. Datum requires this result: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. This directly addresses it.
Incorrect Answers
Answer A is incorrect because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. This would not resolve the stated requirement for A. Datum: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Answer C is incorrect because In the A. Datum case, the required result is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. Selecting this would solve a neighboring problem instead.
Answer D is incorrect because LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. It is not the appropriate selection for A. Datum; the scenario requires: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Question 11
Fourth Coffee requires high transaction rates for block blob objects and wants the premium block-blob service tier. What should the administrator create? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium FileStorage account
- Create a premium BlockBlobStorage account
- Use locally redundant storage (LRS)
Correct Answer: C
Correct Answer
Answer C is correct because A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. It is the suitable choice for Fourth Coffee; the deciding requirement is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Incorrect Answers
Answer A is incorrect because For Fourth Coffee, the required behavior is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. That is not the behavior this scenario calls for.
Answer B is incorrect because A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. That does not line up with the stated constraint for Fourth Coffee: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Answer D is incorrect because LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. For Fourth Coffee, however, that does not meet the stated requirement: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Question 12
Lucerne Publishing has a media metadata service that needs premium block blob performance and does not need queues, tables, or file shares. Which account type best fits? Choose ONE.
- Create a standard general-purpose v2 (StorageV2) account
- Create a premium FileStorage account
- Use locally redundant storage (LRS)
- Create a premium BlockBlobStorage account
Correct Answer: D
Correct Answer
Answer D is correct because For Lucerne Publishing, the required behavior is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. A BlockBlobStorage account is optimized for premium block blob workloads that need consistently low storage latency and high transaction rates rather than broad multi-service storage. That is why this option fits.
Incorrect Answers
Answer A is incorrect because A standard general-purpose v2 account is the recommended general-purpose account type and supports Blob, Files, Queue, and Table services with current Azure Storage features. Even though the feature can be useful, it does not provide The required outcome for Lucerne Publishing: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account.
Answer B is incorrect because The Lucerne Publishing scenario is testing this requirement: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. A FileStorage account is designed for premium Azure Files shares backed by SSD media and is appropriate when the workload specifically requires premium file-share performance. This option does not provide that result.
Answer C is incorrect because The required outcome for Lucerne Publishing is: the application requires premium low-latency block blob storage rather than file shares or a general-purpose standard account. LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. This capability does not satisfy that condition.
Question 13
Contoso must protect a storage account from the loss of one availability zone while keeping all replicas in the primary region. Which redundancy option should it configure? Choose ONE.
- Use zone-redundant storage (ZRS)
- Use locally redundant storage (LRS)
- Use geo-redundant storage (GRS)
- Use read-access geo-redundant storage (RA-GRS)
Correct Answer: A
Correct Answer
Answer A is correct because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. The technical fit for Contoso is direct because the requirement is: data must remain available after a datacenter or availability-zone failure inside the primary region.
Incorrect Answers
Answer B is incorrect because Contoso must satisfy this condition: data must remain available after a datacenter or availability-zone failure inside the primary region. LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. This option is aimed at another design goal.
Answer C is incorrect because GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. Contoso needs a different capability; the required result is: data must remain available after a datacenter or availability-zone failure inside the primary region.
Answer D is incorrect because RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover. The Contoso scenario instead calls for this outcome: data must remain available after a datacenter or availability-zone failure inside the primary region.
Question 14
Fabrikam has a regional application that does not require a secondary region but must survive a datacenter-level outage in a zone-enabled Azure region. What redundancy should it choose? Choose ONE.
- Use locally redundant storage (LRS)
- Use zone-redundant storage (ZRS)
- Use geo-redundant storage (GRS)
- Use read-access geo-redundant storage (RA-GRS)
Correct Answer: B
Correct Answer
Answer B is correct because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. For Fabrikam, that directly matches the stated requirement: data must remain available after a datacenter or availability-zone failure inside the primary region.
Incorrect Answers
Answer A is incorrect because LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. The mismatch for Fabrikam is the stated requirement: data must remain available after a datacenter or availability-zone failure inside the primary region.
Answer C is incorrect because The Fabrikam design calls for this outcome: data must remain available after a datacenter or availability-zone failure inside the primary region. GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. This choice addresses another concern.
Answer D is incorrect because RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover. That feature is valid Azure functionality, but The requirement for Fabrikam is: data must remain available after a datacenter or availability-zone failure inside the primary region.
Question 15
Northwind Traders wants synchronous copies across separate availability zones in the primary region. Which Azure Storage redundancy setting provides this behavior? Choose ONE.
- Use locally redundant storage (LRS)
- Use geo-redundant storage (GRS)
- Use zone-redundant storage (ZRS)
- Use read-access geo-redundant storage (RA-GRS)
Correct Answer: C
Correct Answer
Answer C is correct because The required outcome for Northwind Traders is: data must remain available after a datacenter or availability-zone failure inside the primary region. ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. This option provides that capability.
Incorrect Answers
Answer A is incorrect because In the Northwind Traders case, the required result is: data must remain available after a datacenter or availability-zone failure inside the primary region. LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. Selecting this would solve a neighboring problem instead.
Answer B is incorrect because GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. It is not the appropriate selection for Northwind Traders; the scenario requires: data must remain available after a datacenter or availability-zone failure inside the primary region.
Answer D is incorrect because For Northwind Traders, the deciding constraint is: data must remain available after a datacenter or availability-zone failure inside the primary region. RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover. This solves a different operational need.
Question 16
Adventure Works accepts a single-region design but not a single-datacenter failure domain. Which storage redundancy option meets that requirement? Choose ONE.
- Use locally redundant storage (LRS)
- Use geo-redundant storage (GRS)
- Use read-access geo-redundant storage (RA-GRS)
- Use zone-redundant storage (ZRS)
Correct Answer: D
Correct Answer
Answer D is correct because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. The deciding condition in The Adventure Works scenario is: data must remain available after a datacenter or availability-zone failure inside the primary region. This option fits that condition.
Incorrect Answers
Answer A is incorrect because LRS keeps multiple synchronous copies within one physical datacenter in the primary region, providing the lowest-cost redundancy but not protection from a datacenter-wide outage. That does not line up with the stated constraint for Adventure Works: data must remain available after a datacenter or availability-zone failure inside the primary region.
Answer B is incorrect because GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. For Adventure Works, however, that does not meet the stated requirement: data must remain available after a datacenter or availability-zone failure inside the primary region.
Answer C is incorrect because RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover. It misses the key condition in the Adventure Works case: data must remain available after a datacenter or availability-zone failure inside the primary region.
Question 17
Tailspin Toys uses geo-replication and wants reporting jobs to read the secondary region during normal operations. Which redundancy option should it configure? Choose ONE.
- Use read-access geo-redundant storage (RA-GRS)
- Use geo-redundant storage (GRS)
- Use geo-zone-redundant storage (GZRS)
- Use zone-redundant storage (ZRS)
Correct Answer: A
Correct Answer
Answer A is correct because The key requirement for Tailspin Toys is: the application must be able to read from the geo-replicated secondary endpoint before an account failover. RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover.
Incorrect Answers
Answer B is incorrect because The Tailspin Toys scenario is testing this requirement: the application must be able to read from the geo-replicated secondary endpoint before an account failover. GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. This option does not provide that result.
Answer C is incorrect because The required outcome for Tailspin Toys is: the application must be able to read from the geo-replicated secondary endpoint before an account failover. GZRS combines synchronous zone redundancy in the primary region with asynchronous replication to a secondary region, protecting against both zone and regional failures. This capability does not satisfy that condition.
Answer D is incorrect because The requirement for Tailspin Toys is: the application must be able to read from the geo-replicated secondary endpoint before an account failover. ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. The option therefore targets a different Azure capability.
Question 18
Woodgrove Bank requires asynchronous geo-replication plus a readable secondary storage endpoint without initiating failover. What should the administrator select? Choose ONE.
- Use geo-redundant storage (GRS)
- Use read-access geo-redundant storage (RA-GRS)
- Use geo-zone-redundant storage (GZRS)
- Use zone-redundant storage (ZRS)
Correct Answer: B
Correct Answer
Answer B is correct because RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover. This aligns with The Woodgrove Bank scenario, whose requirement is: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
Incorrect Answers
Answer A is incorrect because GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. Woodgrove Bank needs a different capability; the required result is: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
Answer C is incorrect because GZRS combines synchronous zone redundancy in the primary region with asynchronous replication to a secondary region, protecting against both zone and regional failures. The Woodgrove Bank scenario instead calls for this outcome: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
Answer D is incorrect because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. This would not resolve the stated requirement for Woodgrove Bank: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
Question 19
Proseware has chosen geo-redundant storage but now needs direct read access to the secondary endpoint for a read-only continuity process. Which option should replace GRS? Choose ONE.
- Use geo-redundant storage (GRS)
- Use geo-zone-redundant storage (GZRS)
- Use read-access geo-redundant storage (RA-GRS)
- Use zone-redundant storage (ZRS)
Correct Answer: C
Correct Answer
Answer C is correct because For Proseware, the technical constraint is: the application must be able to read from the geo-replicated secondary endpoint before an account failover. RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover.
Incorrect Answers
Answer A is incorrect because The Proseware design calls for this outcome: the application must be able to read from the geo-replicated secondary endpoint before an account failover. GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. This choice addresses another concern.
Answer B is incorrect because GZRS combines synchronous zone redundancy in the primary region with asynchronous replication to a secondary region, protecting against both zone and regional failures. That feature is valid Azure functionality, but The requirement for Proseware is: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
Answer D is incorrect because For Proseware, the required behavior is: the application must be able to read from the geo-replicated secondary endpoint before an account failover. ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. That is not the behavior this scenario calls for.
Question 20
Litware wants a storage redundancy design with a primary region and a paired secondary region that applications can query for reads. Which option provides the secondary read endpoint? Choose ONE.
- Use geo-redundant storage (GRS)
- Use geo-zone-redundant storage (GZRS)
- Use zone-redundant storage (ZRS)
- Use read-access geo-redundant storage (RA-GRS)
Correct Answer: D
Correct Answer
Answer D is correct because The Litware scenario turns on this requirement: the application must be able to read from the geo-replicated secondary endpoint before an account failover. RA-GRS adds a readable secondary endpoint to geo-redundant replication, allowing applications to read from the secondary region without waiting for a failover. That makes this the appropriate choice.
Incorrect Answers
Answer A is incorrect because GRS keeps redundant copies in the primary region and asynchronously replicates data to a paired secondary region, but the secondary endpoint is not readable during normal operation. It is not the appropriate selection for Litware; the scenario requires: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
Answer B is incorrect because For Litware, the deciding constraint is: the application must be able to read from the geo-replicated secondary endpoint before an account failover. GZRS combines synchronous zone redundancy in the primary region with asynchronous replication to a secondary region, protecting against both zone and regional failures. This solves a different operational need.
Answer C is incorrect because ZRS synchronously copies data across three or more availability zones in the primary region, protecting the account from a zone or datacenter failure within that region. Even though the feature can be useful, it does not provide The required outcome for Litware: the application must be able to read from the geo-replicated secondary endpoint before an account failover.
