1V0-2120 Sample Questions & Answers

The fundamental difference is that a template is a non-runnable master image. It cannot be powered on or edited directly, ensuring its integrity as a gold standard. To update it, you must convert it back to a VM. In contrast, when you clone a VM, the source VM remains a fully functional, editable virtual machine that can be powered on and modified independently of its clones.

This solution meets all requirements. Keeping Admission Control enabled ensures that sufficient resources are reserved for failovers (Requirement 1). Using VM Overrides allows for granular control over restart order. Setting the patient record VMs to 'Highest' priority ensures they restart first (Requirement 1). Setting the administrative VMs to 'Low' priority means they will only restart after the high-priority ones and if resources permit (Requirement 2). The process is automated by HA (Requirement 3). Simply setting a percentage reservation doesn't control restart order. Disabling admission control is risky and could prevent high-priority VMs from restarting. Proactive HA is for hardware degradation, not host failure response.

The .vswp file is the virtual machine swap file. It is created when a VM is powered on and is used by the ESXi host to reclaim memory if the host becomes memory-overcommitted. It allows the hypervisor to swap memory pages from the VM's RAM to disk, freeing up physical RAM for other VMs. Its size is equal to the amount of unreserved VM memory.

EVC works by establishing a baseline of CPU features based on the oldest processor generation in the cluster. It then instructs the hypervisors on hosts with newer CPUs to 'mask' or hide the advanced features from the guest operating systems of the virtual machines. This ensures that all VMs in the cluster see a consistent set of CPU features, allowing them to be freely migrated between any hosts in the cluster without causing guest OS instability.

VMware Tools is a suite of utilities that enhances the performance of the virtual machine's guest operating system and improves management of the VM. It includes optimized drivers for virtual hardware (like the VMXNET3 NIC and paravirtual SCSI controller), enables features like graceful shutdown/restart from the vSphere Client, and facilitates communication between the guest OS and the host (e.g., time synchronization, heartbeat for HA).

VMFS-5 had multiple block size options (1MB, 2MB, 4MB, 8MB), which determined the maximum file size. A 4TB disk would require a block size of 2MB or larger. VMFS-6, however, uses a standardized 1MB block size. A Storage vMotion of a large VMDK from a VMFS-5 datastore with a large block size to a VMFS-6 datastore with a 1MB block size is not supported and will fail. The migration must be done while the VM is powered off (cold migration) to allow the disk format to be converted.

The 'Virtual Machine Power User' role provides permissions for most VM operations, including power state changes, console interaction, and snapshot management. Crucially, it does not include the privilege to edit a VM's settings, such as changing its hardware configuration. This aligns perfectly with the principle of least privilege for the junior operators' required tasks.

A vSphere Distributed Switch (VDS) provides centralized management through vCenter Server. An administrator configures the VDS once, and the configuration is consistently applied across all ESXi hosts that are added to it. VDS also enables advanced features unavailable on a Standard Switch, such as Network I/O Control (NIOC), Port Mirroring, and LACP. Configuration is not done on individual hosts, and it requires vCenter Server for its management plane.

A Type 1 hypervisor, also known as a bare-metal hypervisor, runs directly on the host's hardware to control the hardware and to manage guest operating systems. VMware ESXi is a prime example of a Type 1 hypervisor. A Type 2 hypervisor, or hosted hypervisor, runs on a conventional operating system just like other software applications.

This statement is true. vSphere Fault Tolerance (FT) provides the highest level of availability by creating a complete duplicate of a primary VM on a separate host. The two VMs are kept in 'lockstep' using vLockstep technology. If the host running the primary VM fails, the secondary VM instantly takes over with no interruption in service, thus achieving zero downtime and zero data loss. This is a higher level of protection than vSphere HA, which restarts a failed VM.