Courseiva
Implement and Manage StorageeasyMultiple ChoiceObjective-mapped

AZ-104 Implement and Manage Storage Practice Question

A finance team stores monthly reports in Azure Blob Storage. The data must remain available if one datacenter in the Azure region fails, but the company does not need read access from a secondary region. Which redundancy option should the administrator choose?

⚠ Common exam trap

Many exam-takers choose GRS or RA-GRS because they assume any datacenter failure requires a secondary region, but ZRS within a single region is sufficient and more cost-effective when only one datacenter (zone) fails and secondary read access is not needed.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Zone-redundant storage (ZRS)

Zone-redundant storage (ZRS) replicates data synchronously across three Azure availability zones within a single region, ensuring durability even if one datacenter (zone) fails. Since the requirement specifies no need for read access from a secondary region, ZRS meets the high-availability need without the cost or complexity of geo-replication.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Locally redundant storage (LRS)

    Why it's wrong here

    Locally redundant storage (LRS) maintains three synchronous replicas within a single physical datacenter in one availability zone. This protects against drive and server failures but not against a datacenter-wide event such as a fire or flood, so an entire zone outage could cause data loss. Since the requirement expects resilience at the zone level, LRS fails to meet the stated availability need.

    When this WOULD be correct

    LRS would be correct if the question specified that the data must remain available only if a single server or storage node fails, and the company does not need protection against a datacenter-level failure. For example: 'A company stores temporary log files that can be regenerated; cost is the primary concern.'

  • Zone-redundant storage (ZRS)

    Why this is correct

    Zone-redundant storage (ZRS) replicates your data synchronously across three Azure availability zones within the same region. This design provides high availability even if an entire datacenter or availability zone fails, because copies remain in other zones. Since the requirement is in-region availability rather than geo-redundancy, ZRS is the optimal choice—it delivers the needed resilience without adding a secondary region.

  • Geo-redundant storage (GRS)

    Why it's wrong here

    Geo-redundant storage (GRS) asynchronously replicates your data to a paired secondary region, but it does not provide read access to that secondary copy unless failover occurs. While this protects against a region-wide disaster, it is more than the requirement demands; the finance team only needs availability within a single region. Choosing GRS adds cross-region dependencies and billing costs without answering the immediate availability question, so it is not the right fit.

    When this WOULD be correct

    A company requires data to remain available even if an entire Azure region fails, and they need the ability to read data from the secondary region only after Microsoft initiates a failover (no read access during normal operations).

  • Read-access geo-redundant storage (RA-GRS)

    Why it's wrong here

    Read-access geo-redundant storage (RA-GRS) replicates data asynchronously to a paired secondary region and additionally grants read access to that replica. The question explicitly does not require read access from a secondary region, so choosing RA-GRS would introduce unnecessary geo-replication overhead, higher cost, and a more complex failover design. Even though RA-GRS offers strong durability, it goes beyond the stated scope, making it an incorrect selection.

    When this WOULD be correct

    A company requires data to remain available during a region-wide outage and needs read-only access to the secondary region for disaster recovery or compliance purposes. For example, a global application that must serve read requests from a secondary region if the primary fails.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Zone-redundant storage (ZRS)Correct answer

Why this is correct

Zone-redundant storage (ZRS) replicates your data synchronously across three Azure availability zones within the same region. This design provides high availability even if an entire datacenter or availability zone fails, because copies remain in other zones. Since the requirement is in-region availability rather than geo-redundancy, ZRS is the optimal choice—it delivers the needed resilience without adding a secondary region.

Locally redundant storage (LRS)Wrong answer — click to see why

Why this is wrong here

LRS replicates data three times within a single datacenter, so it does not protect against a full datacenter failure. The question requires availability if one datacenter fails, which ZRS provides by replicating across multiple availability zones within the region.

★ When this WOULD be the correct answer

LRS would be correct if the question specified that the data must remain available only if a single server or storage node fails, and the company does not need protection against a datacenter-level failure. For example: 'A company stores temporary log files that can be regenerated; cost is the primary concern.'

Why candidates choose this

Candidates may confuse 'datacenter failure' with 'server failure' and think LRS provides sufficient redundancy, or they may focus on the 'no read access from secondary region' requirement and incorrectly assume LRS is the cheapest option that meets that condition.

Geo-redundant storage (GRS)Wrong answer — click to see why

Why this is wrong here

Geo-redundant storage (GRS) replicates data to a secondary region, which provides read access from the secondary region only after a failover. The question states the company does not need read access from a secondary region, making GRS unnecessary and more expensive than ZRS.

★ When this WOULD be the correct answer

A company requires data to remain available even if an entire Azure region fails, and they need the ability to read data from the secondary region only after Microsoft initiates a failover (no read access during normal operations).

Why candidates choose this

Candidates may confuse 'geo-redundant' with 'zone-redundant' and think GRS provides higher durability, but they overlook the specific requirement of not needing read access from a secondary region.

Read-access geo-redundant storage (RA-GRS)Wrong answer — click to see why

Why this is wrong here

RA-GRS provides read access to a secondary region, but the question explicitly states the company does not need read access from a secondary region. Additionally, RA-GRS is more expensive and complex than ZRS, which meets the requirement of surviving a datacenter failure within a region.

★ When this WOULD be the correct answer

A company requires data to remain available during a region-wide outage and needs read-only access to the secondary region for disaster recovery or compliance purposes. For example, a global application that must serve read requests from a secondary region if the primary fails.

Why candidates choose this

Candidates may confuse 'geo-redundant' with 'zone-redundant' and think RA-GRS offers higher availability, or they may overlook the 'no read access from secondary' constraint and assume geo-redundancy is always better.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

Azure Blob Storage Tier Comparison

TierStorage CostRetrieval CostLatencyUse Case
HotHighestLowestImmediateActive data, frequent reads
CoolLowerHigherImmediateData accessed < once / month
ColdLower stillHigherImmediateData accessed < once / quarter
ArchiveLowestHighest + rehydration delayHoursLong-term compliance retention

About these practice questions

One of 1,049 original AZ-104 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.