You have an Azure subscription that contains a virtual machine named VM1. VM1 hosts a line-of-business application that is available 24 hours a day. VM1 has one network interface and one managed disk. VM1 uses the D4s v3 size.
You plan to make the following changes to VM1:
✑ Change the size to D8s v3.
✑ Add a 500-GB managed disk.
✑ Add the Puppet Agent extension.
✑ Attach an additional network interface.
Which change will cause downtime for VM1?
Changing the size of a virtual machine in Azure requires the VM to be in a stopped and deallocated state. This means the VM will experience downtime during the size change process. This is necessary to ensure that the resources associated with the VM are correctly allocated and reconfigured to match the new size specifications.
Ok, Question says which "change" will cause Downtime - [ Means we can change the size to D8s V3 but it restarts the VM results in downtime during the change ] , [ To add interface , we need to stop the VM first, which means change is not possible without downtime ] - So I will go with "B".
Agree with falthu. Explanation is clear. Answer is B. Change the size to D8s v3.
Have tried in Azure, B and D will cause downtime for VM1
You are right. Tried it on D4v3 VM. B caused a restart and D can only be done on a stopped VM.
I think the correct answer is D. I tried resizing my vm while still running and it worked, while attaching a new network interface gave me an error which says that vm should be stopped first.
Error: Virtual machine vm244443 with a single network interface must be stop-deallocated before it can be updated to have multiple network interfaces and vice-versa.
check the uptime. I tried with Linux OS, when I changed the size of running VM uptime is less. Same is aplicable to any OS VM.
We can resize when the vm is online. but it performs a restart in the backend. https://azure.microsoft.com/en-us/blog/resize-virtual-machines/ The physical hardware currently hosting your VM. If the physical hardware currently running your virtual machine also supports your desired new size, then it is very easy to change the VM size through a simple size change operation which results in a VM reboot.
its defo B no question about it
B is correct answer
B its correct, when you resize, your VM is rebooted. And regarding the NIC, you can not either attached or detched a NIC if your VM is running
B & D To add a virtual NIC to an existing VM, you deallocate the VM, add the virtual NIC, then start the VM. Different VM sizes support a varying number of NICs, so size your VM accordingly.
B is correct. When i want to change the size from D4s v3 to another size, the azure portal show : If the virtual machine is currently running, changing its size will cause it to be restarted. Stopping the virtual machine may reveal additional sizes.
B is correct answer. I tried with Linux OS, when I changed the size of running VM uptime is less or different.
Two answers should be correct: B and D - The information displayed in the "Size" Settings on the VM blade clearly inform that vm will be restarted after we change its size (restarting is obviously a downtime): "If the virtual machine is currently running, changing its size will cause it to be restarted." - When the VM is running, the "Attach network interface" button is grayed out and the mouse-over information states that it is not possible to attach a NIC while the machine is running (since we need to shutdown the machine to add a NIC, this is obviously also a downtime): "This operation cannot be performed on a running virtual machine"
i could resize the VM wile it's online but i couldn't attach a NIC unless stopping the VM so "D" is correct
You could resize with online VM, but the CHANGE will force a reboot which is a DOWNTIME.
there was no reboot required to change the size but from begining we'll not be able to attach NIC card without stopping the VM
there was no reboot required to change the size but from begining we'll not be able to attach NIC card without stopping the VM
B&D. Resize the VM and also Add and NetworkInterface cause downtime.
don't agree - resize the disk is a change - whereas ATTACH a NIC does not effect a change.
wrong? Why attaching a NIC is not a change?
wrong? Why attaching a NIC is not a change?
The given answer B is the correct one.
B,D shold be the answer.
both B&D
The answer is D: I think if it asks about the downtime, then it should be the most of downtime. As adding network interface will cause most downtime than changing the disk size. Because for adding the networking interface VM should be down.
No - the verb used with a new NIC is 'attach' - you can attach a NIC without changing the existing one - and without causing any downtime - as it is merely 'attached'
you can not attach a NIC without stopping VM.
you can not attach a NIC without stopping VM.
both restart and stop will cause downtime : So B and D
Resizing and Adding a network Interface will required to stop the VM first
disk change requires a reboot, also it will be a long reboot as the host will change. Exam Ref book, page 196
I just tested this. I knew that resizing the VM requires a reboot. But I was unsure about adding an extra network interface card. I just tested this and it made me shut down the VM before giving me the ability to add the Network card.
Adding a NIC is only possible when the VM is down.
The correct answer is D, you can't add a NIC whilst the VM is running, it must be stopped first
tried to resize Vm while its turned on. resize works without shutting it off. the answer should be adding network interface to VM. the VM do not allow to add another interface without powering off.
Answer i B & D I tried to attach a new NIC .. it was in grayed out.. after shutting down only it was able to attach a new NIC. So confirmed.
They might be trying to trick the question.. Resizing will cause the downtime; NIC can be done only when it is down, so it's not causing downtime? Lol, I don't know, maybe the credit will be given to either B or D
From my perspective, this question asks which action would "cause" a downtime. The change VM size would cause it as with a NIC you yourself have to first stop the VM
Tested in lab: B+D are among the correct answers A: Not tested. I haven't created a puppet VM from the marketplace. Has anyone tested this? B: Changing the VM size reboots the VM causing downtime for less then 30 seconds. However you can change the size while running, on the fly. C: You can add or remove a 500GB premium SSD disk without reboot or downtime (premium SSD is the only performance tier that offers above 500 iops, Good to know). Ive done this before and it does not reboot the VM or cause downtime D: You must stop and deallocate the VM before attaching a new Nic. Cannot be done on the fly while running.
B and D
Resizing the VM will need to be done while the VM is down to ensure data integrity.
D is also right. If we need to change network interface then we have to switch off the vm and then change it will give some downtime
VM should be deallocated to add new NIC. So answer should be B & D.