Exam AZ-104 topic 4 question 31 discussion

Answer is correct (D). the main idea is to create 5 VMs asap. To do this you should let Azure do it for you with the least steps. either by using ARM template which is not mentioned here or VM scale set. That leaves us with 2 options C or D. C is like unmanaged Scale set where you add the VMs manually to the scale set as a unmanaged group. while D is managed scale set by Azure where it is based on configuration set during the setup of the VM Scale set

Correct Answer: D ScaleSetVM orchestration mode: 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. It the current default VMSS behavior. (Scale set VMs are created in a single shot). VM (virtual machines) orchestration mode: Virtual machines created outside of the scale set can be explicitly added to the scale set. The orchestration mode VM will only create an empty VMSS without any instances, and you will have to manually add new VMs into it by specifying the VMSS ID during the creation of the VM. (Separately VMs are created and added to scale set later) Reference: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/orchestration-modes

D is corerct

Exam Topic admin, Please remove the outdated questions and information not only here. Many of the questions have outdated information and wrong answers.It is very confusing. I studied Azure from some tutorials and never came across orchestration mode as ScaleSetVM As per the below link only Uniform and Flexible exists https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes Please correct me if wrong. Sorry if this caused any inconvenience to any of you here

D is correct because it specifically supports the deployment and management of a set of identical, load-balanced VMs, which is what a scale set requires for efficient scaling and management.

D is correct

Outdated question. Now it's called: - Scale sets with Uniform orchestration - Scale sets with Flexible orchestration https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes

NAME HAS BEEN CHNAGED NEW NAME IS SOMTHING LIKE THIS FLEXIBLE ORCHESTRATION == VM ORCHASTRATION MODE UNIFORM ORCHESTRATION == SCALESETVM ORCHASTRATION MODE Answer according to this will be Uniform Orchastration Mode

To deploy multiple virtual machine instances as quickly as possible, you should use a virtual machine scale set. Between the given options regarding virtual machine scale sets and their orchestration mode: - VM (virtual machines) orchestration mode allows you to manage each instance of a virtual machine as a separate entity. This is mainly used for situations where you want to customize the instances individually. - ScaleSetVM orchestration mode (the default mode) treats the instances in the scale set as a set, making it easier to manage them as a group, which is ideal for deploying multiple instances quickly. Therefore, the answer is: D. Deploy one virtual machine scale set that is set to ScaleSetVM orchestration mode.

Outdated terminology. Today, the correct answer will be "Uniform Orchestration Mode".

correct is D : reference: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes

Correct Answer: D ScaleSetVM orchestration mode: 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. It the current default VMSS behavior. (Scale set VMs are created in a single shot).

This question is outdated. The two Orchestration Modes are: - Uniform orchestration: 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: With Flexible orchestration, Azure provides a unified experience across the Azure VM ecosystem. Flexible orchestration offers high availability guarantees (up to 1000 VMs) by spreading VMs across fault domains in a region or within an Availability Zone. I can say that Uniform orchestration superceded ScaleSetVM while Flexible orchestration superceded VM mode. Reference: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes

D) " Deploy one virtual machine scale set that is set to ScaleSetVM orchestration mode. " Currently the correct option is the Uniform Orchestration Mode - https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes#scale-sets-with-uniform-orchestration

Correct Answer: D 🗳️ Reference: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/orchestration-modes

Yep D Optimized for large-scale stateless workloads with identical instances. 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. Individual Uniform VM instances are exposed via the virtual machine scale set VM API commands. ***NOTE*** You cannot add existing Machine to any type of VM scale set, In Flexible Orchestration ScaleSet ONLY newly created VMs or VMS spawned by the Condition of the scaleset Can be added to scale set Uniform Scaleset DO NOT allow of addition of newly created VM to the scale set

D. Deploy one virtual machine scale set that is set to ScaleSetVM orchestration mode