Explanation:
Explanation:
Step 1: Stop VM1.
Step 2: Detach Disk1 from VM1.
Step 3: Start VM1.
Detach a data disk using the portal
1. In the left menu, select Virtual Machines.
2. Select the virtual machine that has the data disk you want to detach and click Stop to deallocate the VM.
3. In the virtual machine pane, select Disks.
4. At the top of the Disks pane, select Edit.
5. In the Disks pane, to the far right of the data disk that you would like to detach, click the Detach button image detach button.
6. After the disk has been removed, click Save on the top of the pane.
7. In the virtual machine pane, click Overview and then click the Start button at the top of the pane to restart the VM.
8. The disk stays in storage but is no longer attached to a virtual machine.
Step 4: Attach Disk1 to VM2 -
Attach an existing disk -
Follow these steps to reattach an existing available data disk to a running VM.
1. Select a running VM for which you want to reattach a data disk.
2. From the menu on the left, select Disks.
3. Select Attach existing to attach an available data disk to the VM.
4. From the Attach existing disk pane, select OK.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/detach-disk
https://docs.microsoft.com/en-us/azure/lab-services/devtest-lab-attach-detach-data-disk

Microsoft updates, which Microsoft refers to as planned maintenance events, sometimes require that VMs be rebooted to complete the update. To reduce the impact on VMs, the Azure fabric is divided into update domains to ensure that not all VMs are rebooted at the same time.
Incorrect Answers:
A: An update domain is a group of VMs and underlying physical hardware that can be rebooted at the same time.
B, C: A fault domain shares common storage as well as a common power source and network switch. It is used to protect against unplanned system failure.
References:
https://petri.com/understanding-azure-availability-sets
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-availability-sets

Explanation

Box 1: Assign a tag to each resource.
You apply tags to your Azure resources giving metadata to logically organize them into a taxonomy. After you apply tags, you can retrieve all the resources in your subscription with that tag name and value. Each resource or resource group can have a maximum of 15 tag name/value pairs. Tags applied to the resource group are not inherited by the resources in that resource group.
Box 2: From the Cost analysis blade, filter the view by tag
After you get your services running, regularly check how much they're costing you. You can see the current spend and burn rate in Azure portal.
* Visit the Subscriptions blade in Azure portal and select a subscription.
* You should see the cost breakdown and burn rate in the popup blade.
* Click Cost analysis in the list to the left to see the cost breakdown by resource. Wait 24 hours after you add a service for the data to populate.
* You can filter by different properties like tags, resource group, and timespan. Click Apply to confirm the filters and Download if you want to export the view to a Comma-Separated Values (.csv) file.
Box 3: Download the usage report
References:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-using-tags
https://docs.microsoft.com/en-us/azure/billing/billing-getting-started

Explanation
Box 1 = max value
Box 2 = 20
Explanation
Use max for platformFaultDomainCount
2 or 3 is max value, depending on which region you are in.
Use 20 for platformUpdateDomainCount
Increasing the update domain (platformUpdateDomainCount) helps with capacity and availability planning when the platform reboots nodes. A higher number for the pool (20 is max) means that fewer of their nodes in any given availability set would be rebooted at once.
References:
https://www.itprotoday.com/microsoft-azure/check-if-azure-region-supports-2-or-3-fault-domains-managed-disk
https://github.com/Azure/acs-engine/issues/1030

While resizing the VM it must be in a stopped state.
References:
https://azure.microsoft.com/en-us/blog/resize-virtual-machines/