Exam AZ-104 topic 5 question 31 discussion

Correct Answer: Box 1: RG1, RG2, or RG3 The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. The location of the RG doesn't influence the choice of the location of VM. best practice would be to create the VM1 in the RG1 because the scale set is in RG1. And Microsoft recommends that resources contained in a Resource Group share the same resource lifecycle. Box 2: West US only You can add the virtual machine to a scale set in the same region, zone, and resource group. Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes

Answer is correct. The location of the RG doesn't influence the choice of the location of VM. The location of the VM should be the same like the VM Scale set (single zone or zone redundant )

RG1 (https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-attach-detach-vm?tabs=portal) West US only You can add the virtual machine to a scale set in the same region, zone, and resource group

CORRECT

Just tried this on the portal. vmss that had been created can't even be seen as a choice if i change the RG to RG1 &2. the same goes for location. answers are : -RG1 only -West US only

Limitations for attaching an existing Virtual Machine to a scale set The scale set must use Flexible orchestration mode. The scale set must have a platformFaultDomainCount of 1. The VM and scale set must be in the same resource group. The VM and target scale set must both be zonal, or they must both be regional. You can't attach a zonal VM to a regional scale set. The VM can't be in a self-defined availability set. The VM can't be in a ProximityPlacementGroup. The VM can't be in an Azure Dedicated Host. The VM must have a managed disk. The scale set must have singlePlacementGroup set to False. Scale sets created without a scaling profile default to singlePlacementGroup set to null. To attach VMs to a scale set without a scaling profile, singlePlacementGroup needs to be set to False at the time of the scale set's creation. The VM can't be a Remote Direct Memory Access (RDMA) capable HB-series or N-series VM.

Given answer is correct

ANSWER= RG1 only (same RG as VMSS), West US only (same Region as VMSS) You can only attach new VMs (non identical) to a Virtual Machine Scale Set in Flexible orchestration mode. NOTES: -The VM must be in the same resource group as the scale set. -If the scale set is regional (no availability zones specified), the virtual machine must also be regional. <and both VM and VMSS must be in same region> -If the scale set is zonal or spans multiple zones (one or more availability zones specified), the virtual machine must be created in one of the zones spanned by the scale set. For example, you can't create a virtual machine in Zone 1, and place it in a scale set that spans Zones 2 and 3. https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-attach-detach-vm?tabs=portal-1%2Cportal-2%2Cportal-3#exceptions-to-attaching-a-new-vm-to-a-virtual-machine-scale-set

Answer is: - Resource group: RG1 only - Location: West US You can only attach VMs to a Virtual Machine Scale Set in Flexible orchestration mode. The VM must be in the same resource group as the scale set. If the scale set is regional (no availability zones specified), the virtual machine must also be regional. https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-attach-detach-vm?tabs=portal

The VM must be in the same resource group as the scale set. --> https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-attach-detach-vm?tabs=portal#exceptions-to-attaching-a-vm-to-a-virtual-machine-scale-set So the answer is Box 1: RG1 only Box 2: West US only

Focus on the "should" like others have. Following MS url below; https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/overview So for Box 1; It can be R1, RG2, RG3, but should be RG1. For Box 2; Should be in West US.

The question is poorly written. "Should" is a very ambiguous term. The VM can be created in any RG, but best practices tell us that it should be done in RG1 to have similar lifecycle. So, in theory, both RG1 only and R1,2,3 should be correct answers.

Question asks,"Which resource group and location should you use to deploy VM1? " not "can". So it should be RG1.Isn't it?

In exam today, go with highly voted

Tested in lab with this result: Resource group: RG1 only Location: West US Only When you are going to create de vm1 you can read this: You can add your virtual machine to a virtual machine scale set to design highly available and scalable application architecture. Virtual machines inside a scale set can be deployed into fault domains or Availability zones. The scale set must be set to flexible orchestration mode, and in the same region and resource group.

Correct Answer: Box 1: RG1, RG2, or RG3 The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. The location of the RG doesn't influence the choice of the location of VM. best practice would be to create the VM1 in the RG1 because the scale set is in RG1. And Microsoft recommends that resources contained in a Resource Group share the same resource lifecycle. Box 2: West US only You can add the virtual machine to a scale set in the same region, zone, and resource group. Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes

I can see it both ways. But they gave us all three RGs as a choice together. Tough call, and for MSFT's part not "fair". They need more context or a better word.