A dataset must survive the loss of one datacentre in its primary region without anybody performing a failover, and regulation forbids a copy of it leaving that region. Which redundancy option meets both requirements?
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 Zone-redundant storage
Correct. It writes three copies synchronously across three availability zones inside the primary region, so losing one zone is transparent to the application and nothing leaves the region.
Not correct Locally redundant storage
Wrong. It keeps three copies, but all of them inside a single datacentre, so the one failure the requirement names takes all three at once.
Not correct Geo-redundant storage
Wrong on residency. It copies the data asynchronously to the paired region — precisely the copy leaving the region that regulation forbids — and recovering from that copy involves a failover rather than being transparent.
Not correct Read-access geo-redundant storage
Wrong for the same reason as geo-redundant storage, and it widens the problem: the out-of-region copy is now readable, so there is more of the thing the regulator objected to, not less.
Why
Count the copies, then ask where they are. Locally redundant keeps three in one datacentre; zone-redundant spreads three across zones in the region, written synchronously; geo-redundant adds an asynchronous copy in the paired region; geo-zone-redundant combines both. The synchronous-versus-asynchronous distinction matters as much as the geography: in-region replication is complete before the write is acknowledged, cross-region replication is not, so a regional failover can lose the most recent writes.
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