[Apr 16, 2026] Get Unlimited Access to 305-300 Certification Exam Cert Guide
Reliable Study Materials for 305-300 Exam Success For Sure
NEW QUESTION # 69
How can data be shared between several virtual machines running on the same Linux-based host system?
- A. By mounting other virtual machines' file systems from /dev/virt-disks/remote/.
- B. By setting up a ramdisk in one virtual machine and mounting it using its UUID in the other VMs.
- C. By writing data to the file system since all virtual machines on the same host system use the same file system.
- D. By attaching the same virtual hard disk to all virtual machines and activating EXT4 sharing extensions on it.
- E. By using a network file system or file transfer protocol.
Answer: E
Explanation:
Explanation
The correct way to share data between several virtual machines running on the same Linux-based host system is by using a network file system or file transfer protocol. A network file system (NFS) is a distributed file system protocol that allows a user on a client computer to access files over a network in a manner similar to how local storage is accessed1. A file transfer protocol (FTP) is a standard network protocol used for the transfer of computer files between a client and server on a computer network2. Both methods allow data to be shared between virtual machines regardless of their underlying file systems or virtualization technologies. The other options are incorrect because they either do not work or are not feasible. Option A is wrong because each virtual machine has its own file system that is not directly accessible by other virtual machines. Option B is wrong because there is no such device as /dev/virt-disks/remote/ that can be used to mount other virtual machines' file systems. Option C is wrong because a ramdisk is a volatile storage device that is not suitable for sharing data between virtual machines. Option E is wrong because attaching the same virtual hard disk to multiple virtual machines can cause data corruption and conflicts, and EXT4 does not have any sharing extensions that can prevent this. References:https://kb.vmware.com/s/article/1012706
https://bing.com/search?q=data+sharing+between+virtual+machines
NEW QUESTION # 70
Xen is a:
- A. Type 1 hypervisor
- B. Application virtualization platform
- C. Type 2 hypervisor
- D. Virtualization management tool
Answer: A
Explanation:
Xen is classified as a Type 1 (bare-metal) hypervisor, meaning it runs directly on the system hardware rather than on top of a host operating system. Virtualization documentation defines Type 1 hypervisors as having direct control over CPU, memory, and hardware resources, providing better performance and stronger isolation compared to Type 2 hypervisors.
In a Xen-based system, the hypervisor is loaded first during boot. A privileged management domain, known as Domain 0 (Dom0), is then started to manage hardware access and virtual machine lifecycle operations.
This architecture clearly differentiates Xen from hosted (Type 2) hypervisors such as VirtualBox.
Xen is not merely a management tool or application virtualization platform; it is a full hypervisor used in enterprise, cloud, and service provider environments. Therefore, the correct answer is B.
NEW QUESTION # 71
Which of the following statements are true about sparse images in the context of virtual machine storage?
(Choose two.)
- A. Sparse images allocate backend storage at the first usage of a block.
- B. Sparse images may consume an amount of space different from their nominal size.
- C. Sparse images can only be used in conjunction with paravirtualization.
- D. Sparse images are automatically resized when their maximum capacity is about to be exceeded.
- E. Sparse images are automatically shrunk when files within the image are deleted.
Answer: A,B
Explanation:
Explanation
Sparse images are a type of virtual disk images that grow in size as data is written to them, but do not shrink when data is deleted from them. Sparse images may consume an amount of space different from their nominal size, which is the maximum size that the image can grow to. For example, a sparse image with a nominal size of 100 GB may only take up 20 GB of physical storage if only 20 GB of data is written to it. Sparse images allocate backend storage at the first usage of a block, which means that the physical storage is only used when the virtual machine actually writes data to a block. This can save storage space and improve performance, as the image does not need to be pre-allocated or zeroed out.
Sparse images are not automatically shrunk when files within the image are deleted, because the virtual machine does not inform the host system about the freed blocks. To reclaim the unused space, a special tool such as virt-sparsify1 or qemu-img2 must be used to compact the image. Sparse images can be used with both full virtualization and paravirtualization, as the type of virtualization does not affect the format of the disk image. Sparse images are not automatically resized when their maximum capacity is about to be exceeded, because this would require changing the partition table and the filesystem of the image, which is not a trivial task. To resize a sparse image, a tool such as virt-resize3 or qemu-img2 must be used to increase the nominal size and the filesystem size of the image. References: 1 (search for "virt-sparsify"), 2 (search for
"qemu-img"), 3 (search for "virt-resize").
NEW QUESTION # 72
In an IaaS cloud, what is a common method for provisioning new computing instances with an operating system and software?
- A. Each new instance is connected to the installation media of a Linux distribution and provides access to the installer by logging in via SSH.
- B. Each new instance contains a minimal live system running from a virtual CD as the basis from which the administrator deploys the target operating system.
- C. Each new instance is connected via a VPN with the computer that started the provisioning and tries to PXE boot from that machine.
- D. Each new instance is a clone of another currently running instance that includes all the software, data and state of the original instance.
- E. Each new instance is created based on an image file that contains the operating system as well as software and default configuration for a given purpose.
Answer: E
NEW QUESTION # 73
Which of the following statements are true about container-based virtualization? (Choose two.)
- A. All containers run within the operating system kernel of the host system.
- B. Different containers may use different distributions of the same operating system.
- C. Container-based virtualization relies on hardware support from the host system's CPU.
- D. Linux does not support container-based virtualization because of missingkernel APIs.
- E. Each container runs its own operating system kernel.
Answer: A,B
NEW QUESTION # 74
Which command within virsh lists the virtual machines that are running on the current host?
- A. show
- B. I view
- C. list
- D. list-vm
- E. list-all
Answer: C
Explanation:
Explanation
The command virsh list is used to list all running domains (VMs) on the current host. The command virsh list
--all can be used to list both active and inactive domains. The other options are not valid virsh commands. The command virsh list is a basic command that lists all running domains (VMs). You can also list all configured VMs by adding the --all option. This is useful if you want to see all VMs configured in the target hypervisor that you can use on subsequent commands1. References:
* 1: 8 Linux virsh subcommands for managing VMs on the command line | Enable Sysadmin.
NEW QUESTION # 75
What kind of virtualization is implemented by LXC?
- A. CPU emulation
- B. Hardware containers
- C. System containers
- D. Paravirtualization
- E. Application containers
Answer: C
NEW QUESTION # 76
Which statement is true regarding the Linux kernel module that must be loaded in order to use QEMU with hardware virtualization extensions?
- A. It must be loaded into the kernel of the host system only if the console of a virtual machine will be connected to a physical console of the host system
- B. It must be loaded into the kernel of the first virtual machine as it interacts with the QEMU bare metal hypervisor and is required to trigger the start of additional virtual machines
- C. It must be loaded into the kernel of each virtual machine that will access files and directories from the host system's file system.
- D. It must be loaded into the kernel of each virtual machine to provide Para virtualization which is required by QEMU.
- E. It must be loaded into the Kernel of the host system in order to use the visualization extensions of the host system's CPU
Answer: E
Explanation:
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. References:
* Features/KVM - QEMU
* Kernel-based Virtual Machine
* KVM virtualization on Red Hat Enterprise Linux 8 (2023)
NEW QUESTION # 77
When setting up a KVM virtualization host, which one of the following components is NOT required?
- A. qemu
- B. virsh
- C. libvirt
- D. bridgeutils
- E. kvm kernel modules
Answer: B
Explanation:
When configuring a KVM-based virtualization host, several core components are mandatory to enable and manage virtual machines. According to KVM and virtualization documentation,KVM kernel modulesare essential because they provide hardware-assisted virtualization support within the Linux kernel.QEMUis required to perform hardware emulation and manage virtual machine execution.Libvirtacts as the virtualization management API, enabling centralized and secure control of virtual machines. Additionally, bridgeutilsis commonly required to configure network bridges, allowing virtual machines to communicate with external networks.
However,virshisnot strictly required. Virsh is acommand-line utilitythat interacts with libvirt to manage virtual machines, but it is only amanagement interface, not a core dependency. Virtual machines can still be created and managed using alternative tools such asvirt-manager, Ansible, OpenStack, or custom API- based solutionswithout virsh being installed.
Virtualization documentation clearly distinguishes betweenessential backend components(KVM, QEMU, libvirt) andoptional management tools(virsh). Therefore, while virsh is widely used and highly recommended for administrative convenience, it isnot a mandatory componentfor a functional KVM virtualization host.
NEW QUESTION # 78
What is the purpose of capabilities in the context of container virtualization?
- A. Prevent processes from performing actions which might infringe the container.
- B. Allow regular users to start containers with elevated permissions.
- C. Restrict the disk space a container can consume.
- D. Map potentially dangerous system calls to an emulation layer provided by the container virtualization.
- E. Enable memory deduplication to cache files which exist in multiple containers.
Answer: A
NEW QUESTION # 79
If aDockerfilecontains the following lines:
WORKDIR /
RUN cd /tmp
RUN echo test > test
where is the filetestlocated?
- A. /tmp/test on the system running docker build.
- B. /test within the container image.
- C. /ting/test within the container image.
- D. /root/tesc within the container image.
- E. test in the directory holding the Dockerf ile.
Answer: B
NEW QUESTION # 80
Which of the following components are essential in Docker architecture? (Select all that apply)
- A. Docker Daemon
- B. Docker Registry
- C. Docker Client
- D. Docker Compose
Answer: A,B,C
NEW QUESTION # 81
Which of the following commands deletes all volumes which are not associated with a container?
- A. docker volume prune
- B. docker volume garbage-collect
- C. docker volume cleanup
- D. docker volume vacuum
- E. docker volume orphan -d
Answer: A
Explanation:
Explanation
The command that deletes all volumes which are not associated with a container is docker volume prune. This command removes all unused local volumes, which are those that are not referenced by any containers. By default, it only removes anonymous volumes, which are those that are not given a specific name when they are created. To remove both unused anonymous and named volumes, the --all or -a flag can be added to the command. The command will prompt for confirmation before deleting the volumes, unless the --force or -f flag is used to bypass the prompt. The command will also show the total reclaimed space after deleting the volumes12.
The other commands listed in the question are not valid or do not have the same functionality as docker volume prune. They are either made up, misspelled, or have a different purpose. These commands are:
* docker volume cleanup: This command does not exist in Docker. There is no cleanup subcommand for docker volume.
* docker volume orphan -d: This command does not exist in Docker. There is no orphan subcommand for docker volume, and the -d flag is not a valid option for any docker volume command.
* docker volume vacuum: This command does not exist in Docker. There is no vacuum subcommand for docker volume.
* docker volume garbage-collect: This command does not exist in Docker. There is no garbage-collect subcommand for docker volume.
References:
* docker volume prune | Docker Docs
* How to Remove all Docker Volumes - YallaLabs.
NEW QUESTION # 82
Which of the following commands deletes all volumes which are not associated with a container?
- A. docker volume prune
- B. docker volume garbage-collect
- C. docker volume cleanup
- D. docker volume vacuum
- E. docker volume orphan -d
Answer: A
Explanation:
The command that deletes all volumes which are not associated with a container is docker volume prune. This command removes all unused local volumes, which are those that are not referenced by any containers. By default, it only removes anonymous volumes, which are those that are not given a specific name when they are created. To remove both unused anonymous and named volumes, the --all or -a flag can be added to the command. The command will prompt for confirmation before deleting the volumes, unless the --force or - f flag is used to bypass the prompt. The command will also show the total reclaimed space after deleting the volumes12.
The other commands listed in the question are not valid or do not have the same functionality as docker volume prune. They are either made up, misspelled, or have a different purpose. These commands are:
* docker volume cleanup: This command does not exist in Docker. There is no cleanup subcommand for docker volume.
* docker volume orphan -d: This command does not exist in Docker. There is no orphan subcommand for docker volume, and the -d flag is not a valid option for any docker volume command.
* docker volume vacuum: This command does not exist in Docker. There is no vacuum subcommand for docker volume.
* docker volume garbage-collect: This command does not exist in Docker. There is no garbage- collect subcommand for docker volume.
:
docker volume prune | Docker Docs
How to Remove all Docker Volumes - YallaLabs.
NEW QUESTION # 83
What does IaaS stand for?
- A. Integration as a Service
- B. Instances as a Service
- C. Infrastructure as a Service
- D. Intelligence as a Service
- E. Information as a Service
Answer: C
NEW QUESTION # 84
Which of the following resources can be limited by libvirt for a KVM domain? (Choose two.)
- A. Amount of CPU lime
- B. File systems allowed in the domain
- C. Size of available memory
- D. Number of available files
- E. Number of running processes
Answer: A,C
Explanation:
Libvirt is a toolkit that provides a common API for managing different virtualization technologies, such as KVM, Xen, LXC, and others. Libvirt allows users to configure and control various aspects of a virtual machine (also called a domain), such as its CPU, memory, disk, network, and other resources. Among the resources that can be limited by libvirt for a KVM domain are:
* Amount of CPU time: Libvirt allows users to specify the number of virtual CPUs (vCPUs) that a domain can use, as well as the CPU mode, model, topology, and tuning parameters. Users can also set the CPU shares, quota, and period to control the relative or absolute amount of CPU time that a domain can consume. Additionally, users can pin vCPUs to physical CPUs or NUMA nodes to improve performance and isolation. These settings can be configured in the domain XML file under the <cpu> and <cputune> elements12.
* Size of available memory: Libvirt allows users to specify the amount of memory that a domain can use, as well as the memory backing, tuning, and NUMA node parameters. Users can also set the memory hard and soft limits, swap hard limit, and minimum guarantee to control the memory allocation and reclaim policies for a domain. These settings can be configured in the domain XML file under the <memory>, <memoryBacking>, and <memtune> elements13.
The other resources listed in the question are not directly limited by libvirt for a KVM domain. File systems allowed in the domain are determined by the disk and filesystem devices that are attached to the domain, which can be configured in the domain XML file under the <disk> and <filesystem> elements14. Number of running processes and number of available files are determined by the operating system and the file system of the domain, which are not controlled by libvirt.
:
libvirt: Domain XML format
CPU Allocation
Memory Allocation
Hard drives, floppy disks, CDROMs
NEW QUESTION # 85
Which file in acgroupdirectory contains the list of processes belonging to thiscgroup?
- A. subjects
- B. procs
- C. pids
- D. casks
- E. members
Answer: B
Explanation:
The file procs in a cgroup directory contains the list of processes belonging to this cgroup. Each line in the file shows the PID of a process that is a member of the cgroup. A process can be moved to a cgroup by writing its PID into the cgroup's procs file. For example, to move the process with PID 24982 to the cgroup cg1, the following command can be used: echo 24982 > /sys/fs/cgroup/cg1/procs1. The file procs is different from the file tasks, which lists the threads belonging to the cgroup. The file procs can be used to move all threads in a thread group at once, while the file tasks can be used to move individual threads2. References:
* Creating and organizing cgroups cgroup2 - GitHub Pages
* Control Groups - The Linux Kernel documentation
NEW QUESTION # 86
Which of the following statements are true about sparse images in the context of virtual machine storage?
(Choose two.)
- A. Sparse images allocate backend storage at the first usage of a block.
- B. Sparse images may consume an amount of space different from their nominal size.
- C. Sparse images can only be used in conjunction with paravirtualization.
- D. Sparse images are automatically resized when their maximum capacity is about to be exceeded.
- E. Sparse images are automatically shrunk when files within the image are deleted.
Answer: A,B
Explanation:
Sparse images are a type of virtual disk images that grow in size as data is written to them, but do not shrink when data is deleted from them. Sparse images may consume an amount of space different from their nominal size, which is the maximum size that the image can grow to. For example, a sparse image with a nominal size of 100 GB may only take up 20 GB of physical storage if only 20 GB of data is written to it. Sparse images allocate backend storage at the first usage of a block, which means that the physical storage is only used when the virtual machine actually writes data to a block. This can save storage space and improve performance, as the image does not need to be pre-allocated or zeroed out.
Sparse images are not automatically shrunk when files within the image are deleted, because the virtual machine does not inform the host system about the freed blocks. To reclaim the unused space, a special tool such as virt-sparsify1 or qemu-img2 must be used to compact the image. Sparse images can be used with both full virtualization and paravirtualization, as the type of virtualization does not affect the format of the disk image. Sparse images are not automatically resized when their maximum capacity is about to be exceeded, because this would require changing the partition table and the filesystem of the image, which is not a trivial task. To resize a sparse image, a tool such as virt-resize3 or qemu-img2 must be used to increase the nominal size and the filesystem size of the image. References: 1 (search for "virt-sparsify"), 2 (search for "qemu- img"), 3 (search for "virt-resize").
NEW QUESTION # 87
What is the name of the kernel module that is required to be loaded in order to use KVM on an Intel CPU architecture?
(Specify ONLY the module name without any path information and with or without the module suffix.) Solution:
kvm-intel.ko - or - kvm-intel - or - kvm_intel.ko - or - kvm_intel
Determine whether the given solution is correct?
- A. Correct
- B. Incorrect
Answer: A
Explanation:
Kernel-based Virtual Machine (KVM) relies on hardware-assisted virtualization features provided by modern CPUs. OnIntel CPU architectures, this support is enabled through thekvm_intelkernel module. Official KVM and Linux virtualization documentation clearly states that the required module for Intel processors is namedkvm_intel, with the optional .ko suffix when referring to the kernel object file.
The provided solution lists multiple acceptable representations of the module name, includingkvm_inteland 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 solutioncorrectly identifies the required kernel modulefor 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 iscorrectaligns with verified documentation.
NEW QUESTION # 88
What is the purpose of a .dockerignore file?
- A. It lists files existing in a Docker image which should be excluded when building a derivative image.
- B. It must be placed in the top level directory of volumes that Docker should never attach automatically to a container
- C. It specifies which parts of a Dockerfile should be ignored when building a Docker image.
- D. It exists in the root file system of containers that should ignore volumes and ports provided by Docker.
- E. It specifies files that Docker does not submit to the Docker daemon when building a Docker image
Answer: E
NEW QUESTION # 89
What does IaaS stand for?
- A. Integration as a Service
- B. Instances as a Service
- C. Infrastructure as a Service
- D. Intelligence as a Service
- E. Information as a Service
Answer: C
Explanation:
IaaS is a type of cloud computing service that offers essential compute, storage, and networking resources on demand, on a pay-as-you-go basis. IaaS is one of the four types of cloud services, along with software as a service (SaaS), platform as a service (PaaS), and serverless12. IaaS eliminates the need for enterprises to procure, configure, or manage infrastructure themselves, and they only pay for what they use23. Some examples of IaaS providers are Microsoft Azure, Google Cloud, and Amazon Web Services.
NEW QUESTION # 90
Which of the following commands executes a command in a running LXC container?
- A. lxc-batch
- B. lxc-enter
- C. lxc-accach
- D. lxc-run
- E. lxc-eval
Answer: C
NEW QUESTION # 91
In an IaaS cloud, what is a common method for provisioning new computing instances with an operating system and software?
- A. Each new instance is connected to the installation media of a Linux distribution and provides access to the installer by logging in via SSH.
- B. Each new instance contains a minimal live system running from a virtual CD as the basis from which the administrator deploys the target operating system.
- C. Each new instance is connected via a VPN with the computer that started the provisioning and tries to PXE boot from that machine.
- D. Each new instance is a clone of another currently running instance that includes all the software, data and state of the original instance.
- E. Each new instance is created based on an image file that contains the operating system as well as software and default configuration for a given purpose.
Answer: E
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. References:
* 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?
NEW QUESTION # 92
What is true aboutcontainerd?
- A. It runs in each Docker container and provides DHCP client functionality
- B. It uses rune to start containers on a container host.
- C. It is the initial process run at the start of any Docker container.
- D. It is a text file format defining the build process of containers.
- E. It requires the Docker engine and Docker CLI to be installed.
Answer: B
Explanation:
Explanation
Containerd is an industry-standard container runtime that uses Runc (a low-level container runtime) by default, but can be configured to use others as well1. Containerd manages the complete container lifecycle of its host system, from image transfer and storage to containerexecution and supervision1. It supports the standards established by the Open Container Initiative (OCI)1. Containerd does not require the Docker engine and Docker CLI to be installed, as it can be used independently or with other container platforms2. Containerd is not a text file format, nor does it run in each Docker container or provide DHCP client functionality. Containerd is not the initial process run at the start of any Docker container, as that is the role of the container runtime, such as Runc3. References: 1 (search for "containerd"), 2 (search for "Containerd is an open source"), 3 (search for "It uses rune to start containers").
NEW QUESTION # 93
Which of the following tools is not typically used for VM provisioning and image creation?
- A. cloud-init
- B. Kubernetes
- C. Vagrant
- D. Packer
Answer: B
Explanation:
VM provisioning and image creation tools are used tobuild, configure, and initialize virtual machine images. According to virtualization documentation,Packeris specifically designed for automated image creation,Vagrantis used for provisioning reproducible development environments, andcloud-initis used to configure instances at first boot.
Kubernetes, however, is acontainer orchestration platform, not a VM provisioning or image creation tool.
It manages containerized workloads after infrastructure has already been provisioned.
Documentation clearly separatesinfrastructure provisioning toolsfromapplication orchestration platforms
. As such, Kubernetes is not typically used for VM provisioning or image creation.
Therefore, the correct answer isA.
NEW QUESTION # 94
......
New Lpi 305-300 Dumps & Questions: https://evedumps.testkingpass.com/305-300-testking-dumps.html