Updated Dec-2024 Official licence for 305-300 Certified by 305-300 Dumps PDF
Grab latest Amazon 305-300 Dumps as PDF Updated on 2024
The LPIC-3 Exam 305 is a challenging exam that requires a deep understanding of virtualization and containerization technologies. IT professionals who pass 305-300 exam demonstrate their ability to design, deploy, and manage virtualized and containerized environments in a secure and efficient manner. The LPIC-3 certification is highly respected in the IT industry and is recognized by many organizations worldwide. By earning the LPIC-3 certification, IT professionals can enhance their career prospects and take on more challenging roles in their organizations.
NEW QUESTION # 23
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. --alias=isolated_nw
- B. --ethernet=isolated_nw
- C. --network=isolated_nw
- D. --attach=isolated_nw
- E. --eth0=isolated_nw
Answer: C
NEW QUESTION # 24
FILL BLANK
What LXC command starts a new process within a running LXC container? (Specify ONLY the command without any path or parameters.)
Answer:
Explanation:
lxc-attach
NEW QUESTION # 25
Which of the following statements are true regarding a Pod in Kubernetes? (Choose two.)
- A. All containers of a Pod run on the same node.
- B. When a Pod fails, Kubernetes restarts the Pod on another node by default.
- C. A Pod is the smallest unit of workload Kubernetes can run.
- D. Pods are always created automatically and cannot be explicitly configured.
- E. systemd is used to manage individual Pods on the Kubernetes nodes.
Answer: A,C
NEW QUESTION # 26
What is the purpose ofcloud-init?
- A. Prepare the generic image of an laaS instance to fit a specific instance's configuration.
- B. Standardize the configuration of infrastructure services, such as load balancers or virtual firewalls in a cloud.
- C. Assign an laaS instance to a specific computing node within a cloud.
- D. Replace common Linux inic systems, such as systemd or SysV init.
- E. Orchestrate the creation and start of multiple related laaS instances.
Answer: A
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 # 27
Which of the following devices exist by default in an LXC container? (Choose three.)
- A. /dev/kmem
- B. /dev/console
- C. /dev/root
- D. /dev/log
- E. /dev/urandom
Answer: B,D,E
Explanation:
Explanation
LXC (Linux Containers) is a lightweight virtualization technology that allows multiple isolated Linux systems (containers) to run on the same host. LXC uses Linux kernel features such as namespaces, cgroups, and AppArmor to create and manage containers. Each container has its own file system, network interfaces, process tree, and resource limits. However, containers share the same kernel and hardware with the host, which makes them more efficient and faster than full virtualization.
By default, an LXC container has a minimal set of devices that are needed for its operation. These devices are created by the LXC library when the container is started, and are removed when the container is stopped. The default devices are:
* /dev/log: This is a Unix domain socket that connects to the syslog daemon on the host. It allows the container to send log messages to the host's system log1.
* /dev/console: This is a character device that provides access to the container's console. It is usually connected to the host's terminal or a file. It allows the container to interact with the user or the host's init system12.
* /dev/urandom: This is a character device that provides an unlimited source of pseudo-random numbers. It is used by various applications and libraries that need randomness, such as cryptography, UUID generation, and hashing13.
The other devices listed in the question do not exist by default in an LXC container. They are either not needed, not allowed, or not supported by the container's namespace or cgroup configuration. These devices are:
* /dev/kmem: This is a character device that provides access to the kernel's virtual memory. It is not needed by the container, as it can access its own memory through the /proc filesystem. It isalso not allowed by the container, as it would expose the host's kernel memory and compromise its security4.
* /dev/root: This is a symbolic link that points to the root device of the system. It is not supported by the container, as it does not have a separate root device from the host. The container's root file system is mounted from a directory, an image file, or a loop device on the host5.
References:
* Linux Containers - LXC - Manpages - lxc.container.conf.5
* Linux Containers - LXC - Getting started
* Random number generation - Wikipedia
* /dev/kmem - Wikipedia
* Linux Containers - LXC - Manpages - lxc.container.conf.5
NEW QUESTION # 28
In order to use the optiondom0_memto limit the amount of memory assigned to the Xen Domain-0, where must this option be specified?
- A. In its Makefile, when Xen is built.
- B. In the configuration file /etc/xen/Domain-0.cfg, when Xen starts.
- C. In the bootloader configuration, when Xen is booted.
- D. In its .config file, when the Domain-0 kernel is built.
- E. In any of Xen's global configuration files.
Answer: C
NEW QUESTION # 29
Which of the following commands lists all differences between the disk images vm1-snap.img and vm1.img?
- A. virt-cmp -a vm1-snap.img -A vm1.img
- B. virt-diff -a vm1-snap.img -A vm1.img
- C. virt-delta -a vm1-snap.img -A vm1.img
- D. virt-history -a vm1-snap.img -A vm1.img
- E. virt-cp-in -a vm1-snap.img -A vm1.img
Answer: B
Explanation:
Explanation
The virt-diff command-line tool can be used to list the differences between files in two virtual machines or disk images. The output shows the changes to a virtual machine's disk images after it has been running. The command can also be used to show the difference between overlays1. To specify two guests, you have to use the -a or -d option for the first guest, and the -A or -D option for the second guest. For example: virt-diff -a old.img -A new.img1. Therefore, the correct command to list all differences between the disk images vm1-snap.img and vm1.img is: virt-diff -a vm1-snap.img -A vm1.img. The other commands are not related to finding differences between disk images. virt-delta is a tool to create delta disks from two disk images2. virt-cp-in is a tool to copy files and directories into a virtual machine disk image3. virt-cmp is a tool to compare two files or directories in a virtual machine disk image4. virt-history is a tool to show the history of a virtual machine disk image5. References:
* 21.13. virt-diff: Listing the Differences between Virtual Machine Files ...
* 21.14. virt-delta: Creating Delta Disks from Two Disk Images ...
* 21.6. virt-cp-in: Copying Files and Directories into a Virtual Machine Disk Image ...
* 21.7. virt-cmp: Comparing Two Files or Directories in a Virtual Machine Disk Image ...
* 21.8. virt-history: Showing the History of a Virtual Machine Disk Image ...
NEW QUESTION # 30
Which of the following commands boots a QEMU virtual machine using hardware virtualization extensions?
- A. qvirt -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d -driver hvm
- B. qvm start -vmx -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
- C. qemu -accel kvm -drive file-debian.img -cdrom debian.iso -m 1024 -boot d
- D. qemu-hw -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
- E. vm -kvm -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
Answer: C
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 # 31
Which of the following are true regarding the CPU of a QEMU virtual machine? (Choose two.)
- A. Each QEMU virtual machine can only have one CPU with one core.
- B. QEMU uses the concept of virtual CPUs to map the virtual machines to physical CPUs.
- C. For each QEMU virtual machine, one dedicated physical CPU core must be reserved.
- D. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.
- E. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
Answer: D,E
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 # 32
Which command within virsh lists the virtual machines that are running on the current host?
- A. I view
- B. list
- C. show
- D. list-vm
- E. list-all
Answer: B
NEW QUESTION # 33
Which of the following tasks are part of a hypervisor's responsibility? (Choose two.)
- A. Manage authentication to network services running inside a virtual machine.
- B. Map the resources of virtual machines to the resources of the host system.
- C. Provide host-wide unique PIDs to the processes running inside the virtual machines in order to ease inter-process communication between virtual machines.
- D. Isolate the virtual machines and prevent unauthorized access to resources of other virtual machines.
- E. Create filesystems during the installation of new virtual machine quest operating systems.
Answer: B,D
NEW QUESTION # 34
What is the purpose of the packer inspect subcommand?
- A. Display an overview of the configuration contained in a Packer template.
- B. Retrieve files from an existing Packer image.
- C. Show usage statistics of a Packer image.
- D. Execute commands within a running instance of a Packer image.
- E. List the artifacts created during the build process of a Packer image.
Answer: A
Explanation:
* The purpose of the packer inspect subcommand is to display an overview of the configuration contained in a Packer template1. A Packer template is a file that defines the various components a Packer build requires, such as variables, sources, provisioners, and post-processors2. The packer inspect subcommand can help you quickly learn about a template without having to dive into the HCL (HashiCorp Configuration Language) itself1. 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 more1.
* 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 machine2.
* 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 command2.
* 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 details2.
* 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 session2. References: 1: packer inspect - Commands | Packer | HashiCorp Developer 2:
Commands | Packer | HashiCorp Developer
NEW QUESTION # 35
FILL BLANK
What command is used to run a process in a new Linux namespace? (Specify ONLY the command without any path or parameters.)
Answer:
Explanation:
unshare
NEW QUESTION # 36
How can data be shared between several virtual machines running on the same Linux-based host system?
- A. By using a network file system or file transfer protocol.
- B. By mounting other virtual machines' file systems from /dev/virt-disks/remote/.
- C. By setting up a ramdisk in one virtual machine and mounting it using its UUID in the other VMs.
- D. By writing data to the file system since all virtual machines on the same host system use the same file system.
- E. By attaching the same virtual hard disk to all virtual machines and activating EXT4 sharing extensions on it.
Answer: A
Explanation:
Explanation
The correct way to share data between several virtual machines running on the same Linux-based host system is by using a network file system or file transfer protocol. A network file system (NFS) is a distributed file system protocol that allows a user on a client computer to access files over a network in a manner similar to how local storage is accessed1. A file transfer protocol (FTP) is a standard network protocol used for the transfer of computer files between a client and server on a computer network2. Both methods allow data to be shared between virtual machines regardless of their underlying file systems or virtualization technologies. The other options are incorrect because they either do not work or are not feasible. Option A is wrong because each virtual machine has its own file system that is not directly accessible by other virtual machines. Option B is wrong because there is no such device as /dev/virt-disks/remote/ that can be used to mount other virtual machines' file systems. Option C is wrong because a ramdisk is a volatile storage device that is not suitable for sharing data between virtual machines. Option E is wrong because attaching the same virtual hard disk to multiple virtual machines can cause data corruption and conflicts, and EXT4 does not have any sharing extensions that can prevent this. References:https://kb.vmware.com/s/article/1012706
https://bing.com/search?q=data+sharing+between+virtual+machines
NEW QUESTION # 37
Which of the following statements is true regarding networking with libvirt?
- A. Libvirt networks appear, by default, as standard Linux bridges in the host system.
- B. Libvirt supports exactly one virtual network and connects all virtual machines to it.
- C. Libvirt assiqns the same MAC address to all virtual machines and isolates their network interfaces at the link layer.
- D. Libvirt's network functionality is limited to connectingvirtual machines to a physical network interface of the host system.
- E. Libvirt requires a dedicated network interface that may not be used by the host system.
Answer: A
NEW QUESTION # 38
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. qemu-img pool vms:/vms
- 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. touch /vms/.libvirtpool
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 # 39
Which of the following statements is true regarding networking with libvirt?
- A. Libvirt networks appear, by default, as standard Linux bridges in the host system.
- B. Libvirt supports exactly one virtual network and connects all virtual machines to it.
- C. Libvirt assiqns the same MAC address to all virtual machines and isolates their network interfaces at the link layer.
- D. Libvirt requires a dedicated network interface that may not be used by the host system.
- E. Libvirt's network functionality is limited to connecting virtual machines to a physical network interface of the host system.
Answer: A
Explanation:
Explanation
Libvirt supports creating and managing various types of virtual networks that can be used to connect virtual machines to each other or to the external network. One of the common types of virtual networks is the NAT-based network, which uses network address translation (NAT) to allow virtual machines to access the outside world through the host's network interface. By default, libvirt creates a NAT-based network called
'default' when it is installed and started. This network appears as a standard Linux bridge device on the host system, named virbr0. The bridge device has an IP address of 192.168.122.1/24 and acts as a gateway and a DHCP server for the virtual machines connected to it. The bridge device also has iptables rules to forward and masquerade the traffic from and to the virtual machines. The virtual machines connected to the 'default' network have their own IP addresses in the 192.168.122.0/24 range and their own MAC addresses generated by libvirt. The virtual machines can communicate with each other, with the host, and with the external network through the bridge device and the NAT mechanism12.
The other statements in the question are false regarding networking with libvirt. Libvirt's network functionality is not limited to connecting virtual machines to a physical network interface of the host system. Libvirt can also create isolated networks that do not have any connection to the outside world, or routed networks that use static routes to connect virtual machines to the external network without NAT3.
Libvirt does not assign the same MAC address to all virtual machines and isolate their network interfaces at the link layer. Libvirt assigns a unique MAC address to each virtual machine and allows them to communicate with each other at the network layer4. Libvirt does not require a dedicated network interface that may not be used by the host system. Libvirt can share the host's network interface with the virtual machines using NAT or bridging, or it can pass a physical network interface to a virtual machine exclusively using PCI passthrough5.
Libvirt does not support exactly one virtual network and connect all virtual machines to it. Libvirt supports creating and managing multiple virtual networks with different names and configurations, and connecting virtual machines to different networks according to their needs6. References:
* libvirt: Virtual Networking
* libvirt: NAT forwarding (aka "virtual networks")
* libvirt: Routed network
* libvirt: MAC address
* libvirt: PCI passthrough of host network devices
* [libvirt: Network XML format]
NEW QUESTION # 40
Virtualization of which hardware component is facilitated by CPUs supporting nested page table extensions, such as Intel Extended Page Table (EPT) or AMD Rapid Virtualization Indexing (RVI)?
- A. Hard Disks
- B. Memory
- C. IO Cache
- D. Host Bus Adapters
- E. Network Interfaces
Answer: B
NEW QUESTION # 41
Which of the following resources can be limited by libvirt for a KVM domain? (Choose two.)
- A. Size of available memory
- B. Amount of CPU lime
- C. File systems allowed in the domain
- D. Number of available files
- E. Number of running processes
Answer: A,B
NEW QUESTION # 42
Which of the following commands executes a command in a running LXC container?
- A. lxc-batch
- B. lxc-eval
- C. lxc-run
- D. lxc-enter
- E. lxc-accach
Answer: E
Explanation:
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 # 43
......
Latest 305-300 Exam Dumps Lpi Exam from Training: https://www.realvce.com/305-300_free-dumps.html
Newly Released 305-300 Dumps for LPIC-3 Certified: https://drive.google.com/open?id=1eyuPz4S5EIuYcfI_I32C0Muh-Hjsym4v