305-300 Exam Preparation Material | LPIC-3: Virtualization and Containerization - Exam 305, version 3.0

Explanation:
The Linux kernel module that must be loaded in order to use QEMU with hardware virtualization extensions is KVM (Kernel-based Virtual Machine). KVM is a full virtualization solution that allows a user space program (such as QEMU) to utilize the hardware virtualization features of various processors (such as Intel VT or AMD-V). KVM consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. KVM must be loaded into the kernel of the host system in order to use the virtualization extensions of the host system’s CPU. This enables QEMU to run multiple virtual machines with unmodified Linux or Windows images, each with private virtualized hardware. KVM is integrated with QEMU, so there is no need to load it into the kernel of each virtual machine or the first virtual machine. KVM also does not require paravirtualization, which is a technique that modifies the guest operating system to communicate directly with the hypervisor, bypassing the emulation layer.
Reference: Features/KVM - QEMU
Kernel-based Virtual Machine
KVM virtualization on Red Hat Enterprise Linux 8 (2023)

Explanation:
In an IaaS cloud, the most common method for provisioning new computing instances is to use an image file that contains a pre-installed operating system and software. This image file is also known as a machine image, a virtual appliance, or a template. The image file can be customized for a specific purpose, such as a web server, a database server, or a development environment. The image file can be stored in a repository or a library that is accessible by the cloud provider or the user. When a new instance is requested, the cloud provider copies the image file to a virtual disk and attaches it to the instance. The instance then boots from the virtual disk and runs the operating system and software from the image file. This method is faster and more efficient than installing the operating system and software from scratch for each new instance. It also ensures consistency and reliability across multiple instances that use the same image file.
Reference: LPI Virtualization and Containerization Exam Objectives, Topic 305.1: Virtualization Concepts and Theory, Objective: Describe the concept of machine images and templates LPI Virtualization and Containerization Study Guide, Chapter 1: Virtualization Concepts and Theory, Section: Machine Images and Templates LPI LPIC-3 305 Certification Sample Questions and Practice Exam, Question 10: In an IaaS cloud, what is a common method for provisioning new computing instances with an operating system and software?

Explanation:
LXC stands for Linux Containers, a lightweight virtualization technology that enables multiple isolated Linux systems (containers) to run on a single Linux host. Virtualization and containerization documentation describes LXC as a container-based virtualization solution that uses Linux kernel features such as namespaces, control groups (cgroups), and capabilities to provide process isolation without requiring a full hypervisor.
Unlike traditional virtual machines, LXC containers share the host kernel, which significantly reduces overhead and improves performance. Each container behaves like an independent Linux system with its own process tree, network interfaces, and filesystem, while still relying on the host kernel for execution.
LXC is often referred to as “system containers”, as it allows running full Linux distributions inside containers, unlike application-focused containers such as Docker. It serves as the foundation for higher-level container platforms, including LXD, which provides enhanced management features and APIs.
The other options are incorrect because they do not align with established Linux container terminology. Official Linux container documentation consistently defines LXC as Linux Containers, making option B the correct answer.

Explanation:
Packer is an image automation and building tool developed by HashiCorp. According to virtualization and DevOps documentation, Packer is used to create machine images for multiple platforms from a single configuration file.
Packer is not an orchestration platform, configuration management tool, or hypervisor. Its primary role is to ensure consistent, repeatable, and automated image creation, making B the correct answer.

Explanation:
The purpose of a .dockerignore file is to specify files that Docker does not submit to the Docker daemon when building a Docker image. A .dockerignore file is a text file that contains a list of files or directories that should be excluded from the build context, which is the set of files and folders that are available for use in a Dockerfile. By using a .dockerignore file, you can avoid sending files or directories that are large, contain sensitive information, or are irrelevant to the Docker image to the daemon, which can improve the efficiency and security of the build process. The other options are incorrect because they do not describe the function of a .dockerignore file. Option A is wrong because a .dockerignore file does not affect the files existing in a Docker image, but only the files sent to the daemon during the build. Option C is wrong because a .dockerignore file does not exist in the root file system of containers, but in the same directory as the Dockerfile. Option D is wrong because a .dockerignore file does not affect the volumes that Docker attaches to a container, but only the files included in the build context. Option E is wrong because a .dockerignore file does not affect the parts of a Dockerfile that are executed, but only the files available for use in a Dockerfile.
Reference: What are .dockerignore files, and why you should use them?
Dockerfile reference | Docker Docs
How to use .dockerignore and its importance - Shisho Cloud