Nov-2024 Realistic 305-300 Accurate & Verified Answers As Experienced in the Actual Test!
Latest Lpi 305-300 Practice Test Questions, LPIC-3 Exam 305: Virtualization and Containerization Exam Dumps
NEW QUESTION # 22
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-delta -a vm1-snap.img -A vm1.img
- C. virt-diff -a vm1-snap.img -A vm1.img
- D. virt-cp-in -a vm1-snap.img -A vm1.img
- E. virt-history -a vm1-snap.img -A vm1.img
Answer: C
NEW QUESTION # 23
How does Packer interact with system images?
- A. Packer installs a client within the image which has to be run periodically via cron in order to retrieve the latest template from the Packer server and apply it locally.
- B. Packer has to be installed within the target image and is executed during the image's first boot in order to execute preparation tasks.
- C. Packer downloads and extracts an image in order to make changes to the image's file system, repack the modified image and upload it again.
- D. Packer periodically connects through the network to the Packer daemons of all running Packer images in order to re-apply the whole template to the running instance.
- E. Packer creates an instance based on a source image, prepares the instance through a network connection and bundles the resulting instance as a new system image.
Answer: E
NEW QUESTION # 24
If aDockerfilecontains the following lines:
WORKDIR /
RUN cd /tmp
RUN echo test > test
where is the filetestlocated?
- A. /ting/test within the container image.
- B. /root/tesc within the container image.
- C. test in the directory holding the Dockerf ile.
- D. /tmp/test on the system running docker build.
- E. /test within the container image.
Answer: E
NEW QUESTION # 25
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 # 26
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 lists files existing in a Docker image which should be excluded when building a derivative image.
- C. It specifies which parts of a Dockerfile should be ignored when building a Docker image.
- D. It exists in the root file system of containers that should ignore volumes and ports provided by Docker.
- E. It must be placed in the top level directory of volumes that Docker should never attach automatically to a container
Answer: A
NEW QUESTION # 27
FILL BLANK
What is the default path to the Docker daemon configuration file on Linux? (Specify the full name of the file,Including path.)
Answer:
Explanation:
/etc/docker/daemon.json
NEW QUESTION # 28
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
NEW QUESTION # 29
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
Explanation
The lxc-attach command allows the user to start a new process within a running LXC container12. It takes the name of the container as an argument and optionally a command to execute inside the container. If no command is specified, it creates a new shell inside the container1. For example, to list all the files in the home directory of a container named myContainer, one can use:
lxc-attach -n myContainer - ls -lh /home
References:
* 1: Executing a command inside a running LXC - Unix & Linux Stack Exchange
NEW QUESTION # 30
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. All processes created within the virtual machines are transparently and equally scheduled in the host system for CPU and I/O usage.
- C. The hypervisor provides each virtual machine with hardware of a defined capacity that limits the resources of the virtual machine.
- 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: C,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 # 31
What is true aboutcontainerd?
- A. It is the initial process run at the start of any Docker container.
- B. It runs in each Docker container and provides DHCP client functionality
- C. It requires the Docker engine and Docker CLI to be installed.
- D. It uses rune to start containers on a container host.
- E. It is a text file format defining the build process of containers.
Answer: D
NEW QUESTION # 32
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 -v /data --name service debian bash
- B. docker run --volumes-from datastore --name service debian bash
- C. docker run --volume-backend datastore -v /data --name service debian bash
- D. docker run -v datastore:/data --name service debian bash
- E. docker run --share-with datastore --name service debian bash
Answer: B
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 # 33
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. Each QEMU virtual machine can only have one CPU with one core.
- C. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.
- D. QEMU uses the concept of virtual CPUs to map the virtual machines to physical CPUs.
- E. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
Answer: C,E
NEW QUESTION # 34
What happens when the following command is executed twice in succession?
docker run -tid -v data:/data debian bash
- A. The original content of the container image data is available in both containers, although changes stay local within each container.
- B. The container resulting from the second invocation can only read the content of /data/ and cannot change it.
- C. Each container is equipped with its own independent data volume, available at /data/ in the respective container.
- D. Both containers share the contents of the data volume, have full permissions to alter its content and mutually see their respective changes.
- E. The second command invocation fails with an error stating that the volume data is already associated with a running container.
Answer: D
NEW QUESTION # 35
Which of the following devices exist by default in an LXC container? (Choose three.)
- A. /dev/console
- B. /dev/log
- C. /dev/root
- D. /dev/urandom
- E. /dev/kmem
Answer: A,B,D
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 # 36
Which of the following resources can be limited by libvirt for a KVM domain? (Choose two.)
- A. Amount of CPU lime
- B. Number of available files
- C. File systems allowed in the domain
- D. Number of running processes
- E. Size of available memory
Answer: A,E
NEW QUESTION # 37
Which of the following statements is true regarding the following output ofxl list:
- A. CentOS is the domain which has consumed the most CPU time.
- B. The domain with ID 2 uses Para virtualization.
- C. It is necessary to use the xl command to change Ubuntu's state to running.
- D. Both Debian and Ubuntu require xl commands to start running.
- E. Ubuntu is idle or waiting for I/O.
Answer: E
Explanation:
Explanation
The output of xl list shows the state of the domains. The domain with ID 6, Ubuntu, has a state of "b-". This means that the domain is blocked, which means it is idle or waiting for I/O.
https://xenbits.xen.org/docs/unstable/man/xl.1.html
NEW QUESTION # 38
......
Free 305-300 Exam Files Downloaded Instantly 100% Dumps & Practice Exam: https://www.validtorrent.com/305-300-valid-exam-torrent.html
Nov-2024 Pass Lpi 305-300 Exam in First Attempt Easily: https://drive.google.com/open?id=1ap-CmXAfKF141_Pj5uUhQeO7MmPA778O