You administer a Windows Server virtual machine (VM).
You upload the VM to Azure.
You need to ensure that you are able to deploy the BGInfo and VMAccess extensions.
What should you do?
A.
Select the Install the VM Agent checkbox while provisioning a VM based on your
uploaded VHD.
B.
Select the Enable the VM Extensions checkbox while provisioning a VM based on your
uploaded VHD.
C.
Install the VM Agent MSI and execute the following Power Shell commands: $vm = GetAzureVM -serviceName $svc -Name $name $vm.VM.ProvisionGuestAgent = $true UpdateAzureVM -Name Sname -VM $vm.VM -ServiceName $svc
D.
Install the VM Agent MSI and execute the following Power Shell commands: $vm = GetAzureVM -serviceName $svc -Name $name Set-AzureVMBGInfoExtension -VM $vm.VM
Set-AzureVM Access Extension -VM $vm.VM Update-AzureVM -Name Sname -VM $vm.VM
-ServiceName $svc
Explanation:
http://msdn.microsoft.com/en-us/library/azure/dn606311.aspx
From the question text I would answer as “C”
To be “able to deploy the BGInfo and VMAccess extensions”, in general, we need to have Azure VM agent installed to the machine.
From https://azure.microsoft.com/en-us/blog/vm-agent-and-extensions-part-2/
How to enable VM Agent and Extensions on VMs created from Disks:
Another common scenario for creating VMs is to create Azure VMs from a Disk. If you are using a Sysprep’ed image from the Azure Portal, the VM Agent gets enabled in the create VM workflow without any extra steps. But if you are using a specialized disk, then the VM Agent needs to be manually installed. The steps below describes the process involved.
In the question there is no a word regarding sysprep, so I think the correct answer is C:
we installing the agent from MS, then updating the machine with info that the agent is installed
Nice articles regarding VM extensions:
https://azure.microsoft.com/en-us/blog/vm-agent-and-extensions-part-1/
https://azure.microsoft.com/en-us/blog/vm-agent-and-extensions-part-2/
C is correct answer
C