
Lpi 305-300 Exam Dumps [2026] Practice Valid Exam Dumps Question
305-300 Dumps - Grab Out For [NEW-2026] Lpi Exam
NEW QUESTION # 63
Which of the following statements are true about container-based virtualization? (Choose two.)
- A. Each container runs its own operating system kernel.
- B. Linux does not support container-based virtualization because of missing kernel APIs.
- C. Container-based virtualization relies on hardware support from the host system's CPU.
- D. Different containers may use different distributions of the same operating system.
- E. All containers run within the operating system kernel of the host system.
Answer: D,E
Explanation:
Container-based virtualization is a method of operating system-level virtualization that allows multiple isolated user spaces (containers) to run on the same host system1. Each container shares the same operating system kernel as the host, but has its own file system, libraries, and processes2. Therefore, the statements A and C are false, as containers do not run their own kernels or rely on hardware support from the CPU. The statement E is also false, as Linux does support container-based virtualization through various technologies, such as cgroups, namespaces, LXC, Docker, etc12. The statement B is true, as different containers may use different distributions of the same operating system, such as Debian, Ubuntu, Fedora, etc., as long as they are compatible with the host kernel3. The statement D is also true, as all containers run within the operating system kernel of the host system, which provides isolation and resource management for them12. References:
* 1: Containerization (computing) - Wikipedia.
* 2: What are containers? | Google Cloud.
* 3: What is Container-Based Virtualization? - StackHowTo.
NEW QUESTION # 64
Which of the following statements in aDockerfileleads to a container which outputs hello world? (Choose two.)
- A. ENTRYPOINT "echo", "Hello", "World*
- B. ENTRYPOINT echo Hello World
- C. ENTRYPOINT [ "echo", "hello", "world" ]
- D. ENTRYPOINT [ "echo hello world" ]
- E. ENTRYPOINT "echo Hello World"
Answer: C,D
Explanation:
Explanation
The ENTRYPOINT instruction in a Dockerfile specifies the default command to run when a container is started from the image. The ENTRYPOINT instruction can be written in two forms: exec form and shell form.
The exec form uses a JSON array to specify the command and its arguments, such as [ "executable",
"param1", "param2" ]. The shell form uses a single string to specify the command and its arguments, such as
"executable param1 param2". The shell form is converted to the exec form by adding /bin/sh -c to the beginning of the command. Therefore, the following statements in a Dockerfile are equivalent and will lead to a container that outputs hello world:
ENTRYPOINT [ "echo hello world" ] ENTRYPOINT [ "/bin/sh", "-c", "echo hello world" ] ENTRYPOINT
"echo hello world" ENTRYPOINT [ "echo", "hello", "world" ] ENTRYPOINT [ "/bin/sh", "-c", "echo",
"hello", "world" ] ENTRYPOINT "echo hello world"
The other statements in the question are invalid or incorrect. The statement A. ENTRYPOINT "echo Hello World" is invalid because it uses double quotes to enclose the entire command, which is not allowed in the shell form. The statement D. ENTRYPOINT echo Hello World is incorrect because it does not use quotes to enclose the command, which is required in the shell form. The statement E. ENTRYPOINT "echo", "Hello",
"World" is invalid because it uses double quotes to separate the command and its arguments, which is not allowed in the exec form. References:
* Dockerfile reference | Docker Docs
* Using the Dockerfile ENTRYPOINT and CMD Instructions - ATA Learning
* Difference Between run, cmd and entrypoint in a Dockerfile
NEW QUESTION # 65
FILL BLANK
What LXC command lists containers sorted by their CPU, block I/O or memory consumption? (Specify ONLY the command without any path or parameters.)
Answer:
Explanation:
lxc-top
Explanation
LXD supports the following network interface types for containers: macvlan, bridged, physical, sriov, and ovn1. Macvlan creates a virtual interface on the host that is connected to the same network as the parent interface2. Bridged connects the container to a network bridge that acts as a virtual switch3. Physical attaches the container to a physical network interface on the host2. Ipsec and wifi are not valid network interface types for LXD containers. References:
* 1: Bridge network - Canonical LXD documentation
* 2: How to create a network - Canonical LXD documentation
* 4: LXD containers and networking with static IP - Super User
NEW QUESTION # 66
Which of the following kinds of data cancloud-initprocess directly from user-data? (Choose three.)
- A. Base64-encoded binary files to execute
- B. cloud-config declarations in YAML
- C. Lists of URLs to import
- D. Shell scripts to execute
- E. ISO images to boot from
Answer: B,C,D
Explanation:
Explanation
Cloud-init is a tool that allows users to customize the configuration and behavior of cloud instances during the boot process. Cloud-init can process different kinds of data that are passed to the instance via user-data, which is a mechanism provided by various cloud providers to inject data into the instance. Among the kinds of data that cloud-init can process directly from user-data are:
* Shell scripts to execute: Cloud-init can execute user-data that is formatted as a shell script, starting with the #!/bin/sh or #!/bin/bash shebang. The script can contain any commands that are valid in the shell environment of the instance. The script is executed as the root user during the boot process12.
* Lists of URLs to import: Cloud-init can import user-data that is formatted as a list of URLs, separated by newlines. The URLs can point to any valid data source that cloud-init supports, such as shell scripts, cloud-config files, or include files. The URLs are fetched and processed by cloud-init in the order they appear in the list13.
* cloud-config declarations in YAML: Cloud-init can process user-data that is formatted as a cloud-config file, which is a YAML document that contains declarations for various cloud-init modules. The cloud-config file can specify various aspects of the instance configuration, such as hostname, users, packages, commands, services, and more. The cloud-config file must start with the #cloud-config header14.
The other kinds of data listed in the question are not directly processed by cloud-init from user-data. They are either not supported, not recommended, or require additional steps to be processed. These kinds of data are:
* ISO images to boot from: Cloud-init does not support booting from ISO images that are passed as user-data. ISO images are typically used to install an operating system on a physical or virtual machine, not to customize an existing cloud instance. To boot from an ISO image, the user would need to attach it as a secondary disk to the instance and configure the boot order accordingly5.
* Base64-encoded binary files to execute: Cloud-init does not recommend passing binary files as user-data, as they may not be compatible with the instance's architecture or operating system.
Base64-encoding does not change this fact, as it only converts the binary data into ASCII characters. To execute a binary file, the user would need to decode it and make it executable on the instance6.
References:
* User-Data Formats - cloud-init 22.1 documentation
* User-Data Scripts
* Include File
* Cloud Config
* How to Boot From ISO Image File Directly in Windows
* How to run a binary file as a command in the terminal?.
NEW QUESTION # 67
Which of the following types of guest systems does Xen support? (Choose two.)
- A. Fully virtualized guests
- B. Foreign architecture guests (FA)
- C. Emulated guests
- D. Paravirtualized quests (PVI
- E. Container virtualized guests
Answer: A,D
NEW QUESTION # 68
What are the key benefits of using cloud management tools?
- A. Enhanced security through encryption
- B. Streamlined billing and invoicing
- C. Automated scaling of virtual machines
- D. Efficient resource allocation
Answer: D
Explanation:
Cloud management tools are primarily designed tooptimize and control cloud-based resourcesin virtualized and containerized environments. According to virtualization and containerization documentation, one of the most significant benefits of these tools isefficient resource allocation. Cloud management platforms enable administrators to dynamically assign compute, storage, and network resources based on workload demand, ensuring optimal utilization of infrastructure.
These tools continuously monitor resource consumption across virtual machines and containers, helping prevent underutilization and resource contention. By leveraging centralized dashboards, policy-based management, and automation, cloud management tools ensure that workloads receive appropriate resources while minimizing waste. This capability is especially critical in private, public, and hybrid cloud environments where scalability and cost control are essential.
While features such as automated scaling, billing integration, and security enhancements may be supported by specific cloud platforms, they aresecondary capabilitiesrather than the core function. Encryption, for example, is typically handled by underlying security services rather than cloud management tools themselves.
Similarly, billing and invoicing are more closely associated with cloud service provider platforms.
Virtualization notes consistently emphasize thatefficient resource allocationis the foundational benefit that enables performance optimization, cost efficiency, and scalability in cloud-managed environments.
NEW QUESTION # 69
Which file in acgroupdirectory contains the list of processes belonging to thiscgroup?
- A. members
- B. casks
- C. procs
- D. pids
- E. subjects
Answer: C
NEW QUESTION # 70
Which of the following values are valid in the type attribute of a<domain>element in a libvirt domain definition? (Choose two.)
- A. kvm
- B. cgroup
- C. Ixc
- D. namespace
- E. proc
Answer: A,C
NEW QUESTION # 71
A clone of a previously used virtual machine should be created. All VM specific information, such as user accounts, shell histories and SSH host keys should be removed from the cloned disk image. Which of the following tools can perform these tasks?
- A. virt-sparsi
- B. sysprep
- C. virt-svspre
- D. virc-reset
- E. vire-wipe
- F. virt-rescue
Answer: C
NEW QUESTION # 72
What is Packer?
- A. An image building tool
- B. A virtualization platform
- C. A container orchestration tool
- D. A configuration management tool
Answer: A
Explanation:
Packer is animage automation and building tooldeveloped by HashiCorp. According to virtualization and DevOps documentation, Packer is used to createmachine imagesfor multiple platforms from a single configuration file.
Packer is not an orchestration platform, configuration management tool, or hypervisor. Its primary role is to ensureconsistent, repeatable, and automated image creation, makingBthe correct answer.
NEW QUESTION # 73
What is libvirt?
- A. A virtualization technology
- B. A virtualization management API.
- C. A Linux distribution
- D. A hardware virtualization platform
Answer: B
Explanation:
Libvirt is avirtualization management API, toolkit, and set of command-line utilitiesdesigned to manage virtualization platforms in a consistent and secure manner. According to official virtualization and containerization documentation, libvirt provides acommon interfacefor interacting with multiple hypervisors such asKVM, QEMU, Xen, VMware ESXi, and Hyper-V, abstracting their underlying differences.
Libvirt itself isnot a virtualization technology or hypervisor; rather, it acts as amanagement layerbetween administrators or orchestration tools and the hypervisor. It enables tasks such as creating, starting, stopping, pausing, migrating, and monitoring virtual machines. Tools likevirshandvirt-managerrely on libvirt to perform virtualization operations.
One of libvirt's key strengths is its focus onsecurity and isolation. It integrates with Linux security frameworks such asSELinux and AppArmor, enforcing mandatory access controls on virtual machines.
Libvirt also supportsremote managementusing secure protocols, making it suitable for enterprise and cloud environments.
In virtualization documentation, libvirt is described as a foundational component forInfrastructure as Code and automation, commonly used with tools likeAnsible, OpenStack, and Kubernetes (via KVM). Its standardized API simplifies virtualization management while ensuring portability, scalability, and compliance with best practices.
NEW QUESTION # 74
Which of the following commands executes a command in a running LXC container?
- A. lxc-batch
- B. lxc-accach
- C. lxc-eval
- D. lxc-enter
- E. lxc-run
Answer: B
Explanation:
The command lxc-attach is used to execute a command in a running LXC container. It allows the user to start a process inside the container and attach to its standard input, output, and error streams1. For example, the command lxc-attach -n mycontainer -- ls -lh /home will list all the files and directories in the /home directory of the container named mycontainer1. The other options are not valid LXC commands. The command lxc- batch does not exist. The command lxc-run is an alias for lxc-start, which is used to start a container, not to execute a command in it2. The command lxc-enter is also an alias for lxc-attach, but it is deprecated and should not be used3. The command lxc-eval is also not a valid LXC command. References:
* 1: Executing a command inside a running LXC - Unix & Linux Stack Exchange.
* 2: lxc-start: start a container. - SysTutorials.
* 3: lxc-attach: start a process inside a running container. - SysTutorials.
NEW QUESTION # 75
Which of the following statements are true about container-based virtualization? (Choose two.)
- A. Each container runs its own operating system kernel.
- B. Linux does not support container-based virtualization because of missing kernel APIs.
- C. Container-based virtualization relies on hardware support from the host system's CPU.
- D. Different containers may use different distributions of the same operating system.
- E. All containers run within the operating system kernel of the host system.
Answer: D,E
Explanation:
Explanation
Container-based virtualization is a method of operating system-level virtualization that allows multiple isolated user spaces (containers) to run on the same host system1. Each container shares the same operating system kernel as the host, but has its own file system, libraries, and processes2. Therefore, the statements A and C are false, as containers do not run their own kernels or rely on hardware support from the CPU. The statement E is also false, as Linux does support container-based virtualization through various technologies, such as cgroups, namespaces, LXC, Docker, etc12. The statement B is true, as different containers may use different distributions of the same operating system, such as Debian, Ubuntu, Fedora, etc., as long as they are compatible with the host kernel3. The statement D is also true, as all containers run within the operating system kernel of the host system, which provides isolation and resource management for them12. References:
* 1: Containerization (computing) - Wikipedia.
* 2: What are containers? | Google Cloud.
* 3: What is Container-Based Virtualization? - StackHowTo.
NEW QUESTION # 76
If aDockerfilecontains the following lines:
WORKDIR /
RUN cd /tmp
RUN echo test > test
where is the filetestlocated?
- A. /root/tesc within the container image.
- B. /test within the container image.
- C. /tmp/test on the system running docker build.
- D. /ting/test within the container image.
- E. test in the directory holding the Dockerf ile.
Answer: B
Explanation:
The WORKDIR instruction sets the working directory for any subsequent RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile1. The RUN instruction executes commands in a new layer on top of the current image and commits the results2. 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 environment3. 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
NEW QUESTION # 77
What does IaaS stand for?
- A. Intelligence as a Service
- B. Integration as a Service
- C. Infrastructure as a Service
- D. Instances as a Service
- E. Information as a Service
Answer: C
NEW QUESTION # 78
Which of the following commands moves the libvirt domainweb1from the current host system to the host systemhost2?
- A. virsh pool-add host2 web1
- B. virsh migrate web1 qemu+ssh://host2/system
- C. virsh cp .:web1 host2:web1
- D. virsh node-update host1=-dom:web1 host2=+dom:web1
- E. virsh patch web1 .Domain.Node=host2
Answer: B
NEW QUESTION # 79
Which of the following types of guest systems does Xen support? (Choose two.)
- A. Fully virtualized guests
- B. Foreign architecture guests (FA)
- C. Emulated guests
- D. Paravirtualized quests (PVI
- E. Container virtualized guests
Answer: A,D
Explanation:
Xen supports two types of guest systems: paravirtualized guests (PV) and fully virtualized guests (HVM).
* Paravirtualized guests (PV) are guests that have been modified to run on the Xen hypervisor. They use a special kernel that communicates with the hypervisor through hypercalls, and use paravirtualized drivers for I/O devices. PV guests can run faster and more efficiently than HVM guests, but they require the guest operating system to be ported to Xen and to support the Xen ABI12.
* Fully virtualized guests (HVM) are guests that run unmodified operating systems on the Xen hypervisor. They use hardware virtualization extensions, such as Intel VT-x or AMD-V, to create a virtual platform for the guest. HVM guests can run any operating system that supports the hardware architecture, but they incur more overhead and performance penalties than PV guests. HVM guests can also use paravirtualized drivers for I/O devices to improve their performance12.
The other options are not correct. Xen does not support foreign architecture guests (FA), emulated guests, or container virtualized guests.
* Foreign architecture guests (FA) are guests that run on a different hardware architecture than the host.
For example, running an ARM guest on an x86 host. Xen does not support this type of virtualization, as it would require emulation or binary translation, which are very complex and slow techniques3.
* Emulated guests are guests that run on a software emulator that mimics the hardware of the host or another platform. For example, running a Windows guest on a QEMU emulator. Xen does not support this type of virtualization, as it relies on the emulator to provide the virtual platform, not the hypervisor. Xen can use QEMU to emulate some devices for HVM guests, but not the entire platform14.
* Container virtualized guests are guests that run on a shared kernel with the host and other guests, using namespaces and cgroups to isolate them. For example, running a Linux guest on a Docker container. Xen does not support this type of virtualization, as it requires the guest operating system to be compatible with the host kernel, and does not provide the same level of isolation and security as hypervisor-based virtualization56.
:
Xen Project Software Overview - Xen
Xen ARM with Virtualization Extensions - Xen
Xen Project Beginners Guide - Xen
QEMU - Xen
Docker overview | Docker Documentation
What is a Container? | App Containerization | VMware
NEW QUESTION # 80
What is the purpose ofcloud-init?
- A. Orchestrate the creation and start of multiple related laaS instances.
- B. Replace common Linux inic systems, such as systemd or SysV init.
- C. Prepare the generic image of an laaS instance to fit a specific instance's configuration.
- D. Standardize the configuration of infrastructure services, such as load balancers or virtual firewalls in a cloud.
- E. Assign an laaS instance to a specific computing node within a cloud.
Answer: C
Explanation:
Explanation
Cloud-init is a tool that processes configurations and runs through five stages during the initial boot of Linux VMs in a cloud. It allows users to customize a Linux VM as it boots for the first time, by applying user data to the instance. User data can include scripts, commands, packages, files, users, groups, SSH keys, and more.
Cloud-init can also interact with various cloud platforms and services, such as Azure, AWS, OpenStack, and others. The purpose of cloud-init is to prepare the generic image of an laaS instance to fit a specific instance's configuration, such as hostname, network, security, and application settings. References:
* Cloud-init - The standard for customising cloud instances
* Understanding cloud-init - Azure Virtual Machines
* Tutorial - Customize a Linux VM with cloud-init in Azure - Azure Virtual Machines
NEW QUESTION # 81
What is oVirt?
- A. An approach used to eliminate the need for virtualization called Zero-Virt
- B. A comprehensive management infrastructure for Linux-based virtualization
- C. A Linux-based hypervisor similar to KVM and Xen
- D. An extension to the Linux Kernel used to provide container virtualization similar to LXC and OpenVZ
- E. A library that provides access to several different virtualization technologies in a common manner
Answer: B
Explanation:
oVirt is anopen-source virtualization management platformthat provides a comprehensive infrastructure for managingLinux-based virtualization environments. According to official oVirt and Red Hat documentation, oVirt acts as amanagement layer on top of KVM, offering centralized control over hosts, virtual machines, storage, and networking.
oVirt itself isnot a hypervisor; instead, it relies onKVMas the underlying virtualization technology. It provides both aweb-based management interfaceand REST APIs, enabling administrators to manage large- scale virtualization deployments efficiently. Features include VM lifecycle management, live migration, high availability, storage domain management, and integration with directory services.
Option E describeslibvirt, not oVirt. Options A, C, and D do not match oVirt's documented purpose.
Therefore, the correct answer isB.
NEW QUESTION # 82
Ifdocker stackis to be used to run a Docker Compose file on a Docker Swarm, how are the images referenced in the Docker Compose configuration made available on the Swarm nodes?
- A. docker stack instructs the Swarm nodes to pull the images from a registry, although it does not upload the images to the registry.
- B. docker stack transfers the image from its local Docker cache to each Swarm node.
- C. docker stack builds the images locally and copies them to only those Swarm nodes which run the service.
- D. docker stack passes the images to the Swarm master which distributes the images to all other Swarm nodes.
- E. docker stack triggers the build process for the images on all nodes of the Swarm.
Answer: A
NEW QUESTION # 83
Which of the following are true regarding the CPU of a QEMU virtual machine? (Choose two.)
- A. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
- B. Each QEMU virtual machine can only have one CPU with one core.
- C. QEMU uses the concept of virtual CPUs to map the virtual machines to physical CPUs.
- D. For each QEMU virtual machine, one dedicated physical CPU core must be reserved.
- E. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.
Answer: A,E
Explanation:
The CPU architecture of a QEMU virtual machine is independent of the host system's architecture. QEMU can emulate many CPU architectures, including x86, ARM, Alpha, and SPARC, regardless of the host system' s architecture1. This allows QEMU to run guest operating systems that are not compatible with the host system's hardware. Therefore, option A is correct. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems. QEMU uses the concept of virtual CPUs (vCPUs) to map the virtual machines to physical CPUs. Each vCPU is a thread that runs on a physical CPU core. QEMU allows the user to specify the number of vCPUs and the CPU model for each virtual machine. QEMU can run SMP systems with multiple vCPUs, as well as single-processor systems with one vCPU2. Therefore, option E is also correct. The other options are incorrect because they do not describe the CPU of a QEMU virtual machine. Option B is wrong because QEMU virtual machines can have more than one CPU with more than one core. Option C is wrong because QEMU does not require a dedicated physical CPU core for each virtual machine. QEMU can share the physical CPU cores among multiple virtual machines, depending on the load and the scheduling policy. Option D is wrong because QEMU does not use the term CPU, but vCPU, to refer to the virtual machines' processors. References:
* QEMU vs VirtualBox: What's the difference? - LinuxConfig.org
* QEMU / KVM CPU model configuration - QEMU documentation
* Introduction - QEMU documentation
* Qemu/KVM Virtual Machines - Proxmox Virtual Environment
NEW QUESTION # 84
What is the purpose of a .dockerignore file?
- A. It specifies files that Docker does not submit to the Docker daemon when building a Docker image
- B. It exists in the root file system of containers that should ignore volumes and ports provided by Docker.
- C. It lists files existing in a Docker image which should be excluded when building a derivative image.
- D. It must be placed in the top level directory of volumes that Docker should never attach automatically to a container
- E. It specifies which parts of a Dockerfile should be ignored when building a Docker image.
Answer: A
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.
References:
* What are .dockerignore files, and why you should use them?
* Dockerfile reference | Docker Docs
* How to use .dockerignore and its importance - Shisho Cloud
NEW QUESTION # 85
After setting up a data container using the following command:
docker create -v /data --name datastore debian /bin/true
how is an additional new container started which shares the/datavolume with the datastore container?
- A. docker run --share-with datastore --name service debian bash
- B. docker run -v /data --name service debian bash
- C. docker run --volumes-from datastore --name service debian bash
- D. docker run --volume-backend datastore -v /data --name service debian bash
- E. docker run -v datastore:/data --name service debian bash
Answer: C
Explanation:
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
NEW QUESTION # 86
......
305-300 Exam Dumps PDF Guaranteed Success with Accurate & Updated Questions: https://freetorrent.dumpstests.com/305-300-latest-test-dumps.html