LPI 305-300 Dumps - Pass LPIC-3: Virtualization and Containerization - Exam 305, (version 3.0) in 2026

Kernel-based Virtual Machine (KVM) relies on hardware-assisted virtualization features provided by modern CPUs. On Intel CPU architectures, this support is enabled through the kvm_intel kernel module. Official KVM and Linux virtualization documentation clearly states that the required module for Intel processors is named kvm_intel, with the optional .ko suffix when referring to the kernel object file.

The provided solution lists multiple acceptable representations of the module name, including kvm_intel and kvm_intel.ko, both of which are valid and correct. Linux kernel module naming conventions allow the module to be referenced with or without the .ko suffix when loading it using tools such as modprobe or lsmod.

Although variants using a hyphen (kvm-intel) are not the canonical kernel module name, the solution explicitly includes the correct and documented module name. Therefore, the solution correctly identifies the required kernel module for enabling KVM on Intel CPUs.

Virtualization documentation emphasizes that KVM functionality requires both the generic kvm module and the CPU-specific module (kvm_intel for Intel or kvm_amd for AMD). Hence, the determination that the solution is correct aligns with verified documentation.

Packer is a tool that automates the creation of identical machine images for multiple platforms from a single source configuration. Packer works by creating an instance based on a source image, which is a pre-existing image that serves as a starting point. Packer then connects to the instance through a network connection, such as SSH or WinRM, and runs various commands and scripts to install and configure software within the instance. Packer then shuts down the instance and creates a new system image from it, which can be used to launch new instances. Packer supports many platforms, such as AWS, Azure, VMware, Docker, and others. Packer does not install any software or run any daemon within the target image, nor does it periodically connect to the running instances to re-apply the template. Packer also does not modify the source image directly, but creates a new image from the modified instance. Reference:

Packer by HashiCorp

HashiCorp Packer - Build Automated Machine Images

Introduction | Packer | HashiCorp Developer

Packer is an image automation tool used to create identical machine images for multiple platforms from a single configuration. According to virtualization and containerization documentation, Packer typically uses trusted and standardized base images as the starting point for image creation. The most common sources include official operating system images provided by vendors such as Red Hat, Ubuntu, or cloud service providers, and custom images created internally by an organization.

Using official images ensures that the base system is secure, properly maintained, and compliant with vendor standards. Organizations often build custom base images to enforce internal security policies, hardening standards, and preinstalled software, which Packer then extends into environment-specific images.

Physical servers are not considered common or practical base sources for Packer, as Packer operates on machine image artifacts rather than cloning live hardware systems. Images from untrusted sources are explicitly discouraged in virtualization documentation due to security and compliance risks.

Therefore, documentation clearly supports custom organizational images and official operating system images as the correct and recommended base sources for Packer image creation.

The foundational technology of Infrastructure as a Service (IaaS) is virtualization. Virtualization enables cloud providers to abstract physical hardware into flexible, on-demand virtual resources such as compute instances, storage, and networks.

All major IaaS platforms rely on virtualization to provide scalability, isolation, elasticity, and multi-tenancy. Without virtualization, the dynamic provisioning model of IaaS would not be possible.

Therefore, the correct answer is B.

A hypervisor is a software that creates and runs virtual machines (VMs) by separating the operating system and resources from the physical hardware. One of the main tasks of a hypervisor is to map the resources of VMs to the resources of the host system, such as CPU, memory, disk, and network. This allows the hypervisor to allocate and manage the resources among multiple VMs and ensure that they run efficiently and independently123. Another important task of a hypervisor is to isolate the VMs and prevent unauthorized access to resources of other VMs. This ensures the security and privacy of the VMs and their data, as well as the stability and performance of the host system. The hypervisor can use various techniques to isolate the VMs, such as virtual LANs, firewalls, encryption, and access control145.

The other tasks listed are not part of a hypervisor's responsibility, but rather of the guest operating system or the application running inside the VM. A hypervisor does not create filesystems during the installation of new VMs, as this is done by the installer of the guest operating system6. A hypervisor does not provide host-wide unique PIDs to the processes running inside the VMs, as this is done by the kernel of the guest operating system7. A hypervisor does not manage authentication to network services running inside a VM, as this is done by the network service itself or by a directory service such as LDAP or Active Directory8. Reference: 1 (search for ''What is a hypervisor?''), 2 (search for ''How does a hypervisor work?''), 3 (search for ''The hypervisor gives each virtual machine the resources that have been allocated''), 4 (search for ''Benefits of hypervisors''), 5 (search for ''Isolate the virtual machines and prevent unauthorized access''), 6 (search for ''Create filesystems during the installation of new virtual machine quest operating systems''), 7 (search for ''Provide host-wide unique PIDs to the processes running inside the virtual machines''), 8 (search for ''Manage authentication to network services running inside a virtual machine'').