305-300 LPIC-3: Virtualization and Containerization - Exam 305, version 3.0 Questions and Answers

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 independently 1 2 3 . 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 control 1 4 5 .

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 system 6 .  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 system 7 .  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 Directory 8 .  References :  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”).

Full virtualization is a virtualization approach where the hypervisor provides a complete simulation of the underlying hardware, allowing unmodified guest operating systems to run without awareness of virtualization. Virtualization documentation consistently states that one of the defining characteristics of full virtualization is that guest operating systems do not need to be modified , making option C correct.

Additionally, modern full virtualization platforms benefit from hardware-assisted virtualization , such as Intel VT-x and AMD-V CPU extensions. These extensions significantly improve performance by offloading virtualization tasks to the processor, making option B correct.

Option A is incorrect because Linux-based hypervisors like KVM can perform full virtualization entirely within the Linux ecosystem. Option D is false because all virtualization introduces some performance overhead, even if minimal. Option E is incorrect because full virtualization is widely used in production environments, including enterprise data centers and cloud platforms.

Therefore, based on virtualization principles and documentation, the correct answers are B and C .

LXC implements system containers, which are a type of operating-system-level virtualization. System containers allow running multiple isolated Linux systems on a single Linux control host, using a single Linux kernel. System containers share the same kernel with the host and each other, but have their own file system, libraries, and processes. System containers are different from application containers, which are designed to run a single application or service in an isolated environment. Application containers are usually smaller and more portable than system containers, but also more dependent on the host kernel and libraries. Hardware containers, CPU emulation, and paravirtualization are not related to LXC, as they are different kinds of virtualization methods that involve hardware abstraction, instruction translation, or modification of the guest operating system.  References :

1 : LXC - Wikipedia

2 : Linux Virtualization : Linux Containers (lxc) - GeeksforGeeks

3 : Features - Proxmox Virtual Environment

In Linux-based virtualization environments, qemu-img is the standard utility used to create, convert, inspect, and manage virtual machine disk images. Virtualization and containerization documentation clearly identifies qemu-img as a core component of the QEMU/KVM virtualization stack . It supports multiple disk image formats such as RAW, QCOW2, VMDK, and VHD, making it highly versatile across different hypervisors and platforms.

The qemu-img tool allows administrators to perform critical disk operations, including creating new disk images, resizing existing images, converting between formats, and checking disk integrity. For example, it is commonly used to create QCOW2 images , which support advanced features like copy-on-write, snapshots, and compression.

Other options listed are incorrect because Disk Utility is a general-purpose storage management tool, VirtualBox Manager is specific to Oracle VirtualBox, and Libvirt Disk Manager is not a recognized standalone utility. Libvirt relies on qemu-img internally for disk image handling.

Official virtualization notes consistently reference qemu-img as the primary disk image management tool in Linux virtualization environments, especially when working with KVM and libvirt-based systems.

The purpose of the packer inspect subcommand is to display an overview of the configuration contained in a Packer template 1 .  A Packer template is a file that defines the various components a Packer build requires, such as variables, sources, provisioners, and post-processors 2 .  The packer inspect subcommand can help you quickly learn about a template without having to dive into the HCL (HashiCorp Configuration Language) itself 1 .  The subcommand will tell you things like what variables a template accepts, the sources it defines, the provisioners it defines and the order they’ll run, and more 1 .

The other options are not correct because:

A) Retrieve files from an existing Packer image. This is not the purpose of the packer inspect subcommand.  To retrieve files from an existing Packer image, you need to use the packer scp subcommand, which copies files from a running instance of a Packer image to your local machine 2 .

B) Execute commands within a running instance of a Packer image. This is not the purpose of the packer inspect subcommand.  To execute commands within a running instance of a Packer image, you need to use the packer ssh subcommand, which connects to a running instance of a Packer image via SSH and runs the specified command 2 .

C) List the artifacts created during the build process of a Packer image. This is not the purpose of the packer inspect subcommand.  To list the artifacts created during the build process of a Packer image, you need to use the packer build subcommand with the -machine-readable flag, which outputs the build information in a machine-friendly format that includes the artifact details 2 .

D) Show usage statistics of a Packer image. This is not the purpose of the packer inspect subcommand.  To show usage statistics of a Packer image, you need to use the packer console subcommand with the -stat flag, which launches an interactive console that allows you to inspect and modify variables, sources, and functions, and displays the usage statistics of the current session 2 .  References :  1 : packer inspect - Commands | Packer | HashiCorp Developer  2 : Commands | Packer | HashiCorp Developer

 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 commands 1 .  References :

1 : 8 Linux virsh subcommands for managing VMs on the command line | Enable Sysadmin.

Vagrant supports multiple providers , allowing it to work with different virtualization and container platforms. According to official Vagrant documentation, supported providers include VirtualBox , VMware , and Docker .

VirtualBox is the default and most commonly used provider. VMware is supported through official plugins. Docker is also supported as a provider, enabling lightweight container-based development environments.

Option D (“Haws”) is an apparent typographical error and does not correspond to a valid virtualization platform. While Vagrant can integrate with AWS via community or third-party plugins, the option as written is invalid.

Therefore, the correct answers are A, B, and C .

Libvirt is a virtualization management API, toolkit, and set of command-line utilities designed to manage virtualization platforms in a consistent and secure manner. According to official virtualization and containerization documentation, libvirt provides a common interface for interacting with multiple hypervisors such as KVM, QEMU, Xen, VMware ESXi, and Hyper-V , abstracting their underlying differences.

Libvirt itself is not a virtualization technology or hypervisor ; rather, it acts as a management layer between administrators or orchestration tools and the hypervisor. It enables tasks such as creating, starting, stopping, pausing, migrating, and monitoring virtual machines. Tools like virsh and virt-manager rely on libvirt to perform virtualization operations.

One of libvirt’s key strengths is its focus on security and isolation . It integrates with Linux security frameworks such as SELinux and AppArmor , enforcing mandatory access controls on virtual machines. Libvirt also supports remote management using secure protocols, making it suitable for enterprise and cloud environments.

In virtualization documentation, libvirt is described as a foundational component for Infrastructure as Code and automation , commonly used with tools like Ansible, OpenStack, and Kubernetes (via KVM) . Its standardized API simplifies virtualization management while ensuring portability, scalability, and compliance with best practices.

The WORKDIR instruction sets the working directory for any subsequent RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile 1 .  The RUN instruction executes commands in a new layer on top of the current image and commits the results 2 .  The RUN cd command does not change the working directory for the next RUN instruction, because each RUN command runs in a new shell and a new environment 3 . Therefore, the file test is created in the root directory (/) of the container image, not in the /tmp directory.  References :

Dockerfile reference: WORKDIR

Dockerfile reference: RUN

difference between RUN cd and WORKDIR in Dockerfile

Resource management for full virtualization is the process of allocating and controlling the physical resources of the host system to the virtual machines running on it. The hypervisor is the software layer that performs this task, by providing each virtual machine with a virtual hardware of a defined capacity that limits the resources of the virtual machine. For example, the hypervisor can specify how many virtual CPUs, how much memory, and how much disk space each virtual machine can use. The hypervisor can also enforce resource isolation and prioritization among the virtual machines, to ensure that they do not interfere with each other or consume more resources than they are allowed to. The hypervisor cannot provide fine-grained limits to internal elements of the guest operating system, such as the number of processes, because the hypervisor does not have access to the internal state of the guest operating system. The guest operating system is responsible for managing its own resources within the virtual hardware provided by the hypervisor. For example, the guest operating system can create an arbitrary amount of network sockets, as long as it does not exceed the network bandwidth allocated by the hypervisor. Full virtualization can pose limits to virtual machines, and does not always assign the host system’s resources in a first-come-first-serve manner. The hypervisor can use various resource management techniques, such as reservation, limit, share, weight, and quota, to allocate and control the resources of the virtual machines. The hypervisor can also use resource scheduling algorithms, such as round-robin, fair-share, or priority-based, to distribute the resources among the virtual machines according to their needs and preferences. All processes created within the virtual machines are not transparently and equally scheduled in the host system for CPU and I/O usage. The hypervisor can use different scheduling policies, such as proportional-share, co-scheduling, or gang scheduling, to schedule the virtual CPUs of the virtual machines on the physical CPUs of the host system. The hypervisor can also use different I/O scheduling algorithms, such as deadline, anticipatory, or completely fair queuing, to schedule the I/O requests of the virtual machines on the physical I/O devices of the host system. The hypervisor can also use different resource accounting and monitoring mechanisms, such as cgroups, perf, or sar, to measure and report the resource consumption and performance of the virtual machines.  References :

Oracle VM VirtualBox: Features Overview

Resource Management as an Enabling Technology for Virtualization - Oracle

Introduction to virtualization and resource management in IaaS | Cloud Native Computing Foundation

To establish a private, isolated network between KVM virtual machines on the same host, Linux networking tools are used to create and manage virtual network bridges and TAP interfaces . According to KVM and Linux virtualization documentation, the core components required are brctl , tunctl , and ifconfig (or the modern ip command).

The brctl utility is used to create and manage Linux bridge interfaces, which act as virtual switches connecting multiple virtual machines. tunctl is used to create TAP interfaces that allow virtual machines to connect to the bridge. ifconfig is used to bring interfaces up and assign network parameters.

ebtables is not strictly required for creating a private network; it is used for filtering Ethernet frames. ipconfig is a Windows networking command and is not applicable to Linux systems.

Therefore, the correct and documented answers are B, D, and E .

 The correct way to start a new container that shares the /data volume with the datastore container is to use the --volumes-from flag. This flag mounts all the defined volumes from the referenced containers. In this case, the datastore container has a volume named /data, which is mounted in the service container at the same path. The other options are incorrect because they either use invalid flags, such as --share-with or --volume-backend, or they create new volumes instead of sharing the existing one, such as -v datastore:/data or -v /data.  References :

Docker Docs - Volumes

Stack Overflow - How to map volume paths using Docker’s --volumes-from?

Docker Docs - docker run

 LXC and Docker are both container technologies that use Linux kernel features to create isolated environments for running applications. The main mechanisms that they use are:

Linux Capabilities : These are a set of privileges that can be assigned to processes to limit their access to certain system resources or operations. For example, a process with the CAP_NET_ADMIN capability can perform network administration tasks, such as creating or deleting network interfaces. Linux capabilities allow containers to run with reduced privileges, enhancing their security and isolation.

Kernel Namespaces : These are a way of creating separate views of the system resources for different processes. For example, a process in a mount namespace can have a different file system layout than the host or other namespaces. Kernel namespaces allow containers to have their own network interfaces, process IDs, user IDs, and other resources, without interfering with the host or other containers.

Control Groups : These are a way of grouping processes and applying resource limits and accounting to them. For example, a control group can limit the amount of CPU, memory, disk I/O, or network bandwidth that a process or a group of processes can use. Control groups allow containers to have a fair share of the system resources and prevent them from exhausting the host resources.

POSIX ACLs and file system permissions are not mechanisms used by LXC and Docker to create containers. They are methods of controlling the access to files and directories on a file system, which can be applied to any process, not just containers.

Full virtualization allows unmodified guest operating systems to run in virtual machines, making statement B correct. The hypervisor presents a complete hardware abstraction to the guest OS.

Historically and conceptually, full virtualization relies on CPU emulation or hardware-assisted virtualization , making statement C correct. Even with hardware extensions, some degree of emulation is involved.

Full virtualization also requires additional system resources and processing time to emulate hardware and manage isolation, making statement E correct.

Statement A is incorrect because paravirtualization often offers better performance. Statement D is incorrect because emulated I/O devices generally perform worse than paravirtualized drivers.

Therefore, the correct answers are B, C, and E .

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.

In libvirt-based virtualization environments, the virsh change-media subcommand is used to change the media attached to removable devices such as CD-ROM drives . According to libvirt documentation, this command allows administrators to insert or eject ISO images from a running virtual machine without shutting it down.

This functionality is commonly used during operating system installations or software updates. The change-media command supports both live and persistent changes depending on the options used.

Therefore, the correct and documented answer is change-media .

QEMU can provide some network services in a user network, which is a mode of networking that does not require any administrator privilege to run.  The user network uses the SLIRP TCP/IP emulator to create a virtual NAT’ted subnet, with a DHCP server started by QEMU that gives out IP addresses to the guest machines and puts the host on 10.0.2.2 1 . QEMU can also provide a TFTP server in the user network, which can be used to boot the guest machines from a network image.  The TFTP server can be configured with the -tftp option 2 . QEMU does not provide BGP, CIFS, or AppleTalk services in the user network.  BGP is a routing protocol that is used to exchange routing information between autonomous systems on the Internet 3 .  CIFS is a file-sharing protocol that is used to access files and printers on a network 4 .  AppleTalk is a deprecated network protocol suite that was used by Apple devices 5 . These services require more advanced networking features than the user network can offer, such as bridging, routing, or tunneling.

Infrastructure as Code (IaC) is an approach where infrastructure is defined and managed using machine-readable configuration files . According to DevOps and cloud documentation, Puppet, Terraform, AWS CloudFormation, and Ansible all support IaC principles.

Terraform and AWS CloudFormation are declarative IaC tools used to provision cloud infrastructure. Puppet and Ansible are configuration management and automation tools that also enable infrastructure definition through code.

All listed tools are widely recognized in IaC workflows, making A, B, C, and D correct.

 cloud-init uses the /var/lib/cloud/ directory to store status information and configuration information retrieved from external sources, such as the cloud platform’s metadata service or user data files. The directory contains subdirectories for different types of data, such as instance, data, handlers, scripts, and sem. The instance subdirectory contains information specific to the current instance, such as the instance ID, the user data, and the cloud-init configuration. The data subdirectory contains information about the data sources that cloud-init detected and used. The handlers subdirectory contains information about the handlers that cloud-init executed. The scripts subdirectory contains scripts that cloud-init runs at different stages of the boot process, such as per-instance, per-boot, per-once, and vendor. The sem subdirectory contains semaphore files that cloud-init uses to track the execution status of different modules and stages.  References:

Configuring and managing cloud-init for RHEL 8 - Red Hat Customer Portal

vsphere - what is the linux file location where the cloud-init user …

The firmware attribute of the < os > element in a libvirt domain definition specifies the type of firmware used to boot the virtual machine. The valid values for this attribute are efi and bios, which correspond to the Extensible Firmware Interface (EFI) and the Basic Input/Output System (BIOS) respectively. EFI is a newer standard that supports more features and security than BIOS, such as Secure Boot and faster boot times. BIOS is an older standard that is widely compatible and supported by most hypervisors and operating systems.  The other values, scsi, virtio, and pcie, are not related to firmware, but to different types of devices or drivers that can be used in a virtual machine.  References :  1  (search for firmware enum)

The CPU flag that indicates the hardware virtualization capability on an AMD CPU is SVM. SVM stands for Secure Virtual Machine, and it is a feature of AMD processors that enables the CPU to run virtual machines with hardware assistance. SVM is also known as AMD-V, which is AMD’s brand name for its virtualization technology. SVM allows the CPU to support a hypervisor, which is a software layer that creates and manages virtual machines. A hypervisor can run multiple virtual machines on a single physical machine, each with its own operating system and applications. SVM improves the performance and security of virtual machines by allowing the CPU to directly execute privileged instructions and handle memory access, instead of relying on software emulation or binary translation. SVM also provides nested virtualization, which is the ability to run a virtual machine inside another virtual machine. To use SVM, the CPU must support it and the BIOS must enable it. The user can check if the CPU supports SVM by looking for the svm flag in the /proc/cpuinfo file or by using the lscpu command.  The user can also use the virt-host-validate command to verify if the CPU and the BIOS are properly configured for hardware virtualization 1 2 3 .  References :

How to check if CPU supports hardware virtualization (VT technology) 1

Processor support - KVM 3

How to Enable Virtualization in BIOS for Intel and AMD 4

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.

Virtualization provides several well-documented benefits in modern IT environments. One major advantage is improved hardware utilization (A), as multiple virtual machines can run on a single physical system, maximizing resource usage. Virtualization also enhances security (C) through isolation between workloads, limiting the impact of failures or security breaches.

Another key benefit is simplified backup and recovery (D). Virtual machines are encapsulated into files, making it easier to snapshot, back up, clone, and restore entire systems. This significantly improves disaster recovery and testing workflows.

Option B is not universally true. While virtualization can help standardize environments, it does not inherently reduce software compatibility issues; in some cases, it may even introduce additional layers of complexity.

Virtualization documentation consistently highlights hardware efficiency, security isolation, and operational flexibility as core benefits, making A, C, and D the correct answers.

The xl toolstack is the modern command-line management interface used for administering the Xen hypervisor , replacing the older xm toolstack. According to official Xen virtualization documentation, the global configuration file for the xl toolstack is /etc/xen/xl.conf .

This configuration file defines default behaviors and policies for the xl management commands. It allows administrators to configure global settings such as default CPU scheduling behavior, memory handling, device model settings, and other operational parameters that affect how virtual machines (domains) are managed on a Xen host. These settings apply system-wide and influence the behavior of all xl commands unless overridden by per-domain configuration files.

The file /etc/xen/xl.conf is read by the xl toolstack at runtime and is part of the standard Xen configuration directory structure. Individual virtual machine definitions are typically stored as separate configuration files in /etc/xen/, but xl.conf serves as the central, global configuration reference .

Virtualization notes emphasize that proper configuration of xl.conf is important for performance tuning, stability, and compliance in Xen-based environments. While many default installations function correctly without modifying this file, enterprise deployments often customize it to align with workload requirements and hardware capabilities.

Therefore, the correct and documented global configuration file for the xl toolstack is /etc/xen/xl.conf .

VirtualBox is a hosted hypervisor, which means it runs as an application on top of an existing operating system, not as a special kernel that is booted before the first regular operating system starts 1 .  VirtualBox supports a large number of guest operating systems, including Windows, Linux, Solaris, OS/2, and OpenBSD 1 .  VirtualBox does not require dedicated shared storage, as it can store virtual machine disk images locally on block devices of the virtualization host, or on network shares, or on iSCSI targets 1 .  VirtualBox provides both a graphical user interface (GUI) and command line tools (VBoxManage) to administer virtual machines 1 .  VirtualBox is available for Windows, Linux, macOS, and Solaris hosts 1 , and does not require the source code of the currently running Linux kernel to be available.  References :

Oracle VM VirtualBox: Features Overview

Container orchestration platforms are responsible for deploying, scaling, networking, and managing containerized applications across multiple hosts. According to containerization documentation, Docker Swarm and Kubernetes are recognized container orchestration platforms.

Docker Swarm is Docker’s native orchestration solution, providing clustering, service discovery, load balancing, and rolling updates. Kubernetes is the industry-standard orchestration platform, offering advanced scheduling, self-healing, horizontal scaling, and declarative configuration.

Docker Compose is not considered a full orchestration platform; it is primarily designed for defining and running multi-container applications on a single host , mainly for development and testing. LXC is a container runtime and system container technology, not an orchestration framework.

Container documentation clearly distinguishes orchestration platforms from runtimes and local development tools. Therefore, the correct answers are B and D .

The FROM statement in a Dockerfile specifies the base image from which the subsequent instructions are executed 1 .  The value of the FROM statement can be either an image name, an image name with a tag, or an image ID 1 .  The image name can be either a repository name or a repository name with a registry prefix 2 .  For example, ubuntu is a repository name, and docker.io/ubuntu is a repository name with a registry prefix 2 .  The tag is an optional identifier that can be used to specify a particular version or variant of an image 1 .  For example, ubuntu:focal refers to the image with the focal tag in the ubuntu repository 2 .  The image ID is a unique identifier that is automatically generated when an image is built or pulled 1 .  For example, sha256:9b0dafaadb1cd1d14e4db51bd0f4c0d56b6b551b2982b2b7c637ca143ad605d2 is an image ID 3 .

Therefore, the only valid value in the FROM statement among the given options is ubuntu:focal, which is an image name with a tag. The other options are invalid because:

docker://ubuntu:focal is not a valid image name format.  The docker:// prefix is used to specify a transport protocol, not a registry prefix 4 .

registry:ubuntu:focal is not a valid image name format.  The registry prefix should be a valid hostname or IP address, not a generic term 2 .

file:/tmp/ubuntu/Dockerfile is not a valid image name format.  The file: prefix is used to specify a local file path, not an image name 5 .

http://docker.example.com/images/ubuntu-focal.iso is not a valid image name format.  The http:// prefix is used to specify a web URL, not an image name 5 .

 A Pod in Kubernetes is a collection of one or more containers that share the same network and storage resources, and a specification for how to run the containers. A Pod is the smallest unit of workload Kubernetes can run, meaning that it cannot be divided into smaller units. Therefore, option C is correct. All containers of a Pod run on the same node, which is the smallest unit of computing hardware in Kubernetes. A node is a physical or virtual machine that hosts one or more Pods. Therefore, option A is also correct. Pods are not always created automatically and cannot be explicitly configured. Pods can be created manually using YAML or JSON files, or using commands like kubectl run or kubectl create. Pods can also be created automatically by higher-level controllers, such as Deployment, ReplicaSet, or StatefulSet. Therefore, option B is incorrect. When a Pod fails, Kubernetes does not restart the Pod on another node by default. Pods are ephemeral by nature, meaning that they can be terminated or deleted at any time. If a Pod is managed by a controller, the controller will create a new Pod to replace the failed one, but it may not be on the same node. Therefore, option D is incorrect. systemd is not used to manage individual Pods on the Kubernetes nodes. systemd is a system and service manager for Linux operating systems that can start and stop services, such as docker or kubelet. However, systemd does not interact with Pods directly. Pods are managed by the kubelet service, which is an agent that runs on each node and communicates with the Kubernetes control plane. Therefore, option E is incorrect.  References :

Pods | Kubernetes

What is a Kubernetes pod? - Red Hat

What’s the difference between a pod, a cluster, and a container?

What are Kubernetes Pods? | VMware Glossary

Kubernetes Node Vs. Pod Vs. Cluster: Key Differences - CloudZero

Packer is an image automation tool whose primary benefit is ensuring consistency across environments. According to virtualization and DevOps documentation, Packer allows administrators to create identical machine images for development, testing, and production from a single configuration.

By using the same base image and build process, Packer eliminates configuration drift and ensures that environments behave consistently. This significantly reduces deployment issues caused by environmental differences and supports Infrastructure as Code best practices.

Packer does not monitor virtual machines or directly speed up application development. While it can indirectly simplify deployments, its main advantage is image consistency and repeatability.

Therefore, the correct answer is B.

The command virsh pool-create-as vms dir --target /vms creates and starts a transient storage pool named vms of type dir with the target directory /vms 1 2 . This command resolves the issue of the storage pool not found error, as it makes the existing directory /vms visible to libvirt as a storage pool. The other commands are invalid because:

dd if=/dev/zero of=/vms bs=1 count=0 flags=name:vms is not a valid command syntax.  The dd command does not take a flags argument, and the output file /vms should be a regular file, not a directory 3 .

libvirt-poolctl new --name=/vms --type=dir --path=/vms is not a valid command name.  There is no such command as libvirt-poolctl in the libvirt package 4 .

qemu-img pool vms:/vms is not a valid command syntax.  The qemu-img command does not have a pool subcommand, and the vms:/vms argument is not a valid image specification 5 .

touch /vms/.libvirtpool is not a valid command to create a storage pool.  The touch command only creates an empty file, and the .libvirtpool file is not recognized by libvirt as a storage pool configuration file 6 .

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/procs 1 . 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 threads 2 .  References :

Creating and organizing cgroups · cgroup2 - GitHub Pages

Control Groups — The Linux Kernel documentation

Cloud-init is an initialization and configuration system designed primarily for Linux-based cloud instances . According to official cloud-init documentation, it is supported on a wide range of Linux distributions, including Ubuntu, Red Hat Enterprise Linux, CentOS, Debian, and SUSE.

Windows systems use a separate project called Cloudbase-Init , which is not cloud-init itself. macOS and Android do not support cloud-init.

Therefore, the correct answer is C (Linux) .

 Nested page table extensions, such as Intel Extended Page Table (EPT) or AMD Rapid Virtualization Indexing (RVI), are hardware features that facilitate the virtualization of  memory . They allow the CPU to perform the translation of guest virtual addresses to host physical addresses in a single step, without the need for software-managed shadow page tables. This reduces the overhead and complexity of memory management for virtual machines, and improves their performance and isolation. Nested page table extensions do not directly affect the virtualization of other hardware components, such as network interfaces, host bus adapters, hard disks, or IO cache.