Your storage account replicates to its region's pair. A compliance reviewer asks what pairing actually guarantees about where the second copy sits, and about how Microsoft applies planned platform updates. Which answer is accurate?

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 The paired region normally sits in the same geography, and Microsoft rolls planned platform updates out to one region of a pair at a time

Correct. Staying inside the geography is what keeps data-residency commitments intact after a failover, and staged maintenance means a bad platform update cannot hit both halves of a recovery plan in the same window.

Not correct The paired region is in the same city, so latency between the two matches latency inside a region

Wrong, and it would defeat the purpose. Pairs are deliberately separated by distance so that one flood, fire or power event is unlikely to reach both — and that distance costs latency, which is why cross-region replication is asynchronous.

Not correct The pair is whichever region you nominate when you create the resource

Wrong. Pairing is fixed by Microsoft for each region; it is not a per-resource setting. What you choose is whether to use a geo-redundant option at all.

Not correct Updates are applied to both regions of a pair simultaneously so their software versions never diverge

Wrong. Simultaneous updates are the exact failure mode pairing exists to avoid. A faulty rollout would then land on your primary and your recovery target at the same moment.

Why

Region pairing buys two distinct things: distance, so a regional disaster is unlikely to reach both halves, and staged platform maintenance, so an update lands in one region while the other keeps running. Pairs sit inside the same geography so residency commitments survive a failover — Brazil South is the well-known exception, since its pair lies in another geography. You do not choose the pair, only whether to use it.

Where this comes from

Cited
Microsoft AZ-900 study guide skill area architecture-and-services.core-architectural-components

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

All questions on Azure architecture and services