Correct Answer: Box 1: 4 If you resize the Scale Set all the VMs get resized at once, thus 4 is the correct answer. Box 2: 1 Automatic OS updates update 20% of the VMs at once, with a minimum of 1 VM instance at a time. Also 20% of 4 = 0.8. Reference: https://docs.microsoft.com/en-us/learn/modules/build-app-with-scale-sets/2-features-benefits-virtual-machine-scale-sets https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set

The question asks "if the administrator changes the size", not if it gets scaled up vertically. I tested this, and if you resize the scale set all the virtual machines get resized at once, thus 4 is the correct answer. For the second part, automatic OS updates update 20% of the VMs at once, with a minimum of 1 VM instance at a time.

Final Answer : 4 1

Box 1: 1 This is because the question 1 states : " if the administrator changes the size of a VM (in the scaleset)" It is not resizing the scaleset. AI answer to this is as follows: Resizing an Individual VM: When you change the size (SKU) of an individual VM within the VMSS (e.g., from a smaller size to a larger one), only that specific VM is resized. The other VMs in the VMSS remain unaffected. The resized VM may need to be restarted to apply the new size. In summary, resizing an individual VM within a VMSS does not automatically resize all VMs in the set. You’ll need to manage each VM’s size independently. So the answer is 1 for Box 1. Box 2= 1 Automatic OS updates update 20% of the VMs at once, with a minimum of 1 VM instance at a time. Box 2 = 1

EnableAutomaticUpdates = FALSE: New Windows OS update must be done manually => 0 VM UpgradePolicy = Automatic: 20% of VMs will be upgrade at the same time (Min=1) => 1 VM

Newbee here, where can I know the total number of VMs?

Box 1: 4 & Box 2: 1

Guys, sorry for the noob question. where did you get the value "4"? I don't see any number 4 in the picture.

Box1 - 4 This refers to the second PS cmdlt 'UpgradePolicy' which "determines what happens next after you change the scale set model" (ex. VM size, OS ver, extensionPolicy). Box1 asks what happens when size of VM changes. Since it's set to 'automatic', the change will be applied to all the VMs in the scale set at once [ref: https://msftstack.wordpress.com/2016/11/15/azure-scale-set-upgrade-policy-explained/] Box2 - 0 This refers to the first PS cmdlt 'UpgradePolicy' which "determines what happens when image publishers publishes the latest image OS image - which in this case Microsoft released the Win Server 2016 image. Since it's set to 'false', there will be no changes made- u[dates will need to happen manually with user intervention. [ref: https://techcommunity.microsoft.com/t5/azure-paas-blog/azure-service-fabric-enableautomaticupdates/ba-p/834246]

It seems to me that picture doesn't match questions.

Box 1: 4 The first command has nothing to do with VM Resizing. Box 2: 1 What's set to 'false' is Patch updates. This is recommended to be set to 'False' when Automatic OS upgrades are set to 'True'. What this means is that the automatic rolling OS Upgrades will happen at 20%.

WindowsConfiguration.EnableAutomaticUpdates PropertyGets or sets indicates whether Automatic Updates is enabled for the Windows virtual machine. Default value is true. For virtual machine scale sets, this property can be updated and updates will take effect on OS reprovisioning. Based on the above note, as EnableAutomaticUpdates = False the OS updates will not happen. So answers are Box1: 4 and Box 2: 0

There're seven more confusing comments here, I am totally lost... as usual, I will follow the answer from mlantonis

Part one: Answer 0 The Administrator is doing a manual change to the virtual machine scale set MODEL (AKA OS Build), however this model change does not take immediate affect for the exsiting machines in the Scale Set, see this section of the doc: Read Here: (https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set#how-to-update-global-scale-set-properties) Part 2: Answer 4 The Upgrade policy (Don't get confused with "Update" Policy, which is for OS Patches) is set to Automatic. When the Upgrade policy is set to automatic, all the VMs may be taken down and upgraded at the same time, as per the MS docs: Read Here: (https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set#how-to-bring-vms-up-to-date-with-the-latest-scale-set-model) NB: The 20% policy for upgrades mentioned in other comments is for Extensions in a VMSS, not the actual VM scale set.

Box 1: 0 - The enableAutomaticUpdates parameter is set to false. To update existing VMs, you must do a manual upgrade of each existing VM. Box 2: 4 - Enabling automatic OS image upgrades on your scale set helps ease update management by safely and automatically upgrading the OS disk for all instances in the scale set.

I'm tired of these questions being more of tests of English comprehension than actually doing the job. Trick questions with diagrams that are unimportant or intentionally misleading does not do anything to test knowledge.

Explanation the Get-AzVmssVM cmdlet gets the model view and instance view of a Virtual Machine Scale Set (VMSS) virtual machine. Box 1: 0 The enableAutomaticUpdates parameter is set to false. To update existing VMs, you must do a manual upgrade of each existing VM. Box 2: 1 Below is clearly mentioned in the official Website "The upgrade orchestrator identifies the batch of VM instances to upgrade, with any one batch having a maximum of 20% of the total instance count, subject to a minimum batch size of one virtual machine." So, 20% from 4 ~1