305-300 Exam Questions Get Updated [2026] with Correct Answers [Q49-Q65]

Share

305-300 Exam Questions Get Updated [2026] with Correct Answers

Practice 305-300 Questions With Certification guide Q&A from Training Expert Dumps4PDF


The LPIC-3 Exam 305 covers a range of topics related to virtualization and containerization, including the use of virtualization technologies such as KVM, Xen, and VMware; containerization tools such as Docker and LXC; and cloud computing technologies such as OpenStack and AWS. 305-300 exam also covers topics such as network virtualization, storage virtualization, and security in virtualized environments.

 

NEW QUESTION # 49
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 # 50
Which of the following values would be valid in the FROM statement in aDockerfile?

  • A. file:/tmp/ubuntu/Dockerfile
  • B. ubuntu:focal
  • C. docker://ubuntu: focal
  • D. http://docker.example.com/images/ubuntu-focal.iso
  • E. registry:ubuntu:focal

Answer: B

Explanation:
Explanation
The FROM statement in a Dockerfile specifies the base image from which the subsequent instructions are executed1. The value of the FROM statement can be either an image name, an image name with a tag, or an image ID1. The image name can be either a repository name or a repository name with a registry prefix2. For example, ubuntu is a repository name, and docker.io/ubuntu is a repository name with a registry prefix2. The tag is an optional identifier that can be used to specify a particular version or variant of an image1. For example, ubuntu:focal refers to the image with the focal tag in the ubuntu repository2. The image ID is a unique identifier that is automatically generated when an image is built or pulled1. For example, sha256:9b0dafaadb1cd1d14e4db51bd0f4c0d56b6b551b2982b2b7c637ca143ad605d2 is an image ID3.
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 prefix4.
* registry:ubuntu:focal is not a valid image name format. The registry prefix should be a valid hostname or IP address, not a generic term2.
* 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 name5.
* 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.
References:
* 1: Dockerfile reference | Docker Docs
* 2: docker - Using FROM statement in dockerfile - Stack Overflow
* 3: How to get the image id from a docker image - Stack Overflow
* 4: skopeo - Docker Registry v2 API tool - Linux Man Pages (1)
* 5: How to build a Docker image from a local Dockerfile? - Stack Overflow


NEW QUESTION # 51
Which of the following statements are true regarding resource management for full virtualization? (Choose two.)

  • A. Full virtualization cannot pose any limits to virtual machines and always assigns the host system's resources in a first-come-first-serve manner.
  • B. It is up to the virtual machine to use its assigned hardware resources and create, for example, an arbitrary amount of network sockets.
  • C. The hypervisor provides each virtual machine with hardware of a defined capacity that limits the resources of the virtual machine.
  • D. The hygervisor may provide fine-grained limits to internal elements of the guest operating system such as the number of processes.
  • E. All processes created within the virtual machines are transparently and equally scheduled in the host system for CPU and I/O usage.

Answer: B,C


NEW QUESTION # 52
Which of the following devices exist by default in an LXC container? (Choose three.)

  • A. /dev/urandom
  • B. /dev/root
  • C. /dev/console
  • D. /dev/log
  • E. /dev/kmem

Answer: A,C,D


NEW QUESTION # 53
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 --volume-backend datastore -v /data --name service debian bash
  • B. docker run --share-with datastore --name service debian bash
  • C. docker run --volumes-from datastore --name service debian bash
  • D. docker run -v /data --name service debian bash
  • E. docker run -v datastore:/data --name service debian bash

Answer: C

Explanation:
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 # 54
Which CPU flag indicates the hardware virtualization capability on an AMD CPU?

  • A. SVM
  • B. VMX
  • C. PVM
  • D. HVM
  • E. VIRT

Answer: A

Explanation:
Explanation
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 avirtual 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 virtualization123. References:
* How to check if CPU supports hardware virtualization (VT technology)1
* Processor support - KVM3
* How to Enable Virtualization in BIOS for Intel and AMD4


NEW QUESTION # 55
Which functionality is provided by Vagrant as well as by Docker? (Choose three.)

  • A. Both can apply changes to a base image.
  • B. Both start system images as containers instead of virtual machines by default.
  • C. Both can download required base images.
  • D. Both can share directories from the host file system to a guest.
  • E. Both start system images as virtual machines instead of containers bv default.

Answer: A,C,D

Explanation:
* Both Vagrant and Docker can share directories from the host file system to a guest. This allows the guest to access files and folders from the host without copying them. Vagrant uses the config.vm.synced_folder option in the Vagrantfile to specify the shared folders1. Docker uses the -v or --volume flag in the docker run command to mount a host directory as a data volume in the container2.
* Both Vagrant and Docker can download required base images. Base images are the starting point for creating a guest environment. Vagrant uses the config.vm.box option in the Vagrantfile to specify the base image to use1. Docker uses the FROM instruction in the Dockerfile to specify the base image to use2. Both Vagrant and Docker can download base images from public repositories or local sources.
* Both Vagrant and Docker can apply changes to a base image. Changes are modifications or additions to the base image that customize the guest environment. Vagrant uses provisioners to run scripts or commands on the guest after it is booted1. Docker uses instructions in the Dockerfile to execute commands on the baseimage and create a new image2. Both Vagrant and Docker can save the changes to a new image or discard them after the guest is destroyed.
* Vagrant and Docker differ in how they start system images. Vagrant starts system images as virtual machines by default, using a provider such as VirtualBox, VMware, or Hyper-V1. Docker starts system images as containers by default, using the native containerization functionality on macOS, Linux, and Windows2. Containers are generally more lightweight and faster than virtual machines, but less secure and flexible. References: 1: Vagrant vs. Docker | Vagrant | HashiCorp Developer 2: Vagrant vs Docker:
Which Is Right for You? (Could Be Both) - Kinsta Web Development Tools


NEW QUESTION # 56
Which of the following mechanisms are used by LXC and Docker to create containers? (Choose three.)

  • A. POSIXACLs
  • B. Linux Capabilities
  • C. Control Groups
  • D. Kernel Namespaces
  • E. File System Permissions

Answer: B,C,D

Explanation:
Explanation
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.
References:
* LXC vs Docker: Which Container Platform Is Right for You?
* LXC vs Docker: Why Docker is Better in 2023 | UpGuard
* What is the Difference Between LXC, LXD and Docker Containers
* lxc - Which container implementation docker is using - Unix & Linux Stack Exchange


NEW QUESTION # 57
Which of the following services can QEMU provide in a user network? (Choose three.)

  • A. TFTP
  • B. BGP
  • C. AppleTalk
  • D. DHCP
  • E. CIFS

Answer: A,D,E


NEW QUESTION # 58
Which of the following statements are true regarding a Pod in Kubernetes? (Choose two.)

  • A. Pods are always created automatically and cannot be explicitly configured.
  • B. systemd is used to manage individual Pods on the Kubernetes nodes.
  • C. When a Pod fails, Kubernetes restarts the Pod on another node by default.
  • D. All containers of a Pod run on the same node.
  • E. A Pod is the smallest unit of workload Kubernetes can run.

Answer: D,E

Explanation:
Explanation
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 Podsdirectly. 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


NEW QUESTION # 59
After creating a new Docker network using the following command:
docker network create --driver bridge isolated_nw
which parameter must be added todocker createin order to attach a container to the network?

  • A. --ethernet=isolated_nw
  • B. --alias=isolated_nw
  • C. --network=isolated_nw
  • D. --eth0=isolated_nw
  • E. --attach=isolated_nw

Answer: C


NEW QUESTION # 60
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. vire-wipe
  • B. virc-reset
  • C. virt-sparsi
  • D. virt-svspre
  • E. sysprep
  • F. virt-rescue

Answer: E

Explanation:
Sysprep is a tool that removes all your personal account and security information, and then prepares the machine to be used as an image. It is supported by Windows and some Linux distributions. It can also remove drivers and other machine-specific settings. Sysprep is required when creating a managed image outside of a gallery in Azure
https://learn.microsoft.com/en-us/azure/virtual-machines/generalize


NEW QUESTION # 61
What happens when the following command is executed twice in succession?
docker run -tid -v data:/data debian bash

  • A. The container resulting from the second invocation can only read the content of /data/ and cannot change it.
  • B. Each container is equipped with its own independent data volume, available at /data/ in the respective container.
  • C. The original content of the container image data is available in both containers, although changes stay local within each container.
  • D. The second command invocation fails with an error stating that the volume data is already associated with a running container.
  • E. Both containers share the contents of the data volume, have full permissions to alter its content and mutually see their respective changes.

Answer: E

Explanation:
The command docker run -tid -v data:/data debian bash creates and runs a new container from the debian image, with an interactive terminal and a detached mode, and mounts a named volume data at /data in the container12. If the volume data does not exist, it is created automatically3. If the command is executed twice in succession, two containers are created and run, each with its own terminal and process ID, but they share the same volume data. This means that both containers can access, modify, and see the contents of the data volume, and any changes made by one container are reflected in the other container. Therefore, the statement C is true and the correct answer. The statements A, B, D, and E are false and incorrect, as they do not describe the behavior of the command or the volume correctly. References:
* 1: docker run | Docker Docs.
* 2: Docker run reference | Docker Docs - Docker Documentation.
* 3: Use volumes | Docker Documentation.
* [4]: How to Use Docker Run Command with Examples - phoenixNAP.


NEW QUESTION # 62
The commandvirsh vol-list vmsreturns the following error:
error: failed to get pool 'vms'
error: Storage pool not found: no storage pool with matching name 'vms ' Given that the directory/vmsexists, which of the following commands resolves this issue?

  • A. touch /vms/.libvirtpool
  • B. virsh pool-create-as vms dir --target /vms
  • C. dd if=/dev/zero of=/vms bs=1 count=0 flags=name:vms
  • D. libvirt-poolctl new --name=/vms --type=dir --path=/vms
  • E. qemu-img pool vms:/vms

Answer: B

Explanation:
Explanation
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 /vms12. 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 directory3.
* 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 package4.
* 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 specification5.
* 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 file6.
References:
* 1: virsh - difference between pool-define-as and pool-create-as - Stack Overflow
* 2: dd(1) - Linux manual page - man7.org
* 3: 12.3.3. Creating a Directory-based Storage Pool with virsh - Red Hat Customer Portal
* 4: libvirt - Linux Man Pages (3)
* 5: qemu-img(1) - Linux manual page - man7.org
* 6: touch(1) - Linux manual page - man7.org


NEW QUESTION # 63
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 created based on an image file that contains the operating system as well as software and default configuration for a given purpose.
  • 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 to the installation media of a Linux distribution and provides access to the installer by logging in via SSH.
  • 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 connected via a VPN with the computer that started the provisioning and tries to PXE boot from that machine.

Answer: A

Explanation:
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 # 64
What is Xen's role in paravirtualization?

  • A. It fully virtualizes hardware
  • B. It only supports fully virtualized guests
  • C. Requires modified guest operating systems for improved performance
  • D. None of the above

Answer: C

Explanation:
Inparavirtualization, the guest operating system is aware that it is running in a virtualized environment and is modified to interact efficiently with the hypervisor. According to Xen documentation, Xen was originally designed as aparavirtualization-focused hypervisor, requiringmodified guest operating systemsto achieve better performance.
These modifications allow the guest OS to replace sensitive hardware instructions withhypercalls, reducing the overhead associated with hardware emulation. This results in improved CPU, memory, and I/O performance compared to early full virtualization techniques.
Xen does support fully virtualized (HVM) guests, but that is not its role in paravirtualization. Therefore, option Bcorrectly describes Xen's role.


NEW QUESTION # 65
......

Prepare Top Lpi 305-300 Exam Audio Study Guide Practice Questions Edition: https://www.dumps4pdf.com/305-300-valid-braindumps.html

Free Lpi 305-300 Test Practice Test Questions Exam Dumps: https://drive.google.com/open?id=16CkLiyUmu6HMOpQtwQh9n38L91iuyAEj