DRAG DROP
You have an Azure Virtual Network named fabVNet with three subnets named Subnet-1,
Subnet-2 and Subnet-3. You have a virtual machine (VM) named fabVM running in the
fabProd service.
You need to modify fabVM to be deployed into Subnet-3. You want to achieve this goal by
using the least amount of time and while causing the least amount of disruption to the
existing deployment.
What should you do? To answer, drag the appropriate Power Shell cmdlet to the correct
location in the Power Shell command. Each cmdlet may be used once, more than once, or
not at all. You may need to drag the split bar between panes or scroll to view content.
Answer: 
Explanation:
Answer is correct as per
http://blogs.technet.com/b/canitpro/archive/2014/05/20/step-by-step-move-a-microsoft-azure-vm-to-a-different-subnet-within-a-vnet.aspx
0
0
What’s up colleagues, its wonderful pararaph regarding
cultureand fully defined, keep it up all the time.
0
0
Update-AzureVM syntax seems incorrect, yeah? Doesn’t it need the -Name -ServiceName specified explicitly (in addition to -VM) instead of simply providing the names in double quotes? How will the command know which is the VM name, Service Name? Only VM Object is specified with the -VM parameter.
Anyone noticed this?
0
0
The syntax for Update-AzureVM is as follows-
Update-AzureVM [-Name] -VM [-ServiceName] []
Since [-Name] and [-ServiceName] appear in brackets, does it mean it’s optional to explicitly declare them in the cmdlet? While -VM doesn’t appear in brackets, it needs to explicitly typed in?
0
0
The syntax for Update-AzureVM is as follows-
Update-AzureVM [-Name] String -VM PersistentVM [-ServiceName] String [CommonParameters]
Since [-Name] and [-ServiceName] appear in brackets, does it mean it’s optional to explicitly declare them in the cmdlet? While -VM doesn’t appear in brackets, it needs to explicitly typed in?
0
0