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:
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. And since Port
mirroring allows the network traffic of a virtual machine to be monitored by copying the traffic
and forwarding it to another virtual machine that is configured for monitoring, you should
configure port mirroring on VM2.
Incorrect answers:
A: NUMA spanning is a processor setting that works by projecting a virtual NUMA topology
to the guest operating system in a way that is optimized to match the NUMA topology of the
underlying physical host machine. The effect is to provide virtual machines with additional
computing resources for high-performance server applications such as Microsoft SQL Server
and modern server operating systems such as Windows Server 2012 that include built-in
NUMA optimizations.
B: Resource control in used in the event where you need to adjust the computing resources
of a virtual machine, you can reconfigure the resources to meet the changing needs. You
can also specify resource controls to automate how resources are allocated to virtual
machines.
C: Resource metering includes:
• Total incoming network traffic, measured in megabytes, for a virtual network adapter.
• Total outgoing network traffic, measured in megabytes, for a virtual network adapter
In other words not capturing, just measuring traffic over the network adapters.
D: Virtual Machine Chimney or TCP Chimney Offload as it is also known, transfers
Transmission Control Protocol (TCP) traffic processing, such as packet segmentation and
reassembly processing tasks, from a computer’s CPU to a network adapter that supports
TCP Chimney Offload. Moving TCP/IP processing from the CPU to the network adapter can
free the CPU to perform more application-level functions. TCP Chimney Offload can offload
the processing for both TCP/IPv4 and TCP/IPv6 connections if supported by the network
adapter.
E: VLAN ID is used to specify a segment of the VLAN or isolate network traffic for the virtual
network adapter.

F: Processor settings is used to configure the number of virtual processors that the virtual
machine uses, enable processor compatibility to allow live migrations to hosts having a
different processor architecture, or configure the NUMA topology on a NUMA-capable host,
not to monitor network traffic.
G: The Startup order is set in the BIOS of the computer and has no effect on network
monitoring.
H: Automatic start action allows you to specify what the virtual machine should do when the
host machine boots up. The options you can choose from are to automatically start the
virtual machine if it was running when the VMM service on the host stopped (the default), to
always start the virtual machine automatically, or to do nothing. You can also specify a
startup delay in seconds to reduce resource content between different virtual machines
starting up on the host.
I: Integration Services settings on virtual machines include services such as operating
system shutdown, time synchronization, data exchange, Heartbeat, and Backup (volume
snapshot services not network monitoring.
K: Single-root I/O virtualization -capable network adapters can be assigned directly to a
virtual machine to maximize network throughput while minimizing network latency and the
CPU overhead required for processing network traffic.
References:
http://technet.microsoft.com/en-us/library/jj679878.aspx#bkmk_portmirror