AZ-104 · Question #354
Hotspot Question You have an Azure subscription that contains the resources shown in the following table. VMSS1 is set to VM (virtual machines) orchestration mode. You need to deploy a new Azure virtu
The correct answer is Resource group: RG1; Location: West US. This question tests knowledge of Azure Virtual Machine Scale Sets (VMSS) in VM orchestration mode, specifically the constraints around resource group and location when adding existing VMs to a VMSS.
Question
Exhibits
Answer Area
- Resource groupRG1RG1RG2RG3
- LocationWest USCentral USWest USEast US
Explanation
This question tests knowledge of Azure Virtual Machine Scale Sets (VMSS) in VM orchestration mode, specifically the constraints around resource group and location when adding existing VMs to a VMSS.
Approach. When using VMSS in VM (Flexible) orchestration mode, any VM you want to add to the scale set must reside in the SAME resource group and the SAME Azure region (location) as the VMSS itself. Therefore, VM1 must be deployed into the resource group that contains VMSS1 and in the same location/region where VMSS1 is deployed. This is a hard requirement - Azure does not allow cross-resource-group or cross-region membership in a VM orchestration mode scale set. You would look at the table provided, identify the resource group and location of VMSS1, and select those same values for VM1.
Concept tested. Azure Virtual Machine Scale Sets in VM (Flexible) orchestration mode require that any member virtual machine be deployed in the same resource group and same Azure region as the scale set itself. Unlike Uniform orchestration mode where VMs are managed internally, Flexible/VM mode allows attaching existing VMs, but they must share the same resource group and location as the VMSS.
Topics
Community Discussion
No community discussion yet for this question.

