AZ-104 Practice Question 24: Object Replication Read Locality
Microsoft Azure Administrator Associate (AZ-104) · Test 3 · question 4 of 10
A media team in Singapore reads reference images from stmediauk, a general-purpose v2 account in UK South, and the read latency is hurting them. New images are uploaded to the UK account continuously and must appear in a Southeast Asia account automatically; a few minutes of lag is acceptable. The UK account must remain the only place anyone writes to.
You create stmediaasia in Southeast Asia. What should you configure, and what must be enabled for it to work?
Show answer and explanation
Answer:
Object replication "asynchronously copies block blobs between a source storage account and a destination account," and the first scenario Microsoft lists for it is to "minimize latency ... by enabling clients to consume data from a region in closer physical proximity." The prerequisites are precise and commonly missed: change feed enabled on the source account, and blob versioning "enabled on both the source and destination accounts." It also fits the write constraint for free; once the policy is active, "write operations to the destination container aren't permitted" and fail with error code 409.
Option A gives the wrong kind of secondary. The RA-GZRS secondary lives in the *paired* region of UK South, not in Southeast Asia, so it does not put the data near Singapore; it is a durability and outage-read feature, not a data-placement one.
Option C is a bolt-on for a platform feature. AzCopy is the right tool for a one-off or scripted bulk copy, but a cron job with an agent to babysit brings its own failure modes, and every run must enumerate the container to find what changed.
Option D targets a different service. Azure File Sync synchronises SMB file shares with Windows Servers; it does not replicate block blobs between storage accounts, and a file share has only one cloud endpoint.
Reference: Object replication for block blobs