Your network contains a server named Server1 that runs Windows Server 2012.
Server1 has the Hyper-V server role installed.
Server1 hosts four virtual machines named VM1, VM2,VM3, and VM4. Server1 is configured as shown in the
following table.

You install a network monitoring application on VM2.
You need to ensure that all of the traffic sent to VM3 can be captured on VM2. What should you configure?

A.
NUMA topology

B.
Resource control

C.
Resource metering

D.
Virtual Machine Chimney

E.
The VLAN ID

F.
Processor Compatibility

G.
The startup order

H.
Automatic Start Action

I.
Integration Services

J.
Port mirroring
K.
Single-root I/O virtualization

Explanation:
http://technet.microsoft.com/en-us/library/jj679878.aspx#bkmk_portmirror
What’s New in Hyper-V Virtual Switch
Port Mirroring
With Port Mirroring, traffic sent to or from a Hyper-V Virtual Switch port is copied and sent to a mirror port.
There are a range of applications for port mirroring – an entire ecosystem of network visibility companies exist
that have products designed to consume port mirror data for performance management, security analysis,and
network diagnostics. With Hyper-V Virtual Switch port mirroring, you can select the switch ports that are
monitored as well as the switch port that receives copies of all the traffic.
The following examples configure port mirroring so that all traffic that is sent and received by both MyVM and
MyVM2 is also sent to the VM named MonitorVM.
Set-VMNetworkAdapter VMName MyVM PortMirroring Source
Set-VMNetworkAdapter VMName MyVM2 PortMirroring Source
Set-VMNetworkAdapter VMName MonitorVM PortMirroring Destination
==================