Your company has a Microsoft Hyper-V Server 2008 R2 environment. You manage the
virtual environment by using Microsoft System Center Virtual Machine Manager (VMM) 2008
R2. You are creating a virtual test environment by installing two child partitions. The test
environment must be completely isolated from all production servers. You need to ensure

that the child partitions can communicate with each other. Which connection type should you
configure?

A.
Private

B.
Internal

C.
External

D.
Dedicated host

Explanation:
Types of virtual networks
While Hyper-V allows you to configure complex virtual network environments, the basic
concept of virtual networking is straightforward. A virtual network works like a physical
network switch except that the switch is implemented in software (which is why it is
sometimes referred to as a virtual network switch). Ports are added or removed as they are
needed when virtual machines are connected to or disconnected from a virtual network.
Virtual Network Manager (available from the Hyper-V Manager snap-in) offers three types of
virtual networks that you can use to define various networking topologies for virtual
machines and the virtualization server. You can create the following types of virtual
networks: Private virtual networks. Use this type when you want to allow communication only
between virtual machines on the same virtualization server. A private virtual network is not
bound to a physical network adapter. A private virtual network is isolated from all external
network traffic on the virtualization server, as well any network traffic between the
management operating system and the external network. This type of network is useful
when you need to create an isolated networking environment, such as an isolated test
domain. A closer look at external virtual networks For a simple virtual network configuration
that establishes connectivity to an external network, we recommend that you have at least
two network adapters on the server running Hyper- V: one network adapter dedicated to the
management operating system so you can access it remotely, and one or more network
adapters dedicated to the virtual machines. If you are running an Internet SCSI (iSCSI)
initiator for virtual hard disk storage, we recommend that you use additional network
adapters in the management operating system. When you add the Hyper-V role during a full
installation of Windows Server2008 or Windows Server2008R2, you have the option to
configure one or more external virtual networks. However, this option is not available when
you install Hyper-V on a Server Core installation. When you create an external virtual
network, this action affects how networking is configured in the management operating
system. Hyper-V creates a virtual network adapter in the management operating system.
Hyper-V then binds the standard services and protocols to the virtual network adapter
instead of the physical network adapter, and binds only the Virtual Network Service Protocol
to the physical network adapter. After an external virtual network is configured, all
networking traffic is routed though the virtual network switch. The virtual network switch
functions as a physical switch would and routes networking traffic through the virtual network
to its destination. For this reason, we recommend using at least one additional physical
network adapter for managing network traffic. External virtual networks. Use this type when
you want to provide virtual machines with access to a physical network to communicate with
externally located servers and clients. This type of virtual network also allows virtual
machines on the same virtualization server to communicate with each other. This type of
network may also be available for use by the management operating system, depending on

how you configure the networking. (The management operating system runs the yper-V
role.) For more information, see “A closer look at external virtual networks” later in this topic.
Internal virtual networks
Use this type when you want to allow communication between virtual machines on the same
virtualization server and between virtual machines and the management operating system.
This type of virtual network is commonly used to build a test environment in which you need
to connect to the virtual machines from the management operating system. An internal
virtual network is not bound to a physical network adapter. As a result, an internal virtual
network is isolated from all external network traffic.