Cascade Regional Airlines' crew-scheduling application scales a pool of worker VMs up and down constantly inside its own VNet, and the platform team wants each new VM to automatically get a resolvable DNS A record in the linked private DNS zone the moment it's created, without any manual record entry. Which private DNS zone setting achieves this?

Enabling autoregistration on a private DNS zone's virtual network link makes Azure automatically create an A record (and a corresponding PTR record if reverse lookup is configured) for every VM's primary network interface in that linked VNet, and automatically remove the record when the VM is deleted — exactly the hands-off behavior needed for a frequently scaling worker pool. A resolution-only virtual network link, by contrast, lets VMs in that VNet query existing records in the zone but does nothing to create records for VMs automatically; without autoregistration also enabled, each new worker VM would need a manually created record. A public zone delegation is a completely different concept involving internet-facing NS records at a domain registrar and has no bearing on private, VNet-internal name creation. A Traffic Manager priority routing method governs global failover between separate endpoints and has nothing to do with per-VM DNS record creation inside a VNet. The exam-relevant caveat: autoregistration only creates records for VMs, not for other resource types like load balancers or App Services, so those still require manually created records in the same zone if they need to be resolvable. To verify, provision a new worker VM in the linked VNet and confirm an A record matching its hostname appears automatically in the private DNS zone's record set shortly afterward.