You administer a set of virtual machine (VM) guests hosted in Hyper-V on Windows Server 2012 R2.
The virtual machines run the following operating systems:
Windows Server 2008
Windows Server 2008 R2
Linux (open SUSE 13.1)
All guests currently are provisioned with one or more network interfaces with static bindings and VHDX disks.
You need to move the VMs to Azure Virtual Machines hosted in an Azure subscription.
Which three actions should you perform? Each correct answer presents part of the solution.
A.
Install the WALinuxAgent on Linux servers.
B.
Ensure that all servers can acquire an IP by means of Dynamic Host Configuration Protocol (DHCP).
C.
Upgrade all Windows VMs to Windows Server 2008 R2 or higher.
D.
Sysprep all Windows servers.
E.
Convert the existing virtual disks to the virtual hard disk (VHD) format.
Explanation:
A: For Linux the WALinuxAgent agent is mandatory.
C: Need to upgrade to Windows Server 2008 R2 or higher.
E: VHDX is not supported, so VHD is needed.
https://azure.microsoft.com/fr-fr/documentation/articles/virtual-machines-create-upload-vhdwindows-server/
https://azure.microsoft.com/fr-fr/documentation/articles/virtual-machines-create-upload-vhd-windows-server/
I’m pretty sure it’s ABE.
Regarding C, 2008 is supported (https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines) “For versions that are earlier than Windows Server 2008 R2, there is no Azure Marketplace support, and customers must provide their own images.”
0
0
B is not needed when migrating to Azure
0
0
Yes it is. Azure will assign a automatic IP to the VM and then you configura an Azure Static IP for the VM if needed.
0
0
I would go with ADE since sysprep is necessary
https://docs.microsoft.com/en-au/azure/virtual-machines/windows/classic/createupload-vhd
0
0
I agree. Azure supports 2003+ windows versions
0
0
Agree ADE
0
0
Agree… i think the confusion here is that you can create a windows server 2008 vm in azure but you can migrate windows 2003 and up over.
0
0
Meant to say can’t create a windows server 2008
0
0
No. Sysprep is not used in this case. Only if you wish to create a new Image for furture VM deployments.
0
0
I will go with ADE
0
0
https://technet.microsoft.com/library/cc794868.aspx
question doesn’t specify what service pack the 2008 is using but seeing as 2003 is supported i would imagine 2008 is as well. I believe it’s ADE
0
0
https://blogs.technet.microsoft.com/cbernier/2014/01/27/move-vms-between-hyper-v-and-windows-azure/
Of course i also find this that says 2008 r2 and above… ugh
0
0
https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-support-matrix-to-azure#support-for-replicated-machine-os-versions
yeah i’m gonna go with ACE
0
0
ADE +1
0
0
In my opnion (A,B and E):
A.
Install the WALinuxAgent on Linux servers.
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/create-upload-generic?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json
The Azure Linux Agent (waagent) is required to properly provision a Linux virtual machine in Azure. You can get the latest version, file issues or submit pull requests at the Linux Agent GitHub repo.
B.
Ensure that all servers can acquire an IP by means of Dynamic Host Configuration Protocol (DHCP).
Prepare the VM
If you intend to use the VHD as-is to create a new VM, ensure the following steps are completed.
Prepare a Windows VHD to upload to Azure. Do not generalize the VM using Sysprep.
Remove any guest virtualization tools and agents that are installed on the VM (like VMware tools).
Ensure the VM is configured to pull its IP address and DNS settings via DHCP. This ensures that the server obtains an IP address within the VNet when it starts up.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/create-vm-specialized
1
0
Why we need to Sysprep? it’s already on the Hyper-V…
Sysprep step on some MS links doesn’t mean it’s mandatory.
ABE
1
0
+1, ABE
0
0
ABE 100%
2008 is not supported but that doesnt mean you cant upload your own vhd. It just prevents you from choosing 2008 from marketplace image gallery.
you need dhcp because azure has its own vnet infrastructure
you need walinuxagent for linux
you need vhd because vhdx is not supported
sysprep would be relevant if you wanted to deploy multiple virtual machines based on this one vhd(in which case, sysprep would generalize the image to be used many times)
0
0
BTW, part of new 243Q 70-533 dumps for your reference:
https://drive.google.com/open?id=0B-ob6L_QjGLpfnV3MVl6X3pXOWw1Z3YtQUpJRVRiTkNkbGNFbVBNRXhjSkw3bWk1WHdYcW8
Best Regards!
0
0