You need to run a stateless web workload on Azure virtual machines and automatically increase or decrease instance count based on demand. You also want a single management boundary for the VM instances. Which solution should you deploy?
VM Scale Sets support group management and autoscaling for identical VM instances.
Why this answer
A Virtual Machine Scale Set (VMSS) is the correct solution because it provides an autoscaling group of identical VMs that can automatically increase or decrease instance count based on demand (e.g., CPU or memory metrics). It also offers a single management boundary, allowing you to manage, monitor, and scale all instances as a unified resource rather than individually.
Exam trap
The trap here is that candidates often confuse an availability set (which provides high availability but no scaling) with a Virtual Machine Scale Set (which provides both scaling and a single management boundary), or they mistakenly think backup/recovery services can manage compute scaling.
How to eliminate wrong answers
Option B is wrong because an availability set with individual VMs does not provide autoscaling; it only ensures high availability by distributing VMs across fault domains and update domains, but each VM must be managed separately and scaled manually. Option C is wrong because Azure Backup is a data protection service for backing up VMs, files, and workloads; it has no capability to manage compute scaling or instance count. Option D is wrong because a Recovery Services vault is used for backup and disaster recovery (e.g., Azure Site Recovery), not for deploying or autoscaling compute instances.