HOTSPOT -
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 virtual machine named VM1, and then add VM1 to VMSS1.
Which resource group and location should you use to deploy VM1? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
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.
Box 2: West US only -
Note: Virtual machine scale sets will support 2 distinct orchestration modes:
ScaleSetVM ג€" Virtual machine instances added to the scale set are based on the scale set configuration model. The virtual machine instance lifecycle - creation, update, deletion - is managed by the scale set.
VM (virtual machines) ג€" Virtual machines created outside of the scale set can be explicitly added to the scaleset.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview
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
Completely agree even if it say "Should" you use. TO be honest, I wanted to asnwer different because I think I should use "RG1 only" except if there is a good reason behind (cost / department / etc) and so to have all my VM in the same RG for easier management.
Yes you can use any RG, but here it asks what RG you SHOULD use? That sounds like by this question Microsoft encourages us to follow their recommendations, and the answer should be RG1 only.
superb
Box 1: RG1 only. The VM must be in the same resource group as the scale set. Reference : https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-attach-detach-vm?tabs=portal
you are right!
Yes, RG1 only. "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#exceptions-to-attaching-a-vm-to-a-virtual-machine-scale-set
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 )
Answer is not correct. I just tested it in the lab and a new VM needed to be in the SAME resource group and region. Otherwise, a given VMSS was not available.
Not sure how you tested it...Did you consult Bill Gates!! Anyway the VMSS set should and would be available as long as you are in the right subscription, it will give you option to chose the resource group then you can chose the VMSS. Just remember this RG and Subscriptions ONLY hold the meta data of the resources, what matters is the region
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
same region = RG1 and West US
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
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.
Question asks,"Which resource group and location should you use to deploy VM1? " not "can". So it should be RG1.Isn't it?
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
More details/additional info: • Virtual Machines Scale Sets provide a logical grouping of platform-managed virtual machines. • With scale sets, you create a virtual machine configuration model, automatically add or remove additional instances based on CPU or memory load, and automatically upgrade to the latest OS version. • Traditionally, scale sets allow you to create virtual machines using a VM configuration model provided at the time of scale set creation, and the scale set can only manage virtual machines that are implicitly created based on the configuration model. • Scale set orchestration modes allow you to have greater control over how virtual machine instances are managed by the scale set. There are 2 modes- Uniform & Flexible
• Virtual Machine Scale Sets with Uniform orchestration use a virtual machine profile or template to scale up to desired capacity. While there is some ability to manage or customize individual virtual machine instances, Uniform uses identical VM instances. • Flexible orchestration : o Allows to mix DIFFERENT virtual machine types or Spot and on-demand VMs together o offers high availability guarantees by spreading VMs across fault domains in a region or within an Availability Zone (Uniform works within same AZ) o You can only attach new VMs (non identical) to a Virtual Machine Scale Set in Flexible orchestration mode.
"should" is the word. Not "can". Best practice is to put the VM in a scale set in the same resource group. Answer is A and C
Given answer is correct.. RG holds the meta data of resources and hence its location dont matter but Resources should mostly be in same region and in this case the VM and the VMSS MUST be in same region
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.
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.
Creating virtual machines in virtual machine scale set is only allowed for scale sets with flexible orchestration mode. When you create a VM, you can optionally specify that it is added to a virtual machine scale set. A VM can only be added to a scale set at time of VM creation. The newly created VM must be in the same resource group as the Flexible scale set regardless of deployment methods. Tested in the lab. https://docs.microsoft.com/en-us/azure/virtual-machines/flexible-virtual-machine-scale-sets
If the location is "West US", should not it also determine the resource group, which is RG2, and not RG1, RG2, or RG3? Because a resource group uses a location too.
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.
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
In exam today, go with highly voted
Given answer is correct