Manage Virtual Machines practice questions

Quick Migration

Why wrong: Quick migration requires the hosts to be part of a failover cluster and involves a brief pause in service while the VM state is saved to shared storage. It is not suitable for scenarios requiring zero downtime or for hosts that are not joined in a cluster configuration for high availability.

Storage Migration

Why wrong: Storage migration allows an administrator to move the virtual machine configuration files and virtual hard disks to a different storage location while the VM remains running. This process is independent of the host-to-host migration and focuses strictly on the storage subsystem to prevent I/O bottlenecks or hardware upgrades.

Hyper-V Replica

Why wrong: Hyper-V Replica is a disaster recovery tool that asynchronously replicates virtual machines from one host to another at defined intervals. It does not provide zero-downtime migration, as the replica VM is kept in an offline state and must be manually or automatically failed over during a scheduled or unscheduled outage.

Production Checkpoint

Why wrong: Production checkpoints use the Volume Shadow Copy Service in Windows guests to create a backup-consistent image of the virtual machine. While highly reliable for data integrity, they do not capture the current running memory state, meaning the VM will restart from a cold boot state if the checkpoint is later applied.

Recovery Checkpoint

Why wrong: Recovery checkpoints are not a standard feature type within the Hyper-V Manager interface for manual creation. This term is often confused with automated recovery points created by Azure Site Recovery or Hyper-V Replica, which serve different purposes related to long-term disaster recovery rather than immediate administrative rollbacks.

Differential Checkpoint

Why wrong: Differential is a term related to the underlying virtual hard disk structure rather than the administrative checkpoint type. While checkpoints create AVHDX files to store changes, the user interface requires selecting between Standard or Production to determine how the guest operating system and memory are handled during the capture process.

Active Directory Certificate Services

Why wrong: Active Directory Certificate Services provides PKI infrastructure but does not offer the specialized attestation or key release mechanisms required for Shielded VMs. While it can issue certificates used within the environment, it lacks the specific logic to verify host health against a known baseline before allowing a protected VM to boot.

Network Controller

Why wrong: Network Controller is a component of Software Defined Networking used to manage virtual and physical network infrastructure centrally. It does not play a role in the security attestation or encryption key management required to shield virtual machines from unauthorized access by host administrators or malicious software on the virtualization host.

Windows Defender Application Control

Why wrong: Windows Defender Application Control is used to restrict which applications and scripts are allowed to run on a host system. While it enhances host security, it is not the primary service responsible for the attestation of host health or the management of encryption keys for Shielded Virtual Machine environments.

Guest Service Interface

Why wrong: The Guest Service Interface allows the Hyper-V administrator to copy files to a running virtual machine without using a network connection. While useful for management tasks, it does not provide time synchronization or shutdown capabilities and is often disabled by default to reduce the attack surface of the virtual machine.

Data Exchange

Why wrong: Data Exchange, also known as Key-Value Pairs, allows the host and guest to share specific metadata about their configuration. While it helps in identifying VM versions and host names, it is not responsible for the synchronization of the system clock or the execution of guest operating system shutdown commands.

Heartbeat

Why wrong: Heartbeat is a service that allows the host to monitor the state of the guest operating system by sending regular signals. If the guest stops responding, the host identifies it as unresponsive, but this service itself does not facilitate the actual shutdown process or manage the system time settings.

External

Why wrong: An External virtual switch is bound to a physical network adapter, allowing virtual machines to access the physical network and interact with other physical devices and the internet. This is the standard choice for production servers that need to provide services to users across the entire organization's network.

Private

Why wrong: A Private virtual switch restricts communication exclusively to the virtual machines running on the host. It does not allow the virtual machines to communicate with the host operating system or the external network, providing the highest level of isolation for sensitive test environments or multi-tier application development labs.

Transparent

Why wrong: Transparent switches are typically used in container networking rather than standard Hyper-V virtual machine deployments. They allow containers to be treated as if they are directly connected to the physical network, which is a different use case than isolating virtual machines on a standard Windows Server Hyper-V host.

The VM uses a legacy BIOS and supports 32-bit operating systems only.

Why wrong: Generation 2 virtual machines use UEFI firmware rather than the legacy BIOS found in Generation 1. This provides support for modern features like Secure Boot and is specifically designed for 64-bit operating systems, which improves boot times and allows for more efficient hardware handling compared to legacy VM architectures.

The VM is configured with 4GB of startup memory and a 100GB virtual disk.

Why wrong: The cmdlet explicitly sets the -MemoryStartupBytes parameter to 4GB and defines a new virtual hard disk with a size of 100GB. This matches the standard requirements for a baseline server deployment, ensuring that the VM has enough resources to initialize the operating system and store the necessary application files.

The VM will automatically enable Dynamic Memory with a 100GB maximum.

Why wrong: While the command sets the startup memory, it does not include the parameters for Dynamic Memory, such as -DynamicMemory or -MemoryMaximumBytes. By default, the VM will use a static memory allocation of 4GB unless the administrator executes additional commands to enable and configure the dynamic memory range and buffer.

The VM disk is created using the older VHD format for compatibility.

Why wrong: The -NewVHDPath parameter specifies a file with the .vhdx extension. VHDX is the modern virtual disk format introduced with Windows Server 2012, which offers better performance, data corruption protection, and support for larger disk sizes up to 64TB, unlike the legacy VHD format which is limited to 2TB.

Hyper-V Replica Broker

Why wrong: The Hyper-V Replica Broker is used specifically for managing replication in a clustered environment, but it is not a requirement for the basic failover functionality of the cluster itself. It provides a unified contact point for replication traffic rather than the underlying mechanism that handles host failure and VM restart.

NIC Teaming on the VM

Why wrong: NIC Teaming within the guest virtual machine provides network redundancy for the guest but is not a component of the host-level high-availability cluster. While it improves the resilience of the VM's network connection, it does not facilitate the failover of the entire VM from one physical host to another.

VHDX with Dynamically Expanding

Why wrong: Dynamically expanding disks save space by only using as much physical storage as is currently needed by the guest. However, they introduce a slight performance penalty during write operations when the file must grow, and they are generally less preferred for high-I/O database workloads compared to fixed-size disks.

VHD with Fixed Size

Why wrong: The older VHD format is limited to 2TB and lacks the resiliency features found in VHDX, such as the ability to protect metadata from corruption during power failures. Using VHD for a modern database server is not recommended unless compatibility with very old versions of Hyper-V or Azure is required.

VHDX with Differencing

Why wrong: Differencing disks are used to store changes made to a parent disk and are common in VDI or lab environments to save space. They are not suitable for high-performance production databases because they introduce significant I/O overhead and create a dependency on the parent disk, increasing the risk of failure.

Change the number of Virtual Processors

Why wrong: Changing the number of virtual processors assigned to a VM requires the machine to be in a powered-off state. While Windows supports adding CPUs to physical servers (hot-add), Hyper-V does not currently support increasing or decreasing the vCPU count while the virtual machine is actively running its guest operating system.

Change the VM Generation from 1 to 2

Why wrong: The generation of a virtual machine is determined at the time of creation and defines the virtual hardware architecture, such as BIOS vs UEFI. It is a fundamental configuration that cannot be changed after the VM is created, regardless of whether the VM is running or powered off.

Expand the size of the Boot VHDX file

Why wrong: While you can expand a VHDX file while it is attached to a running VM, the guest operating system must then be told to recognize the new space. However, this is a storage operation rather than a hardware modification like adding a new adapter or adjusting the volatile memory allocation.

It automatically upgrades any VM to the D4s_v3 size.

Why wrong: The policy uses a 'deny' effect, which prevents the creation of non-compliant resources rather than modifying them. Azure Policy does not have an 'upgrade' mechanism in this context; it simply evaluates the request against the rules and rejects it if the specified SKU name is not in the allowed list.

It allows the creation of any VM size except the two listed.

Why wrong: The logic 'notIn' combined with 'deny' means that if the VM size is NOT one of the two listed, the request is denied. Therefore, it effectively restricts the administrator to using ONLY the Standard_D2s_v3 and Standard_D4s_v3 sizes, rejecting all other possible virtual machine SKUs in the Azure catalog.

It audits VMs that are not using the D2s or D4s sizes.

Why wrong: The 'effect' field is explicitly set to 'deny', which means the operation will be blocked immediately upon attempted creation. An 'audit' effect would allow the creation of the virtual machine but would flag the resource as non-compliant in the Azure Policy compliance dashboard for later review by administrators.

Startup RAM

Why wrong: Startup RAM defines the amount of memory the VM requires to boot. While important for the initial power-on sequence, it does not influence how the host prioritizes memory allocation once the guest is running or how it handles resource contention between multiple competing virtual machines on the same physical server.

Memory Buffer

Why wrong: The Memory Buffer is a percentage-based setting that determines how much 'extra' RAM Hyper-V attempts to assign to the VM as a cache. While it helps performance by providing extra space for the guest OS, it does not set the relative priority of the VM compared to others on the host.

Minimum RAM

Why wrong: Minimum RAM specifies the lowest amount of memory that Hyper-V can reclaim from the VM after it has finished booting. While this ensures the VM doesn't drop below a functional threshold, it is a boundary setting rather than a prioritization mechanism for allocating resources during periods of host-wide memory pressure.

Create a Virtual Fibre Channel SAN

Why wrong: Virtual Fibre Channel is used to provide a virtual machine with direct access to a Fibre Channel storage array. It has no relation to Hyper-V Replica, which is a software-based replication mechanism that operates at the host level to copy virtual hard disk changes over standard IP-based networks.

Install the Windows Server Backup feature

Why wrong: While Windows Server Backup is used for creating point-in-time backups of servers, it is not a prerequisite for Hyper-V Replica. Replica is a separate, continuous data protection feature that uses its own engine to track and transmit changes to virtual hard disks, independent of the standard backup infrastructure.

Generation 1

Why wrong: Generation 1 virtual machines use legacy BIOS firmware and emulate older hardware like IDE controllers for boot disks. They do not support modern security features like Secure Boot or the ability to boot directly from SCSI controllers, making them less suitable for modern Windows Server 2022 deployments.

Generation 3

Why wrong: There is currently no 'Generation 3' virtual machine type in Microsoft Hyper-V. The choice remains between Generation 1 for legacy compatibility and Generation 2 for modern, UEFI-based workloads. Microsoft continues to enhance Generation 2 rather than introducing a third generation for standard Windows Server virtualization tasks.

Azure Edition

Why wrong: Azure Edition usually refers to a specific version of the Windows Server operating system (like Windows Server 2022 Datacenter: Azure Edition) that includes cloud-specific features. It is not a virtual machine hardware generation type within the Hyper-V Manager or the New-VM PowerShell cmdlet.

Restart VM1 from within the guest operating system.

Why wrong: Restarting the VM from within the guest operating system only reboots the software environment and does not trigger the underlying Azure fabric to reallocate physical resources. To change the hardware profile, the VM must be stopped through the portal or PowerShell to allow for resource re-assignment.

Change the VM1 availability set to a proximity placement group.

Why wrong: Proximity placement groups are used to reduce network latency by ensuring VMs are physically close to each other, but they do not resolve hardware constraints during a resize operation. In fact, using a proximity placement group might further restrict the available hardware clusters for the new VM size.

Modify the Azure Resource Manager (ARM) policy for the resource group.

Why wrong: Azure Resource Manager policies are used to govern and restrict resource creation or configuration but do not facilitate the actual resizing process. Policies might prevent certain sizes from being chosen, but they cannot initiate the hardware change required to increase the CPU and memory of an existing VM.

Enable replication on Host2, shut down VM1 on Host1, and start VM1 on Host2.

Why wrong: Starting a replica VM without performing a formal failover process results in data inconsistency and potential split-brain scenarios. This approach does not synchronize the final changes from the primary server, leading to data loss and requiring a full resynchronization of the virtual hard disks once the primary host returns.

Turn off VM1 on Host1, click Failover on Host2, and then select the latest recovery point.

Why wrong: This sequence describes an unplanned failover, which is used during actual disasters. Using an unplanned failover for a scheduled event may result in small amounts of data loss because it relies on the last successful asynchronous replication point rather than performing a final synchronous update of all pending data.

Pause replication on Host1, export VM1 to Host2, and then resume replication on Host2.

Why wrong: Exporting and importing VMs is a manual migration method that is not part of the standard Hyper-V Replica failover workflow. This method is inefficient for disaster recovery scenarios because it does not utilize the built-in replication engine to track changes, resulting in significantly longer downtime and higher administrative overhead.

The Hyper-V hosts must have the Failover Clustering feature installed.

Why wrong: Shared Nothing Live Migration is specifically designed to work without Failover Clustering. While clustering provides high availability, it is not a requirement for this specific migration type, which focuses on moving VMs between independent hosts that do not share any underlying physical disk resources or cluster quorum.

The virtual machine must be configured with a static MAC address.

Why wrong: Hyper-V Live Migration handles MAC address management automatically during the move process. While static MAC addresses can be useful in certain networking scenarios, they are not a prerequisite for Shared Nothing Live Migration, as the hypervisor manages the transition of network identity across the different physical network interfaces.

A Virtual Fibre Channel adapter must be added to the virtual machine.

Why wrong: Virtual Fibre Channel is used to connect a guest VM directly to a Storage Area Network (SAN). Since Shared Nothing Live Migration is intended for environments without shared storage, requiring a Fibre Channel adapter would be contradictory to the goal of moving VMs between hosts with local storage.

To enable Discrete Device Assignment (DDA) for a GPU.

Why wrong: Discrete Device Assignment (DDA) is used to pass through a physical PCIe device directly to a virtual machine. This requires different PowerShell commands, such as Add-VMPassignDevice, and is unrelated to the virtualization extensions of the processor, which focus on enabling the hypervisor role within the guest OS.

To allow the VM to use Dynamic Memory across multiple NUMA nodes.

Why wrong: Dynamic Memory and NUMA spanning are managed through memory-specific settings in the VM configuration. The ExposeVirtualizationExtensions parameter specifically handles hardware-assisted virtualization features of the CPU, not the memory management or the spanning of resources across physical processor sockets or memory banks.

To activate the Shielded VM protection for a Linux-based guest.

Why wrong: Shielded VM protection is enabled using the Set-VMSecurity cmdlet and requires a Guardian and a shielding data file. It is a security feature involving encryption and attestation, whereas exposing virtualization extensions is a hardware feature pass-through designed to support secondary hypervisors inside the virtual machine.

Capacity Only

Why wrong: The 'Capacity Only' eviction policy means the VM will only be evicted if Azure needs the hardware capacity back for pay-as-you-go customers. This does not take the price into account, so the VM will continue running regardless of price fluctuations as long as the hardware cluster has available space.

Stop-Deallocate

Why wrong: Stop-Deallocate is an eviction 'type' rather than a 'policy.' It determines what happens to the VM when an eviction is triggered by the policy. Choosing this type ensures that the VM's state is preserved on disk, but it does not control the logic of why the eviction occurred.

Delete

Why wrong: Like Stop-Deallocate, 'Delete' is an eviction 'type' that defines the fate of the VM and its associated disks once the eviction policy is met. It is used for completely transient workloads where data does not need to be persisted, but it is not the policy that evaluates eviction criteria.

Performance Monitor

Why wrong: Performance Monitor is excellent for real-time tracking and creating detailed logs, but it is a general-purpose Windows tool. While it can monitor Hyper-V counters, it does not provide the simplified, per-VM historical aggregation that is specifically built into the Hyper-V resource metering feature for long-term capacity planning and reporting.

Azure Monitor

Why wrong: Azure Monitor is a cloud-based solution that can collect data from on-premises servers using agents. While powerful, it requires an Azure subscription and network connectivity to the cloud. For a local, built-in solution on a Windows Server host, Hyper-V resource metering provides a more direct and immediate way to track VM metrics.

Resource Metering

Why wrong: Resource Metering is a built-in Hyper-V feature enabled via PowerShell that collects resource usage data for a virtual machine. It tracks metrics such as average CPU use, average memory use, and total network traffic, allowing administrators to query the cumulative data at any time for reporting or capacity management.

Task Manager

Why wrong: Task Manager provides a snapshot of current resource utilization but lacks the ability to aggregate data over long periods or store historical metrics for analysis. It is useful for immediate troubleshooting of a slow system but is entirely insufficient for a 30-day capacity planning study involving specific virtual machine workloads.

Enable-WindowsOptionalFeature -FeatureName Microsoft-Hyper-V

Why wrong: This command is used to install the Hyper-V role on a Windows operating system. While it is necessary to run this inside the guest VM eventually, it will fail unless the physical host has first been configured to pass through the virtualization extensions to that specific virtual machine's hardware profile.

Set-VMNetworkAdapter -MacAddressSpoofing On

Why wrong: MAC address spoofing is often required in nested virtualization to allow the inner VMs to communicate over the network through the outer VM's adapter. However, this command does not enable the CPU's virtualization extensions, which is the primary hardware requirement for installing the Hyper-V role in a guest.

Set-VMMemory -DynamicMemoryEnabled $false

Why wrong: Nested virtualization in earlier versions of Hyper-V required static memory, but modern versions on Windows Server 2022 are more flexible. Regardless, disabling dynamic memory is not the action that enables the virtualization extensions needed to run a hypervisor within the guest; that requires a specific processor-level configuration.

Set-VMProcessor -ExposeVirtualizationExtensions $true

Why wrong: This command is the essential step for enabling nested virtualization. By setting the -ExposeVirtualizationExtensions parameter to true for a specific VM, the Hyper-V host passes the hardware-assisted virtualization features (like Intel VT-x or AMD-V) to the guest VM, allowing it to function as a hypervisor itself.