Latest 305-300 Practice Test Questions Verified Answers As Experienced in the Actual Test!
Pass Lpi 305-300 Exam in First Attempt Easily
NEW QUESTION # 11
Which of the following statements is true regarding networking with libvirt?
- A. Libvirt's network functionality is limited to connectingvirtual machines to a physical network interface of the host system.
- B. Libvirt networks appear, by default, as standard Linux bridges in the host system.
- C. Libvirt supports exactly one virtual network and connects all virtual machines to it.
- D. Libvirt assiqns the same MAC address to all virtual machines and isolates their network interfaces at the link layer.
- E. Libvirt requires a dedicated network interface that may not be used by the host system.
Answer: B
NEW QUESTION # 12
Which of the following commands lists all differences between the disk images vm1-snap.img and vm1.img?
- A. virt-diff -a vm1-snap.img -A vm1.img
- B. virt-history -a vm1-snap.img -A vm1.img
- C. virt-cp-in -a vm1-snap.img -A vm1.img
- D. virt-delta -a vm1-snap.img -A vm1.img
- E. virt-cmp -a vm1-snap.img -A vm1.img
Answer: A
NEW QUESTION # 13
What is the purpose of capabilities in the context of container virtualization?
- A. Prevent processes from performing actions which might infringe the container.
- B. Enable memory deduplication to cache files which exist in multiple containers.
- C. Map potentially dangerous system calls to an emulation layer provided by the container virtualization.
- D. Restrict the disk space a container can consume.
- E. Allow regular users to start containers with elevated permissions.
Answer: A
NEW QUESTION # 14
Which of the following kinds of data cancloud-initprocess directly from user-data? (Choose three.)
- A. Lists of URLs to import
- B. Shell scripts to execute
- C. cloud-config declarations in YAML
- D. Base64-encoded binary files to execute
- E. ISO images to boot from
Answer: A,B,C
NEW QUESTION # 15
If aDockerfilecontains the following lines:
WORKDIR /
RUN cd /tmp
RUN echo test > test
where is the filetestlocated?
- A. /root/tesc within the container image.
- B. test in the directory holding the Dockerf ile.
- C. /ting/test within the container image.
- D. /test within the container image.
- E. /tmp/test on the system running docker build.
Answer: D
NEW QUESTION # 16
What is the purpose of the commandvagrant init?
- A. It starts a Vagrant box.
- B. It installs Vagrant on a Linux host.
- C. It executes a provisioning tool in a running box.
- D. It downloads a Vagrant box.
- E. It creates a Vagrant configuration file.
Answer: E
Explanation:
Explanation
The command vagrant init is used to initialize the current directory to be a Vagrant environment by creating an initial Vagrantfile if one does not already exist1. The Vagrantfile contains the configuration settings for the Vagrant box, such as the box name, box URL, network settings, synced folders, provisioners, etc. The command vagrant init does not execute any provisioning tool, start any box, install Vagrant on a Linux host, or download any box. Those actions are performed by other Vagrant commands, such as vagrant provision, vagrant up, vagrant install, and vagrant box add, respectively. References:
* 1: vagrant init - Command-Line Interface | Vagrant | HashiCorp Developer
NEW QUESTION # 17
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. Pods are always created automatically and cannot be explicitly configured.
- D. systemd is used to manage individual Pods on the Kubernetes nodes.
- E. A Pod is the smallest unit of workload Kubernetes can run.
Answer: A,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 # 18
Ifdocker stackis to be used to run a Docker Compose file on a Docker Swarm, how are the images referenced in the Docker Compose configuration made available on the Swarm nodes?
- A. docker stack triggers the build process for the images on all nodes of the Swarm.
- B. docker stack transfers the image from its local Docker cache to each Swarm node.
- C. docker stack builds the images locally and copies them to only those Swarm nodes which run the service.
- D. docker stack instructs the Swarm nodes to pull the images from a registry, although it does not upload the images to the registry.
- E. docker stack passes the images to the Swarm master which distributes the images to all other Swarm nodes.
Answer: D
Explanation:
Explanation
Docker stack is a command that allows users to deploy and manage a stack of services on a Docker Swarm cluster. A stack is a group of interrelated services that share dependencies and can be orchestrated and scaled together. A stack is typically defined by a Compose file, which is a YAML file that describes the services, networks, volumes, and other resources of the stack. To use docker stack to run a Compose file on a Swarm, the user must first create and initialize a Swarm cluster, which is a group of machines (nodes) that are running the Docker Engine and are joined into a single entity. The Swarm cluster has one or more managers, which are responsible for maintaining the cluster state and orchestrating the services, and one or more workers, which are the nodes that run the services.
When the user runs docker stack deploy with a Compose file, the command parses the file and creates the services as specified. However, docker stack does not build or upload the images referenced in the Compose file to any registry. Instead, it instructs the Swarm nodes to pull the images from a registry, which can be the public Docker Hub or a private registry. The user must ensure that the images are available in the registry before deploying the stack, otherwise the deployment will fail. The user can use docker build and docker push commands to create and upload the images to the registry, or use an automated build service such as Docker Hub or GitHub Actions. The user must also make sure that the image names and tags in the Compose file match the ones in the registry, and that the Swarm nodes have access to the registry if it is private. By pulling the images from a registry, docker stack ensures that the Swarm nodes have the same and latest version of the images, and that the images are distributed across the cluster in an efficient way.
The other options are not correct. Docker stack does not build the images locally or on the Swarm nodes, nor does it copy or transfer the images to the Swarm nodes. Dockerstack also does not pass the images to the Swarm master, as this would create a bottleneck and a single point of failure. Docker stack relies on the registry as the source of truth for the images, and delegates the image pulling to the Swarm nodes. References:
* Deploy a stack to a swarm | Docker Docs1
* docker stack deploy | Docker Docs2
* docker build | Docker Docs3
* docker push | Docker Docs4
NEW QUESTION # 19
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
Explanation
The unshare command is used to run a process in a new Linux namespace12. It takes one or more flags to specify which namespaces to create or unshare from the parent process1. For example, to run a shell in a new mount, network, and PID namespace, one can use:
unshare -mnp /bin/bash
References:
* 1: unshare(1) - Linux manual page - man7.org
* 2: A gentle introduction to namespaces in Linux - Packagecloud
NEW QUESTION # 20
Which of the following values are valid in thefirmwareattribute of a<os>element in a libvirt domain definition?(Choose two.)
- A. bios
- B. efi
- C. scsi
- D. pcie
- E. virtio
Answer: A,B
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 # 21
Which of the following services can QEMU provide in a user network? (Choose three.)
- A. AppleTalk
- B. BGP
- C. TFTP
- D. CIFS
- E. DHCP
Answer: C,E
Explanation:
Explanation
QEMU can provide some network services in a user network, which is a mode of networking that does not require any administrator privilege to run. The user network uses the SLIRP TCP/IP emulator to create a virtual NAT'ted subnet, with a DHCP server started by QEMU that gives out IP addresses to the guest machines and puts the host on 10.0.2.21. QEMU can also provide a TFTP server in the user network, which can be used to boot the guest machines from a network image. The TFTP server can be configured with the
-tftp option2. QEMU does not provide BGP, CIFS, or AppleTalk services in the user network. BGP is a routing protocol that is used to exchange routing information between autonomous systems on the Internet3. CIFS is a file-sharing protocol that is used to access files and printers on a network4. AppleTalk is a deprecated network protocol suite that was used by Apple devices5. These services require more advanced networking features than the user network can offer, such as bridging, routing, or tunneling.
References:
* Documentation/Networking - QEMU
* QEMU/Networking - Wikibooks, open books for an open world
* Border Gateway Protocol - Wikipedia
* Common Internet File System - Wikipedia
* AppleTalk - Wikipedia
NEW QUESTION # 22
Which of the following statements in aDockerfileleads to a container which outputs hello world? (Choose two.)
- A. ENTRYPOINT "echo", "Hello", "World*
- B. ENTRYPOINT [ "echo hello world" ]
- C. ENTRYPOINT "echo Hello World"
- D. ENTRYPOINT echo Hello World
- E. ENTRYPOINT [ "echo", "hello", "world" ]
Answer: B,E
Explanation:
Explanation
The ENTRYPOINT instruction in a Dockerfile specifies the default command to run when a container is started from the image. The ENTRYPOINT instruction can be written in two forms: exec form and shell form.
The exec form uses a JSON array to specify the command and its arguments, such as [ "executable",
"param1", "param2" ]. The shell form uses a single string to specify the command and its arguments, such as
"executable param1 param2". The shell form is converted to the exec form by adding /bin/sh -c to the beginning of the command. Therefore, the following statements in a Dockerfile are equivalent and will lead to a container that outputs hello world:
ENTRYPOINT [ "echo hello world" ] ENTRYPOINT [ "/bin/sh", "-c", "echo hello world" ] ENTRYPOINT
"echo hello world" ENTRYPOINT [ "echo", "hello", "world" ] ENTRYPOINT [ "/bin/sh", "-c", "echo",
"hello", "world" ] ENTRYPOINT "echo hello world"
The other statements in the question are invalid or incorrect. The statement A. ENTRYPOINT "echo Hello World" is invalid because it uses double quotes to enclose the entire command, which is not allowed in the shell form. The statement D. ENTRYPOINT echo Hello World is incorrect because it does not use quotes to enclose the command, which is required in the shell form. The statement E. ENTRYPOINT "echo", "Hello",
"World" is invalid because it uses double quotes to separate the command and its arguments, which is not allowed in the exec form. References:
* Dockerfile reference | Docker Docs
* Using the Dockerfile ENTRYPOINT and CMD Instructions - ATA Learning
* Difference Between run, cmd and entrypoint in a Dockerfile
NEW QUESTION # 23
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. Full virtualization cannot pose any limits to virtual machines and always assigns the host system's resources in a first-come-first-serve manner.
- C. It is up to the virtual machine to use its assigned hardware resources and create, for example, an arbitrary amount of network sockets.
- D. The hypervisor provides each virtual machine with hardware of a defined capacity that limits the resources of the virtual machine.
- 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 # 24
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
Explanation:
Explanation
Libvirt is a toolkit that provides a common API for managing different virtualization technologies, such as KVM, Xen, LXC, and others. Libvirt allows users to configure and control various aspects of a virtual machine (also called a domain), such as its CPU, memory, disk, network, and other resources. Among the resources that can be limited by libvirt for a KVM domain are:
* Amount of CPU time: Libvirt allows users to specify the number of virtual CPUs (vCPUs) that a domain can use, as well as the CPU mode, model, topology, and tuning parameters. Users can also set the CPU shares, quota, and period to control the relative or absolute amount of CPU time that a domain can consume. Additionally, users can pin vCPUs to physical CPUs or NUMA nodes to improve performance and isolation. These settings can be configured in the domain XML file under the <cpu> and <cputune> elements12.
* Size of available memory: Libvirt allows users to specify the amount of memory that a domain can use, as well as the memory backing, tuning, and NUMA node parameters. Users can also set the memory hard and soft limits, swap hard limit, and minimum guarantee to control the memory allocation and reclaim policies for a domain. These settings can be configured in the domain XML file under the <memory>, <memoryBacking>, and <memtune> elements13.
The other resources listed in the question are not directly limited by libvirt for a KVM domain. File systems allowed in the domain are determined by the disk and filesystem devices that are attached to the domain, which can be configured in the domain XML file under the <disk> and <filesystem> elements14. Number of running processes and number of available files are determined by the operating system and the file system of the domain, which are not controlled by libvirt.
References:
* libvirt: Domain XML format
* CPU Allocation
* Memory Allocation
* Hard drives, floppy disks, CDROMs
NEW QUESTION # 25
What is the purpose ofcloud-init?
- A. Replace commonLinux inic systems, such as systemd or SysV init.
- B. Assign an laaSinstance to a specific computingnode within a cloud.
- C. Prepare the generic image of an laaS instance to fit a specific instance's configuration.
- D. Orchestrate the creation and start of multiple related laaS instances.
- E. Standardize the configuration of infrastructure services, such as load balancers or virtual firewalls in a cloud.
Answer: C
NEW QUESTION # 26
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 is a clone of another currently running instance that includes all the software, data and state of the original instance.
- C. 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.
- D. Each new instance is connected to the installation media of a Linux distribution and provides access to the installer by logging in via SSH.
- 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 # 27
What is the purpose of a .dockerignore file?
- A. It exists in the root file system of containers that should ignore volumes and ports provided by Docker.
- B. It lists files existing in a Docker image which should be excluded when building a derivative image.
- C. It specifies files that Docker does not submit to the Docker daemon when building a Docker image
- D. It must be placed in the top level directory of volumes that Docker should never attach automatically to a container
- E. It specifies which parts of a Dockerfile should be ignored when building a Docker image.
Answer: C
NEW QUESTION # 28
......
We offers you the latest free online 305-300 dumps to practice: https://www.dumpexams.com/305-300-real-answers.html
The Most Efficient 305-300 Pdf Dumps For Assured Success : https://drive.google.com/open?id=1A10nQuPHWax8bC4smT5gdYFlJOCmlMKZ