Which servers should you identify?

Your network contains an Active Directory domain named contoso.com.
You deploy Microsoft System Center 2012 Virtual Machine Manager (VMM).
The network contains five physical servers.
The servers are configured as shown in the following table.
You plan to use VMM to convert the existing physical servers to virtual machines.
You need to identify which physical servers can be converted to virtual machines.
Which servers should you identify? (Each correct answer presents part of the solution. Choose all that apply.)

Your network contains an Active Directory domain named contoso.com.
You deploy Microsoft System Center 2012 Virtual Machine Manager (VMM).
The network contains five physical servers.
The servers are configured as shown in the following table.
You plan to use VMM to convert the existing physical servers to virtual machines.
You need to identify which physical servers can be converted to virtual machines.
Which servers should you identify? (Each correct answer presents part of the solution. Choose all that apply.)

A.
Server1

B.
Server2

C.
Server3

D.
Server4

E.
Server5

Explanation:
with certbase
certbase Notes:
Microsoft System Center Virtual Machine Manager (VMM) allows you to convert physical machines to virtual machines using the physical-to-virtual machine
conversion (P2V). VMM simplifies P2V conversion by a task-based wizard that largely automates the conversion process. For a P2V conversion following conditions
apply to the source computer:

Mindestes 512 MB RAM
Volumes are only supported up to a size of 2040 GB.
ACPI BIOS (Advanced Configuration and Power Interface) – Vista WinPE will not install using a different BIOS.
VMM and the host computer must have access to the source machine.
Must not be located in a perimeter network. A perimeter network, also known as a screened subnet, is a collection of devices and subnets that are positioned
between an intranet and the Internet to protect the intranet from unauthorized Internet users. The source computer for a P2V conversion can be in any other network
topology, connect to the source computer manufactured in the VMM server for temporary installation of an agent and Windows Management Instrumentation (WMI)
calls to the source computer can be made.
https://technet.microsoft.com/en-us/library/gg610562.aspx

https://technet.microsoft.com/en-us/library/gg610610.aspx



Leave a Reply 9

Your email address will not be published. Required fields are marked *


Han Solo

Han Solo

OS Versions = Ok (No 2003 Sp1)
Memory = Ok (>512 MB)
CPU = Ok (No Itanium)

That leaves the disks which cannot be over 2TB:

Only Server 2 and Server 3 have bigger disks.

Answer is correct.

ADE

no

no

Be careful with this one, Han! Only 2040GB, so only D would fit this criteria as it’s the only one with ANY volume that is not larger than 2040GB (not 2048GB=2TB)

David

David

Technically, a TB is decimal, a TiB is binary. So 2TB would be 2000GB.

However, I believe Microsoft wants us to realize the limit is indeed 2040 instead of 2048 and so Mr ‘no’ is likely correct in considering A & E traps.

These are the kind of questions where it would be nice to hear from MS what the correct answer is…

no

no

You’re being a bit too literal. 1GB = 1024MB as far as Microsoft is concerned. Although, as far as MANUFACTURERS go, yes, you’re right, 1000MB = 1GB. That’s why you never get the full size of a HDD when you buy it, due to that conversion discrepancy.

Leunis

Leunis

If you work with that logic, then 4 and 5 would definitely fit, as then the “2TB” drive they mention would actually be 1950MB or whatever the exact number is in the discrepancy

Very difficult question, but I cannot believe that MS would ask for multiple answers and only give one that is valid.

I would stick with the given answer for this one

Han Solo

Han Solo

I misread 2040 for 2048 in this question:-) Tricky indeed.

In the exam i got a bit different one then this one. But still it was about the hard disk sizes.

Marvin

Marvin

Ms/Mr “no” is correct. Only physical server SERVE4 can be converted to virtual machine using SCVMM 2012

I created a 2050-GB VHDX on Hyper-V host. I attached it to a VM. When I initialised it as MBR, Windows system automatically splits the disk into two parts: 2048GB and 2GB. Given the limitation of MBR is 2TB, it is extremely likely that 2TB is equal to 2048GB in Microsoft’s dictionary.

Thank you, no, David, Leunis and Han Solo!