PrepAway - Latest Free Exam Questions & Answers

You need to ensure that you are able to deploy the BGInfo and VMAccess extensions

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?

PrepAway - Latest Free Exam Questions & Answers

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

24 Comments on “You need to ensure that you are able to deploy the BGInfo and VMAccess extensions”

  2. CastorTray says:

    +1 for C

    The VM Agent can be enabled by manually downloading and installing the VM Agent (either the Windows or Linux version) on an existing VM instance and then setting the ProvisionGuestAgent value to true using Powershell or a REST call. (If you do not set this value after manually installing the VM Agent, the addition of the VM Agent is not detected properly.) The following code example shows how to do this using PowerShell where the $svc and $name arguments have already been determined.

    $vm = Get-AzureVM ­serviceName $svc ­Name $name
    $vm.VM.ProvisionGuestAgent = $TRUE
    Update-AzureVM ­Name $name ­VM $vm.VM ­ServiceName $svc

    Reference: VM Agent and VM Extensions Overview




    0



    0
  3. an says:

    +1 for C
    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




    0



    0
  5. Harish Suhanda says:

    A is correct considering that the VHD is already uploaded you just need to ensure that VM Agent is installed, this option is available on portal while creating the VM




    0



    0
    1. David says:

      The question says “You upload the VM to Azure”, meaning that the VM is already running on Azure, right?

      PS
      Microsoft is really big on using powershell, so the answer will probably have to involve a power shell command.




      0



      0
  7. fred says:

    Why not D?

    We had to install TWO extension: BGInfo and VMAccess extensions

    This is the only command line that install both of them.

    The question does not say we created the VM from the portal, but we upload the VM. So BGInfo is not set by default.




    0



    0
  10. Romeo says:

    Fab is 100% correct. Completed this in my Azure environment. You need the VM agent regardless. The agent can be installed after the VM is uploaded and running. Microsoft released a MSI.




    0



    0
  13. challenge says:

    C is the answer – you are uploading a VM to Azure (not provisioning a VM from Azure – so therefore needs the VM Agent MSI)

    Is VM Agent installed?

    $x = Get-AzureVM -ServiceName $vmName
    $x.vm.ProvisionGuestAgent

    If ‘False’ –

    1. Install standalone VM Agent

    2. Inform the Azure platform that the VM now has the agent installed

    $vm = Get-AzureVM –serviceName $svc –Name $name $vm.VM.ProvisionGuestAgent = $TRUE Update-AzureVM –Name $name -VM $vm.VM -ServiceName $svc




    0



    0

Leave a Reply