Contoso, Ltd. has a Windows Server 2012 R2 server with the Hyper-V role installed. Contoso has a virtual
machine named CVM1. The company uses System Center 2012 R2 Virtual Machine Manager (VMM) to
manage the environment.
Contoso acquires Fabrikam, Inc. Fabrikam has a Windows Server 2012 R2 server with the Hyper-v role
installed.
CVM1 must be able to communicate with a virtual machine named FVM2 on a non-routable subnet in the
Fabrikam Hyper-V environment
You need to ensure that CVM1 can communicate with FVM2.
Which technology should you implement?
A.
Remote Desktop (RD) Gateway
B.
Windows Network Load Balancing (WNLB)
C.
Windows Server Gateway
D.
Reverse Proxy Server
In my opinion the correct answer is C. Windows Server Gateway
The question says ..!!
“CVM1 must be able to communicate with a virtual machine named FVM2 on a non-routable subnet in the Fabrikam Hyper-V environment”
it seems to be a same network according to non-routable statement, so i would go with Answer B…
any other suggestion?
C seems to be correct!
A Remote Desktop Gateway (RD Gateway) server is a type of gateway that enables authorized users to connect to remote computers on a corporate network
Windows Network Load Balancing (WNLB)
NLB allows all of the computers in the cluster to be addressed by the same set of cluster IP addresses, and it maintains a set of unique, dedicated IP addresses for each host. For load-balanced applications, when a host fails or goes offline, the load is automatically redistributed among the computers that are still operating. When a computer fails or goes offline unexpectedly, active connections to the failed or offline server are lost
Windows Server Gateway
Windows Server Gateway (Windows Server Gateway) is a virtual machine (VM)-based software router that allows Cloud Service Providers (CSPs) and Enterprises to enable datacenter and cloud network traffic routing between virtual and physical networks, including the Internet.
Virtual networks are created by using Hyper-V Network Virtualization, which is a technology that was introduced in Windows Server® 2012.
Reverse Proxy Server
In computer networks, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client from one or more servers. These resources are then returned to the client as though they originated from the server itself (or servers themselves).[1] While a forward proxy acts as an intermediary for its (usually nearby) associated client(s) and returns to them resources accessible on the Internet, a reverse proxy acts as an intermediary for its (usually nearby) associated server(s) and only returns resources provided by those associated server(s).
sorry I meant “B” seems to be correct!
Why b? I think its c……
I believe the answer is C, the keyword being “non-routable” networks.
Here is my explanation:
Windows Server Gateway (Windows Server Gateway) is a virtual machine (VM)-based software router that allows Cloud Service Providers (CSPs) and Enterprises to enable datacenter and cloud network traffic routing between virtual and physical networks, including the Internet.
In Windows Server 2012 R2, Windows Server Gateway routes network traffic between the physical network and VM network resources, regardless of where the resources are located. You can use Windows Server Gateway to route network traffic between physical and virtual networks at the same physical location or at many different physical locations. For example, if you have both a physical network and a virtual network at the same physical location, you can deploy a computer running Hyper-V that is configured with a Windows Server Gateway VM to act as a forwarding gateway and route traffic between the virtual and physical networks.
Large enterprises may either be hesitant, or for compliance reasons, unable to move some of their services and data to a public cloud hoster. However, enterprises still want to obtain the benefits of the cloud and network virtualization by consolidating their datacenter resources into a private cloud. In a private cloud deployment, overlapping IP addresses may not be needed because corporations have sufficient internal non-routable address space (for example, 10.x.x.x or 192.x.x.x).
http://technet.microsoft.com/en-us/library/jj618319.aspx
It’s C; a gateway acts like a broker between subnets/networks.
NLB is for spreading load between >1 server, and completely non applicable.
The correct answer is C. Even if you would not know about Windows Server Gateway, the answers A, B and D are all obviously wrong, leaving only answer C as the correct answer. For those who believe that the correct answer is B, as Bob already stated, answer B has nothing to do with this whole question.
You are not going to solve routing/communication problems with a load balancing solution. You need a routing solution for this which is Server Gateway (C)