An organization has two teams of developers. One team develops web applications. The other team develops
mobile applications.
You administer servers for the organization. All four servers run Windows Server 2012 R2 and are part of a
Hyper-V cluster. You create six virtual machines (VMs) for each team.
You plan to create a virtual environment for the teams. You have the following requirements:
Both teams must use the 10.10.10.0/24 subnet.
Each VM for the web application team must have network connectivity with all other web application VMs.
Each VM for the mobile application team must have network connectivity with all other mobile application VMs.
The VMs for the web application team must NOT connect to the VMs for the mobile application team.
You need to create the network for the VMs.
What should you do?
A.
Configure one connected network. Allow new VM networks created on this logical network to use network
virtualization.
B.
Set the virtual LAN ID for the management network.
C.
Enable private virtual LAN (PVLAN) networks.
D.
Configure one connected network. Do NOT allow newVM networks created on this logical network to use
network virtualization.
Any official explanation link? As of why the answer is A?
0
0
The VMs for the web application team must NOT connect to the VMs for the mobile application team
is not accomplished with A?
0
0
For an explanation see ‘http://blogs.technet.com/b/scvmm/archive/2013/06/17/logical-networks-part-v-network-virtualization.aspx’ where it states:
“Network Virtualization introduced in Windows Server 2012 Hyper-V provides administrators with the ability to create multiple virtual networks on a shared physical network. In this approach to isolation, each tenant gets a complete virtual network, which includes support for virtual subnets and virtual routing. Tenants can even use their own IP addresses and subnets in these virtual networks, even if these conflict with or overlap with those used by other tenants. Further, since virtual networks are defined entirely in software, it is not necessary to reconfigure the physical network (unlike VLANs and PVLANS solutions) to onboard or remove tenant networks or to make changes to reflect new business requirements.”
0
0
I agree that A is the answer
0
0
Would C be a valid option?
0
0
C would not work because with Hyper-V PVLANs the VM’s cannot talk to each other, they can only talk to the router.
http://blogs.technet.com/b/scvmm/archive/2013/06/04/logical-networks-part-iv-pvlan-isolation.aspx
In this scenario the VM among each group need to talk to each other.
0
0
Not right. In community mode, VMs can talk to each other in the same PVLAN.
0
0
community mode doesn’t exist in vmm
0
0
bah it does exist on hyper-v 2012 R2 and the question doesn’t mention anything about VMM, C would be a plausible answer as well, allthough i still go for A.
0
0
But Network Virtusalization ist a part of VMM. And that product is not mentioned in the quastion !
So I Think it’s Answer C
0
0
In my opinion the answer is C, read this blog:
http://blog.marcosnogueira.org/multitenant-security-and-isolation-with-hyper-2012/
0
0
rectification. The correct answer is A. Look This:
http://blogs.technet.com/b/scvmm/archive/2013/06/17/logical-networks-part-v-network-virtualization.aspx
” In this approach to isolation, each tenant gets a complete virtual network, which includes support for virtual subnets and virtual routing.” -> Both teams must use the 10.10.10.0/24 subnet.
0
0
You cannot use the same IP subnet’s with PVLAN’s ! You need network virtualization for this. Therefore, answer is A
0
0