Microsoft Hyper-V and SCVMM Fundamentals

DPM supports three storage types: direct disk-to-disk (D2D), disk-to-tape (D2T), and hybrid disk-to-disk-to-tape (D2D2T). Tape-to-tape is not supported because DPM always writes to disk first.

Hyper-V Server 2008 R2 supports up to 384 virtual machines per host, limited by logical processor count and memory. This doubled from the 192 VM limit in the original release.

SCVMM admin console requires all three: Windows Server 2003 SP2 as the OS base, .NET Framework 3.0 to run the application, and IIS Web Server role for web-based management features.

Hyper-V R2 introduced three major capabilities: live migration for zero-downtime VM movement, Cluster Shared Volumes enabling multiple nodes to access the same VHD simultaneously, and processor compatibility mode allowing migration across CPU generations.

SCONFIG is the Server Core configuration tool in Hyper-V Server that handles networking, Remote Desktop enablement, and domain joining. All three are valid functions of this utility.

Pass-through disks provide highest performance by giving the VM direct access to physical storage without the VHD format overhead. Fixed VHDs add a virtualization layer, while dynamic VHDs can suffer from fragmentation.

Hyper-V virtual network adapters work with physical NICs at any standard Ethernet speed. The adapter's actual performance depends on the physical NIC speed, not a fixed limit.

The netsh command enables the Remote Administration rule group in Windows Firewall, allowing management tools from remote systems. Option A is for OCs setup, B is registry scripting, C lists OCs.

The VHD format used by Hyper-V 2008 R2 has a 2TB maximum due to 32-bit sector addressing. Newer VHDX format supports larger disks but wasn't available in 2008 R2.

Windows Server 2008 R2 Failover Clustering supports up to 16 nodes per cluster, double the 8-node limit from Server 2008. This allows larger virtualization environments with more physical hosts.

In SCVMM (System Center Virtual Machine Manager), ISO files must be added to the VMM library before they can be used to install operating systems on virtual machines. Burning to DVD (A), renaming to .img (C), or extracting to a folder (D) are not the correct methods for SCVMM-based VM deployment.

Hyper-V supports Automatic Private IP Addressing (APIPA) for self-configuring addresses when DHCP fails, Dynamic IP addresses via DHCP, and Static IP addresses configured manually. Classless IP Addressing (D) refers to CIDR notation, not a distinct IP address type.

The VMM Administrative Console manages all components of the virtual infrastructure: Physical Servers (the host machines), Virtual Servers (the VMs), the VMM Library (storage for ISOs, VHDs, profiles), and Virtual Networks (networking configuration). All components (E) are included.

Integration components (like Hyper-V Integration Services) are installed in guest VMs to accelerate hardware access for smoother performance. They enable features like time sync, heartbeat, and data exchange. They are not required for creating VMs (A), moving them (B), or basic access control (C).

Hyper-V Server 2008 R2 supports a maximum of 64 logical processors per host system. This was a significant increase from the original Hyper-V release and is a well-documented specification for the R2 version.

Hyper-V supports three types of virtual networks: External (connected to physical network), Internal (host-to-VM communication), and Private (VM-to-VM only). All three types (D) are fully supported.

For Hyper-V storage monitoring, you should track Physical Disk % Disk Read Time, % Disk Write Time, and % Idle Time counters. All three metrics (D) provide comprehensive visibility into storage performance and bottlenecks.

VMM 2008 has multiple prerequisites: Windows Server 2008 x64 edition, .NET Framework 3.0, and PowerShell 1.0. The 'Windows Remote Management tools' likely refers to WinRM which is also required. Since all components A-D are needed, option E (All of the above) is correct.

The Hyper-V Settings page in VMM allows configuration of multiple aspects: virtual hard disk paths/settings, keyboard behavior for VM connection, and managing saved credentials. Since all individual options A-C are valid settings that can be modified, option D (All of the above) is correct.

Snapshots in Hyper-V capture the complete state of a virtual machine at a point in time, including memory, disk state, and configuration. You can revert to a snapshot to restore the VM to that previous state. Live migration is for moving VMs between hosts, P2V converts physical to virtual, and neither are for restoration.