AZ-305 Practice Question 97: VMSS Flexible Zone Spread
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 10 · question 7 of 10
A design calls for a stateful application tier that must keep running if an entire Azure availability zone in the region becomes unavailable. The team wants Azure to automatically spread newly created and replaced instances across the zones in the region, wants to be able to attach and detach individual virtual machines from the group, and wants each instance to be individually addressable rather than treated as an identical, interchangeable clone. Which compute design meets these requirements?
Show answer and explanation
Answer:
Flexible orchestration mode spreads virtual machine instances across availability zones or fault domains in a region, supports mixing instance types and individually addressable, stateful virtual machines, and allows attaching or detaching specific VMs from the scale set, all of which the scenario requires.
Option A is wrong because Uniform mode treats instances as identical, interchangeable clones from a single model and is a poor fit for individually addressable stateful instances, and selecting only one zone provides no protection if that zone fails. Option C is wrong because an availability set protects against a rack or hardware failure inside a single datacenter, not a zone-wide outage, since fault domains do not span availability zones. Option D is wrong because individually created virtual machines with no scale set require manual effort to keep spread across zones and to replace a failed instance, which is exactly the automation the requirement asks for.
Reference: Orchestration modes for Virtual Machine Scale Sets in Azure