2024年02月26日更新された305-300トレーニング最新認定問題をゲットLPIC-3合格目指せ [Q12-Q37]

2024年02月26日更新された305-300トレーニング最新認定問題をゲットLPIC-3合格目指せ

認定トレーニング305-300試験問題集でテストエンジン

LPIC-3試験305は、仮想化とコンテナ化技術に焦点を当てた高度に専門的な試験です。この専門分野で知識とスキルをテストしたいIT専門家向けに設計されています。この試験に合格すると、今日の雇用市場で競争力があり、キャリアの成長のための新しい機会が開かれます。

LPI 305-300試験は、Linux Professional Instituteが管理する専門的な認定試験です。この試験は、仮想化とコンテナ化技術における高度な知識と経験を検証したい人向けに設計されています。 LPI 305-300試験は、LPIC-3認定プログラムの一部であり、ベンダー中立である高度なレベルのソフトウェア認証プログラムです。

 

質問 # 12
FILL BLANK
What command is used to run a process in a new Linux namespace? (Specify ONLY the command without any path or parameters.)

正解：

解説：
unshare

質問 # 13
Which functionality is provided by Vagrant as well as by Docker? (Choose three.)

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

正解：B、C、E

質問 # 14
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 any of Xen's global configuration files.
• B. In its .config file, when the Domain-0 kernel is built.
• C. In the bootloader configuration, when Xen is booted.
• D. In the configuration file /etc/xen/Domain-0.cfg, when Xen starts.
• E. In its Makefile, when Xen is built.

正解：C

質問 # 15
FILL BLANK
What is the default path to the Docker daemon configuration file on Linux? (Specify the full name of the file,Including path.)

正解：

解説：
/etc/docker/daemon.json

質問 # 16
What is the purpose ofcloud-init?

• A. Orchestrate the creation and start of multiple related laaS instances.
• B. Assign an laaS instance to a specific computing node within a cloud.
• C. Prepare the generic image of an laaS instance to fit a specific instance's configuration.
• D. Standardize the configuration of infrastructure services, such as load balancers or virtual firewalls in a cloud.
• E. Replace common Linux inic systems, such as systemd or SysV init.

正解：C

解説：
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

質問 # 17
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 transfers the image from its local Docker cache to each Swarm node.
• B. docker stack builds the images locally and copies them to only those Swarm nodes which run the service.
• C. docker stack passes the images to the Swarm master which distributes the images to all other Swarm nodes.
• D. docker stack triggers the build process for the images on all nodes of the Swarm.
• E. docker stack instructs the Swarm nodes to pull the images from a registry, although it does not upload the images to the registry.

正解：E

解説：
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

質問 # 18
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. qvm start -vmx -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
• C. vm -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. qvirt -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d -driver hvm

正解：A

質問 # 19
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 transfers the image from its local Docker cache to each Swarm node.
• B. docker stack builds the images locally and copies them to only those Swarm nodes which run the service.
• C. docker stack passes the images to the Swarm master which distributes the images to all other Swarm nodes.
• D. docker stack triggers the build process for the images on all nodes of the Swarm.
• E. docker stack instructs the Swarm nodes to pull the images from a registry, although it does not upload the images to the registry.

正解：E

質問 # 20
What kind of virtualization is implemented by LXC?

• A. Application containers
• B. Hardware containers
• C. CPU emulation
• D. Paravirtualization
• E. System containers

正解：E

解説：
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

質問 # 21
Which of the following services can QEMU provide in a user network? (Choose three.)

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

正解：B、D

解説：
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

質問 # 22
Which command within virsh lists the virtual machines that are running on the current host?

• A. show
• B. list-all
• C. list-vm
• D. list
• E. I view

正解：D

質問 # 23
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. Network Interfaces
• B. Hard Disks
• C. IO Cache
• D. Memory
• E. Host Bus Adapters

正解：D

解説：
Explanation
Nested page table extensions, such as Intel Extended Page Table (EPT) or AMD Rapid Virtualization Indexing (RVI), are hardware features that facilitate the virtualization of memory. They allow the CPU to perform the translation of guest virtual addresses to host physical addresses in a single step, without the need for software-managed shadow page tables. This reduces the overhead and complexity of memory management for virtual machines, and improves their performance and isolation. Nested page table extensions do not directly affect the virtualization of other hardware components, such as network interfaces, host bus adapters, hard disks, or IO cache.
References:
* Second Level Address Translation - Wikipedia
* c - What is use of extended page table? - Stack Overflow
* Hypervisor From Scratch - Part 4: Address Translation Using Extended ...

質問 # 24
Which of the following commands deletes all volumes which are not associated with a container?

• A. docker volume prune
• B. docker volume orphan -d
• C. docker volume vacuum
• D. docker volume cleanup
• E. docker volume garbage-collect

正解：A

解説：
Explanation
The command that deletes all volumes which are not associated with a container is docker volume prune. This command removes all unused local volumes, which are those that are not referenced by any containers. By default, it only removes anonymous volumes, which are those that are not given a specific name when they are created. To remove both unused anonymous and named volumes, the --all or -a flag can be added to the command. The command will prompt for confirmation before deleting the volumes, unless the --force or -f flag is used to bypass the prompt. The command will also show the total reclaimed space after deleting the volumes12.
The other commands listed in the question are not valid or do not have the same functionality as docker volume prune. They are either made up, misspelled, or have a different purpose. These commands are:
* docker volume cleanup: This command does not exist in Docker. There is no cleanup subcommand for docker volume.
* docker volume orphan -d: This command does not exist in Docker. There is no orphan subcommand for docker volume, and the -d flag is not a valid option for any docker volume command.
* docker volume vacuum: This command does not exist in Docker. There is no vacuum subcommand for docker volume.
* docker volume garbage-collect: This command does not exist in Docker. There is no garbage-collect subcommand for docker volume.
References:
* docker volume prune | Docker Docs
* How to Remove all Docker Volumes - YallaLabs.

質問 # 25
Which of the following services can QEMU provide in a user network? (Choose three.)

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

正解：B、C、E

質問 # 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.

正解：A

解説：
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?

質問 # 27
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.)

正解：

解説：
net-edit

質問 # 28
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. virt-sparsi
• C. virt-rescue
• D. vire-wipe
• E. virc-reset
• F. sysprep

正解：A

質問 # 29
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*

正解：B、D

解説：
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

質問 # 30
Which of the following statements about the commandlxc-checkpointis correct?

• A. It doubles the memory consumption of the container.
• B. It creates a container image based on an existing container.
• C. It only works on stopped containers.
• D. It creates a clone of a container.
• E. It writes the status of the container to a file.

正解：E

解説：
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

質問 # 31
Which of the following values are valid in thefirmwareattribute of a<os>element in a libvirt domain definition?(Choose two.)

• A. virtio
• B. pcie
• C. scsi
• D. efi
• E. bios

正解：D、E

解説：
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)

質問 # 32
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. qemu-img pool vms:/vms
• D. libvirt-poolctl new --name=/vms --type=dir --path=/vms
• E. dd if=/dev/zero of=/vms bs=1 count=0 flags=name:vms

正解：A

質問 # 33
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. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
• D. For each QEMU virtual machine, one dedicated physical CPU core must be reserved.
• E. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.

正解：C、E

解説：
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

質問 # 34
Which command within virsh lists the virtual machines that are running on the current host?

• A. show
• B. list-all
• C. list-vm
• D. list
• E. I view

正解：D

解説：
Explanation
The command virsh list is used to list all running domains (VMs) on the current host. The command virsh list
--all can be used to list both active and inactive domains. The other options are not valid virsh commands. The command virsh list is a basic command that lists all running domains (VMs). You can also list all configured VMs by adding the --all option. This is useful if you want to see all VMs configured in the target hypervisor that you can use on subsequent commands1. References:
* 1: 8 Linux virsh subcommands for managing VMs on the command line | Enable Sysadmin.

質問 # 35
If aDockerfilecontains the following lines:
WORKDIR /
RUN cd /tmp
RUN echo test > test
where is the filetestlocated?

• A. /tmp/test on the system running docker build.
• B. test in the directory holding the Dockerf ile.
• C. /root/tesc within the container image.
• D. /test within the container image.
• E. /ting/test within the container image.

正解：D

解説：
Explanation
The WORKDIR instruction sets the working directory for any subsequent RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile1. The RUN instruction executes commands in a new layer on top of the current image and commits the results2. The RUN cd command does not change the working directory for the next RUN instruction, because each RUN command runs in a new shell and a new environment3. Therefore, the file test is created in the root directory (/) of the container image, not in the /tmp directory. References:
* Dockerfile reference: WORKDIR
* Dockerfile reference: RUN
* difference between RUN cd and WORKDIR in Dockerfile

質問 # 36
Which of the following devices exist by default in an LXC container? (Choose three.)

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

正解：A、C、E

質問 # 37
......

LPIC-3 Exam 305は、仮想化およびコンテナ化技術についての堅固な理解と、これらの技術を実際のシナリオで展開および管理する経験を求められる上級レベルの認定試験です。この認定は、仮想化およびコンテナ化分野でキャリアを進めたいITプロフェッショナルを対象に設計されており、彼らの専門知識と信頼性を潜在的な雇用主に証明することを目的としています。

 

合格を確定するガイドで305-300試験準備しよう：https://jp.fast2test.com/305-300-premium-file.html

LPIC-3 305-300無料最新のリアル試験問題と回答：https://drive.google.com/open?id=1RKOl6pYJIs1vJ2GWeRlHTthfziltuxPf