You administer two Windows Server 2012 R2 servers that have the Hyper-V role installed. You use System
Center 2012 Virtual Machine Manager (VMM) to managethe Hyper-V host servers.
You need to create a server lab environment. The lab servers have the following requirements:
All of the lab servers must be virtual zed.
All of the lab servers must be on an isolated network. All of the lab servers must be able to communicate with
each other.
You need to configure networking for the lab environment.
What should you do?
A.
Create a logical switch.
B.
Create a media access control (MAC) pool.
C.
Add a load balancer.
D.
Create a private virtual LAN (PVLAN) logical network.
“All of the lab servers must be able to communicate with each other.”
This isn’t possible with PVLAN. I assume the question should read “must NOT be able”.
0
0
Microsoft Pvlan implementation supports only isolated mode
http://blogs.technet.com/b/scvmm/archive/2013/06/04/logical-networks-part-iv-pvlan-isolation.aspx
Only possible answer left is logical switch (A)
0
0
I am gonna have to go with logical switch too…
0
0
I would have to go with answer D.
The question states that “All of the lab servers must be on an isolated network”. This implies network virtualization / PVLANs.
It also states that “All of the lab servers must be able to communicate with each other”. This can also be achieved with network virtualization / PVLANs.
See below articles for reference:
http://technet.microsoft.com/en-us/library/dn376344.aspx
http://technet.microsoft.com/en-us/library/dn376344.aspx
http://technet.microsoft.com/en-us/library/jj721575.aspx
0
0
no it doesn’t. it assumes a virtual switch of the type “private”.
0
0
forget this remark. That would only work on 1 hyper-v host. The vm’s could be spread out over more hosts.
0
0
Correct Answer D
0
0
Correct Answer is D
I see it as if each one of the “Lab Environments” is a Tenant in the Cloud.
Private Virtual LANs (PVLANS) are often used by Service Providers (Hosters) to work around the scale limitations of VLANS . They essentially allow network administrators to divide a VLAN into a number of separate and isolated sub-networks which can then be allocated to individual customers (tenants).
http://blogs.technet.com/b/scvmm/archive/2013/06/04/logical-networks-part-iv-pvlan-isolation.aspx
0
0
I agree, answer is PVLANS logical network.
0
0
I would say the correct answer it’s A.
D seems wrong to me because:
The questions states that System Center Virtual Machine Manager 2012 is being used (Not R2).
PVLAN isolation Community mode (which will allow to “All of the lab servers must be able to communicate with each other”) doesn’t exist prior SCVMM 2012 R2 according to http://blogs.technet.com/b/scvmm/archive/2013/06/04/logical-networks-part-iv-pvlan-isolation.aspx
“…SC VMM 2012 SP1 only supports isolated mode (as described above) and has no concept of primary (promiscuous) or community modes …” so according to this info “D” would not work to have communications between all of the servers located on the PVLAN
0
0
PVLAN, according to Microsoft’s definition of a PVLAN, does not allow communication between VM’s. They can only talk directly to the gateway. So D is incorrect.
0
0
The correct answer is A, not D. The requirements are that all of the lab servers must be virtualized, on an isolated network and must be able to communicate with
each other. Answer D does not allow the lab servers to communicate with each other. Answer A fulfills all the requirements, see http://technet.microsoft.com/en-us/library/jj721568.aspx#BKMK_LogicalNetworks for example.
0
0
Hi, the correct answer is for sure D. A logical switch is just a template for a virtual switch. You can not configure isolation with logical switches.
Answer A is not ‘Logical Network’ answer A is ‘Logical Switch’ and therefor the answer is D.
It is right, the Community code is only available with R2 and I think the miss the R2 in the Question.
I had the Question in the exam today and the answer is D virtual Lan (PVLan).
0
0
pvlan’s could work. However i have found no evidence of “community pvlans” (which would be needed for vm’s to communicate with each other) is supported in VMM 2012 R2 (it is supported in Windows 2012 r2, so with 1 Hyper-V host without VMM it could definitely work).
For that reason i will go for answer A.
A logical switch can link a VLAN of a physical switch to an uplink port profile with a virtual port profile. As long as the VLAN is not routable are requirements are met.
Not that it will mention anything about a VLAN without gateway, it’s still an inresting read (part1-4): http://www.hyper-v.nu/archives/mvaneijk/2013/08/system-center-vmm-2012-r2-bare-metal-deployment-with-converged-fabric-and-network-virtualization-part-1-intro/
0
0
“VLAN is not routable All requirements are met”*
that’s actaully true for PVLAN’s as well as the “subnet” needs to be isolated.
0
0
As explained by this link : http://blogs.technet.com/b/scvmm/archive/2013/06/04/logical-networks-part-iv-plan-isolation.aspx
SC VMM 2012 SP1 only supports isolated mode (as described above) and has no concept of primary (promiscuous) or community modes. What this means in practice is that a Virtual Machine connected to a PVLAN in this release is completely isolated from any other resources on the network. The only device it can directly communicate with is the default IP gateway.
Therefore the answer is A.
0
0
A is right answer.
https://blogs.technet.microsoft.com/canitpro/2014/02/11/hyper-v-clustering-resiliency-step-4-logical-switches/
0
0