A storage account is configured for geo-redundant storage. During a regional incident a developer tries to read the secondary copy directly and cannot. What is the explanation?
Microsoft Certified: Azure Fundamentals (AZ-900), objective architecture-and-services. Azure architecture and services medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Correct With plain geo-redundant storage the secondary copy is not readable; reading it requires the read-access variant, or a failover to that region
Correct. Plain geo-redundancy keeps the second copy for recovery, not for serving traffic. The read-access variant exists precisely because some designs want to read it.
Not correct The secondary is readable, so this must be a role assignment problem
Wrong diagnosis. A missing role assignment produces an authorisation failure, but here the behaviour is by design: without read access enabled there is no secondary endpoint to authorise against.
Not correct Geo-redundant replication runs once a night, so today's data has not arrived yet
Wrong. Replication to the secondary region is asynchronous but continuous, not a nightly batch. Asynchronous does mean the very latest writes may not have landed, which is what a recovery point objective describes.
Not correct Geo-redundant storage keeps the second copy in the same region, so there is nothing elsewhere to read
Wrong. Geo-redundancy means the secondary lives in the paired region; keeping copies within one region is what the local and zone options do.
Why
Redundancy and readability are separate settings. Geo-redundant storage guarantees a durable second copy in the paired region; read access to that copy is an option you turn on, giving you a second read-only endpoint at the secondary region's address. Designs that plan to serve reads from the secondary during an incident must choose the read-access variant deliberately, and must tolerate data that may be slightly behind.
Where this comes from
- Cited
- Microsoft AZ-900 study guide skill area architecture-and-services.storage
Practise this
Reading one question is not practice. The trainer will draw a set from objective architecture-and-services and space the ones you get wrong.
Practise Microsoft Certified: Azure Fundamentals (AZ-900)
More questions on this objective
- An image-resizing routine runs for about two seconds whenever a file lands in a storage container — perhaps two hundred times on a busy day, and not at all on a quiet one. The team wants to pay for the work done and maintain no servers. Which compute option fits? machine-checked
- A fifteen-year-old accounting application needs a kernel-level driver, a scheduled task that edits the registry, and a runtime version nobody supports any more. The business wants it running in Azure this quarter with as few code changes as possible. Where does it go? machine-checked
- A team runs nine small services, each with its own conflicting library versions. They want each one packaged with its dependencies, starting in seconds, several to a host, without a separate operating system per service. Which compute type are they describing? machine-checked
- Which TWO of these statements about Azure compute types are true? machine-checked
- A public website runs on four identical virtual machines behind a load balancer. Traffic triples while a television advert airs and falls back an hour later. The team wants instances added and removed automatically against CPU, all built from one image, with nobody clicking. Which option is designed for that? machine-checked
- Three virtual machines form a quorum-based cluster in a region that has no availability zones. You want them placed so that neither a single rack losing power nor a single batch of planned host maintenance can take all three at once. What do you configure? machine-checked