You administer of 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 (openSUSE 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: Azure Linux Agent
This agent is installed on the Linux VM and is responsible to communicate with the Azure Frabric
Controller.
* UPLOADING A VIRTUAL MACHINE TO WINDOWS AZURE
Assumption: A Windows Server (2008 R2 or 2012) is created and running as a virtual machine in Hyper-V.
(C)
Log onto the Windows Server hosted in Hyper-V you’d like to upload to Windows Azure and open and
command prompt (I’m using Windows Server 2012 R2).Navigate to c:\\Windows\\System32\\Sysprep
Type in sysprep.exe and select enter: (D)
ABE
https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-prepare-for-upload-vhd-image?toc=%2fazure%2fvirtual-machines%2fwindows%2ftoc.json
0
0
sure 100%
ACE
0
0
The move is only for the VMs so the disks need to be in VHD format to be imported into Azure (E), they need to have their networking modified to work in the new address space (B) and the Linux machines need the WALinuxAgent agent installed to work in Azure (A).
I don’t see any need for Sysprep as the machines are not going to be recreated, just moved (there is nothing to suggest the domain or functions will change so no need to change the SSID or accounts).
I don’t see a need to change the OS of the 2008 servers to R2 as 2008 is supported:
https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines
So it is ABE by this chain of thought.
0
0
ACE as Ahmed says.
A – Linux Servers need the agent prior to migration
Not B – VMs get a new network adapter so modifying the current one is pointless
C – 2008 R2 is the oldest supported Windows Server OS on Azure
Not D – It didn’t say it wanted the VMs to be used as an image
E – VHDX is not supported in Azure so any VHDX have to be converted to VHD
0
0
From Iain’s link “For versions that are earlier than Windows Server 2008 R2, there is no Azure Marketplace support, and customers must provide their own images.”
Which means you should be able to upload 2008 VM.
ABE, I think.
0
0
What’s more, part of that new 243Q Microsoft 70-533 dumps for reviewing:
https://drive.google.com/open?id=0B-ob6L_QjGLpfnV3MVl6X3pXOWw1Z3YtQUpJRVRiTkNkbGNFbVBNRXhjSkw3bWk1WHdYcW8
Best Regards!
0
0