Get 305-300 Products Practice Material for 305-300 Exam Question Preparation
Most Reliable Lpi 305-300 Training Materials
Get to know about the certification Worth of the LPI 305-300 Exam
The LPI 305-300 exam is a very important one for anyone who wants to become a Cisco expert. The certification will help you with your career growth and also help you to get better job opportunities in the IT industry. LPI 305-300 exam dumps will help you prepare for this exam.
You may be wondering why it is so important for you to pass this exam? The answer is simple; passing this exam will give you access to many good jobs in the IT industry. You will be able to use this certification as proof of your expertise in networking and networking technologies.
The best part about this certification is that it can be used anywhere around the world, so it doesn't matter where you are from. All you need is an internet connection and an LPI certification ID card which you can get from our website or any other website that sells them online.
The LPIC-3 Exam 305: Virtualization and Containerization is an essential certification for IT professionals who want to demonstrate their expertise in virtualization and containerization technologies. 305-300 exam covers a wide range of topics and requires a significant amount of preparation, but passing it can open up many career opportunities in the IT industry.
NEW QUESTION # 37
FILL BLANK
Which subcommand ofvirshopens the XML configuration of a virtual network in an editor in order to make changes to that configuration? (Specify ONLY the subcommand without any parameters.)
Answer:
Explanation:
net-edit
Explanation
The subcommand of virsh that opens the XML configuration of a virtual network in an editor in order to make changes to that configuration is net-edit1. This subcommand takes the name or UUID of the network as a parameter and opens the network XML file in the default editor, which is specified by the $EDITOR shell variable1. The changes made to the network configuration are applied immediately after saving and exiting the editor1.
References:
* 1: net-edit - libvirt.
NEW QUESTION # 38
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-svspre
- B. vire-wipe
- C. virt-rescue
- D. virc-reset
- E. virt-sparsi
- F. sysprep
Answer: A
NEW QUESTION # 39
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 host system in order to use the visualization extensions of the host system's CPU
- 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 the first virtual machine as it interacts with the QEMU bare metal hypervisor and is required to trigger the start of additional virtual machines
- E. It must be loaded into the kernel of each virtual machine to provide Para virtualization which is required by QEMU.
Answer: B
NEW QUESTION # 40
Which of the following are true regarding the CPU of a QEMU virtual machine? (Choose two.)
- A. For each QEMU virtual machine, one dedicated physical CPU core must be reserved.
- B. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
- C. QEMU uses the concept of virtual CPUs to map the virtual machines to physical CPUs.
- D. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.
- E. Each QEMU virtual machine can only have one CPU with one core.
Answer: B,D
Explanation:
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 # 41
Which of the following are true regarding the CPU of a QEMU virtual machine? (Choose two.)
- A. For each QEMU virtual machine, one dedicated physical CPU core must be reserved.
- B. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
- C. QEMU uses the concept of virtual CPUs to map the virtual machines to physical CPUs.
- D. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.
- E. Each QEMU virtual machine can only have one CPU with one core.
Answer: B,D
NEW QUESTION # 42
Which file in acgroupdirectory contains the list of processes belonging to thiscgroup?
- A. subjects
- B. members
- C. casks
- D. procs
- E. pids
Answer: D
NEW QUESTION # 43
What kind of virtualization is implemented by LXC?
- A. Hardware containers
- B. Application containers
- C. Paravirtualization
- D. System containers
- E. CPU emulation
Answer: D
Explanation:
Explanation
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, andprocesses. 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
NEW QUESTION # 44
Which of the following types of guest systems does Xen support? (Choose two.)
- A. Foreign architecture guests (FA)
- B. Paravirtualized quests (PVI
- C. Fully virtualized guests
- D. Emulated guests
- E. Container virtualized guests
Answer: B,C
Explanation:
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.
References:
* 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 # 45
Which of the following values are valid in thefirmwareattribute of a<os>element in a libvirt domain definition?(Choose two.)
- A. efi
- B. scsi
- C. pcie
- D. virtio
- E. bios
Answer: A,E
Explanation:
Explanation
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)
NEW QUESTION # 46
Which of the following statements about the commandlxc-checkpointis correct?
- A. It creates a clone of a container.
- B. It writes the status of the container to a file.
- C. It creates a container image based on an existing container.
- D. It only works on stopped containers.
- E. It doubles the memory consumption of the container.
Answer: B
Explanation:
Explanation
The command lxc-checkpoint is used to checkpoint and restore containers. Checkpointing a container means saving the state of the container, including its memory, processes, file descriptors, and network connections, to a file or a directory. Restoring a container means resuming the container from the saved state, as if it was never stopped. Checkpointing and restoring containers can be useful for various purposes, such as live migration, backup, debugging, or snapshotting. The command lxc-checkpoint has the following syntax:
lxc-checkpoint {-n name} {-D path} [-r] [-s] [-v] [-d] [-F]
The options are:
* -n name: Specify the name of the container to checkpoint or restore.
* -D path: Specify the path to the file or directory where the checkpoint data is dumped or restored.
* -r, --restore: Restore the checkpoint for the container, instead of dumping it. This option is incompatible with -s.
* -s, --stop: Optionally stop the container after dumping. This option is incompatible with -r.
* -v, --verbose: Enable verbose criu logging. Only available when providing -r.
* -d, --daemon: Restore the container in the background (this is the default). Only available when providing -r.
* -F, --foreground: Restore the container in the foreground. Only available when providing -r.
The command lxc-checkpoint uses the CRIU (Checkpoint/Restore In Userspace) tool to perform the checkpoint and restore operations. CRIU is a software that can freeze a running application (or part of it) and checkpoint it to a hard drive as a collection of files. It can then use the files to restore and run the application from the point it was frozen at1.
The other statements about the command lxc-checkpoint are not correct. It does not create a clone or an image of a container, nor does it double the memory consumptionof the container. It can work on both running and stopped containers, depending on the options provided. References:
* Linux Containers - LXC - Manpages - lxc-checkpoint.12
* lxc-checkpoint(1) - Linux manual page - man7.org3
* CRIU4
NEW QUESTION # 47
Which file in acgroupdirectory contains the list of processes belonging to thiscgroup?
- A. subjects
- B. members
- C. casks
- D. procs
- E. pids
Answer: D
Explanation:
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 # 48
What is true aboutcontainerd?
- A. It uses rune to start containers on a container host.
- B. It is a text file format defining the build process of containers.
- C. It requires the Docker engine and Docker CLI to be installed.
- D. It is the initial process run at the start of any Docker container.
- E. It runs in each Docker container and provides DHCP client functionality
Answer: A
NEW QUESTION # 49
Which CPU flag indicates the hardware virtualization capability on an AMD CPU?
- A. VMX
- B. SVM
- C. PVM
- D. HVM
- E. VIRT
Answer: B
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 # 50
Which of the following commands executes a command in a running LXC container?
- A. lxc-eval
- B. lxc-batch
- C. lxc-enter
- D. lxc-accach
- E. lxc-run
Answer: D
NEW QUESTION # 51
Which of the following statements are true about container-based virtualization? (Choose two.)
- A. Container-based virtualization relies on hardware support from the host system's CPU.
- B. Each container runs its own operating system kernel.
- C. All containers run within the operating system kernel of the host system.
- D. Linux does not support container-based virtualization because of missing kernel APIs.
- E. Different containers may use different distributions of the same operating system.
Answer: C,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 # 52
Which of the following commands boots a QEMU virtual machine using hardware virtualization extensions?
- A. qemu -accel kvm -drive file-debian.img -cdrom debian.iso -m 1024 -boot d
- B. qvirt -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d -driver hvm
- C. vm -kvm -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
- D. qvm start -vmx -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
- E. qemu-hw -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
Answer: A
Explanation:
Explanation
The correct command to boot a QEMU virtual machine using hardware virtualization extensions is qemu
-accel kvm -drive file-debian.img -cdrom debian.iso -m 1024 -boot d. This command uses the -accel option to specify the hardware accelerator to use, which in this case is kvm. KVM is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V)1. The -drive option specifies the disk image file to use, which in this case is debian.img. The -cdrom option specifies the ISO image file to use as a CD-ROM, which in this case is debian.iso. The -m option specifies the amount of memory to allocate to the virtualmachine, which in this case is 1024 MB. The -boot option specifies the boot order, which in this case is d, meaning to boot from the CD-ROM first. References:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_
https://fedoraproject.org/wiki/Virtualization
NEW QUESTION # 53
What is the purpose of thekubeletservice in Kubernetes?
- A. Provide a command line interface to manage Kubernetes.
- B. Manage permissions of users when interacting with the Kubernetes API.
- C. Store and replicate Kubernetes configuration data.
- D. Build a container image as specified in a Dockerfile.
- E. Run containers on the worker nodes according to the Kubernetes configuration.
Answer: E
NEW QUESTION # 54
Which of the following commands boots a QEMU virtual machine using hardware virtualization extensions?
- A. qemu -accel kvm -drive file-debian.img -cdrom debian.iso -m 1024 -boot d
- B. qvirt -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d -driver hvm
- C. vm -kvm -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
- D. qvm start -vmx -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
- E. qemu-hw -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
Answer: A
NEW QUESTION # 55
Which of the following values are valid in the type attribute of a<domain>element in a libvirt domain definition? (Choose two.)
- A. Ixc
- B. proc
- C. namespace
- D. cgroup
- E. kvm
Answer: A,E
NEW QUESTION # 56
Which of the following statements are true regarding resource management for full virtualization? (Choose two.)
- A. All processes created within the virtual machines are transparently and equally scheduled in the host system for CPU and I/O usage.
- B. The hypervisor provides each virtual machine with hardware of a defined capacity that limits the resources of the virtual machine.
- C. Full virtualization cannot pose any limits to virtual machines and always assigns the host system's resources in a first-come-first-serve manner.
- D. It is up to the virtual machine to use its assigned hardware resources and create, for example, an arbitrary amount of network sockets.
- E. The hygervisor may provide fine-grained limits to internal elements of the guest operating system such as the number of processes.
Answer: B,D
Explanation:
Explanation
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 alsouse 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
NEW QUESTION # 57
Which of the following mechanisms are used by LXC and Docker to create containers? (Choose three.)
- A. Kernel Namespaces
- B. POSIXACLs
- C. File System Permissions
- D. Control Groups
- E. Linux Capabilities
Answer: A,D,E
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 # 58
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. virsh pool-create-as vms dir --target /vms
- B. touch /vms/.libvirtpool
- C. libvirt-poolctl new --name=/vms --type=dir --path=/vms
- D. dd if=/dev/zero of=/vms bs=1 count=0 flags=name:vms
- E. qemu-img pool vms:/vms
Answer: A
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 # 59
Which of the following statements are true about sparse images in the context of virtual machine storage?
(Choose two.)
- A. Sparse images can only be used in conjunction with paravirtualization.
- B. Sparse images allocate backend storage at the first usage of a block.
- C. Sparse images may consume an amount of space different from their nominal size.
- D. Sparse images are automatically shrunk when files within the image are deleted.
- E. Sparse images are automatically resized when their maximum capacity is about to be exceeded.
Answer: B,C
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 # 60
......
The LPI 305-300 exam is a valuable certification for anyone looking to advance their career in the IT industry. With the rapid growth in virtualization and containerization technologies, there is a high demand for skilled professionals who can effectively manage these systems. By obtaining this certification, professionals can demonstrate their expertise in these technologies and stand out in a competitive job market. LPIC-3 Exam 305: Virtualization and Containerization certification is recognized globally and is a testament to an individual's commitment to professional development and excellence in their field.
LATEST 305-300 Exam Practice Material: https://www.examsreviews.com/305-300-pass4sure-exam-review.html
The Realest Study Materials 305-300 Dumps: https://drive.google.com/open?id=1QEFGkTuBsi2f1lPPoaT_oPgDbfAbz5al