• ホーム
  • ブログ
  • [2024年07月23日] 最新版を今すぐ試そう305-300練習テスト問題解答 [Q37-Q58]

[2024年07月23日] 最新版を今すぐ試そう305-300練習テスト問題解答 [Q37-Q58]

Share

[2024年07月23日] 最新版を今すぐ試そう305-300練習テスト問題解答

305-300問題集と試験テストエンジン


LPIC-3試験305に備えて、ITプロフェッショナルは、LPI承認のトレーニングコース、学習ガイド、練習問題、オンラインフォーラムなどのさまざまなリソースを活用することができます。これらの教材を学習し、練習することで、ITプロフェッショナルは、試験に合格してLPIC-3認定を取得するために完全に準備することができます。


仮想化およびコンテナ化技術におけるLPIC-3認定は、専門家にいくつかの利点を提供できます。分野での知識とスキルを向上させ、より良い雇用機会とより高い給与を得る可能性を高めることができます。 LPIC-3認定も世界的に認識されており、専門家が世界のさまざまな地域で雇用を容易にします。

 

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

正解：C


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

正解：B


質問 # 39
Which of the following kinds of data cancloud-initprocess directly from user-data? (Choose three.)

  • A. Base64-encoded binary files to execute
  • B. Lists of URLs to import
  • C. cloud-config declarations in YAML
  • D. ISO images to boot from
  • E. Shell scripts to execute

正解：B、C、E

解説：
Explanation
Cloud-init is a tool that allows users to customize the configuration and behavior of cloud instances during the boot process. Cloud-init can process different kinds of data that are passed to the instance via user-data, which is a mechanism provided by various cloud providers to inject data into the instance. Among the kinds of data that cloud-init can process directly from user-data are:
* Shell scripts to execute: Cloud-init can execute user-data that is formatted as a shell script, starting with the #!/bin/sh or #!/bin/bash shebang. The script can contain any commands that are valid in the shell environment of the instance. The script is executed as the root user during the boot process12.
* Lists of URLs to import: Cloud-init can import user-data that is formatted as a list of URLs, separated by newlines. The URLs can point to any valid data source that cloud-init supports, such as shell scripts, cloud-config files, or include files. The URLs are fetched and processed by cloud-init in the order they appear in the list13.
* cloud-config declarations in YAML: Cloud-init can process user-data that is formatted as a cloud-config file, which is a YAML document that contains declarations for various cloud-init modules. The cloud-config file can specify various aspects of the instance configuration, such as hostname, users, packages, commands, services, and more. The cloud-config file must start with the #cloud-config header14.
The other kinds of data listed in the question are not directly processed by cloud-init from user-data. They are either not supported, not recommended, or require additional steps to be processed. These kinds of data are:
* ISO images to boot from: Cloud-init does not support booting from ISO images that are passed as user-data. ISO images are typically used to install an operating system on a physical or virtual machine, not to customize an existing cloud instance. To boot from an ISO image, the user would need to attach it as a secondary disk to the instance and configure the boot order accordingly5.
* Base64-encoded binary files to execute: Cloud-init does not recommend passing binary files as user-data, as they may not be compatible with the instance's architecture or operating system.
Base64-encoding does not change this fact, as it only converts the binary data into ASCII characters. To execute a binary file, the user would need to decode it and make it executable on the instance6.
References:
* User-Data Formats - cloud-init 22.1 documentation
* User-Data Scripts
* Include File
* Cloud Config
* How to Boot From ISO Image File Directly in Windows
* How to run a binary file as a command in the terminal?.


質問 # 40
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
Explanation
The default path to the Docker daemon configuration file on Linux is /etc/docker/daemon.json. This file is a JSON file that contains the settings and options for the Docker daemon, which is the service that runs on the host operating system and manages the containers, images, networks, and other Docker resources. The
/etc/docker/daemon.json file does not exist by default, but it can be created by the user to customize the Docker daemon behavior. The file can also be specified by using the --config-file flag when starting the Docker daemon. The file must be a valid JSON object and follow the syntax and structure of the dockerd reference docs12. References:
* Docker daemon configuration file - Medium3
* Docker daemon configuration overview | Docker Docs4
* docker daemon | Docker Docs5


質問 # 41
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 each virtual machine to provide Para virtualization which is required by QEMU.
  • C. 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
  • D. It must be loaded into the Kernel of the host system in order to use the visualization extensions of the host system's CPU
  • E. 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

解説：
Explanation
The Linux kernel module that must be loaded in order to use QEMU with hardware virtualization extensions is KVM (Kernel-based Virtual Machine). KVM is a full virtualization solution that allows a user space program (such as QEMU) to utilize the hardware virtualization features of various processors (such as Intel VT or AMD-V). KVM consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. KVM must be loaded into the kernel of the host system in order to use the virtualization extensions of the host system's CPU. This enables QEMU to run multiple virtual machines with unmodified Linux or Windows images, each with private virtualized hardware. KVM is integrated with QEMU, so there is no need to load it into the kernel of each virtual machine or the first virtual machine. KVM also does not require paravirtualization, which is a technique that modifies the guest operating system to communicate directly with the hypervisor, bypassing the emulation layer. References:
* Features/KVM - QEMU
* Kernel-based Virtual Machine
* KVM virtualization on Red Hat Enterprise Linux 8 (2023)


質問 # 42
Which of the following statements are true regarding VirtualBox?

  • A. It provides both a graphical user interface and command line tools to administer virtual machines.
  • B. It requires dedicated shared storage, as it cannot store virtual machine disk images locally on block devices of the virtualization host.
  • C. It is a hypervisor designed as a special kernel that is booted before the first regular operating system starts.
  • D. It only supports Linux as a guest operating system and cannot run Windows inside a virtual machine.
  • E. It is available for Linux only and requires the source code of the currently running Linux kernel to be available.

正解：A

解説：
Explanation
VirtualBox is a hosted hypervisor, which means it runs as an application on top of an existing operating system, not as a special kernel that is booted before the first regular operating system starts1. VirtualBox supports a large number of guest operating systems, including Windows, Linux, Solaris, OS/2, and OpenBSD1. VirtualBox does not require dedicated shared storage, as it can store virtual machine disk images locally on block devices of the virtualization host, or on network shares, or on iSCSI targets1. VirtualBox provides both a graphical user interface (GUI) and command line tools (VBoxManage) to administer virtual machines1. VirtualBox is available for Windows, Linux, macOS, and Solaris hosts1, and does not require the source code of the currently running Linux kernel to be available. References:
* Oracle VM VirtualBox: Features Overview


質問 # 43
Which of the following resources can be limited by libvirt for a KVM domain? (Choose two.)

  • A. Amount of CPU lime
  • B. Number of running processes
  • C. File systems allowed in the domain
  • D. Number of available files
  • E. Size of available memory

正解：A、E


質問 # 44
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. namespace
  • C. kvm
  • D. proc
  • E. cgroup

正解：A、C


質問 # 45
Which of the following resources can be limited by libvirt for a KVM domain? (Choose two.)

  • A. Amount of CPU lime
  • B. Number of running processes
  • C. File systems allowed in the domain
  • D. Number of available files
  • E. Size of available memory

正解：A、E

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


質問 # 46
What is the default provider of Vagrant?

  • A. virtualbox
  • B. docker
  • C. hyperv
  • D. vmware_workstation
  • E. lxc

正解：A

解説：
Explanation
Vagrant is a tool that allows users to create and configure lightweight, reproducible, and portable development environments. Vagrant supports multiple providers, which are the backends that Vagrant uses to create and manage the virtual machines. By default, VirtualBox is the default provider for Vagrant. VirtualBox is still the most accessible platform to use Vagrant: it is free, cross-platform, and has been supported by Vagrant for years. With VirtualBox as the default provider, it provides the lowest friction for new users to get started with Vagrant. However, users can also use other providers, such as VMware, Hyper-V, Docker, or LXC, depending on their preferences and needs. To use another provider, users must install it as a Vagrant plugin and specify it when running Vagrant commands. Users can also change the default provider by setting the VAGRANT_DEFAULT_PROVIDER environmental variable. References:
* Default Provider - Providers | Vagrant | HashiCorp Developer1
* Providers | Vagrant | HashiCorp Developer2
* How To Set Default Vagrant Provider to Virtualbox3


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

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

正解：D、E


質問 # 48
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. --attach=isolated_nw
  • B. --network=isolated_nw
  • C. --ethernet=isolated_nw
  • D. --alias=isolated_nw
  • E. --eth0=isolated_nw

正解：B

解説：
Explanation
To attach a container to a network when creating it, the --network flag must be used with the name of the network as the argument. The --network flag specifies the network mode for the container. By default, the network mode is bridge, which means the container is connected to the default bridge network. However, if a custom network is created, such as isolated_nw in this case, the container must be explicitly attached to it using the --network flag. For example, to create a container named web1 and attach it to the isolated_nw network, the command would be:
docker create --name web1 --network isolated_nw nginx
The other options are not valid parameters for docker create. The --eth0, --ethernet, and --attach flags do not exist. The --alias flag is used to specify an additional network alias for the container on a user-defined network, but it does not attach the container to the network. References:
* docker network create | Docker Documentation1
* docker create | Docker Documentation
* Networking overview | Docker Docs2


質問 # 49
What is the purpose of the commandvagrantinit?

  • A. It installs Vagrant on a Linux host.
  • B. It executes a provisioning tool in a running box.
  • C. It downloads a Vagrant box.
  • D. It creates a Vagrant configuration file.
  • E. It starts a Vagrant box.

正解：D


質問 # 50
Which of the following tasks are part of a hypervisor's responsibility? (Choose two.)

  • A. Create filesystems during the installation of new virtual machine quest operating systems.
  • B. Manage authentication to network services running inside a virtual machine.
  • C. Map the resources of virtual machines to the resources of the host system.
  • D. Provide host-wide unique PIDs to the processes running inside the virtual machines in order to ease inter-process communication between virtual machines.
  • E. Isolate the virtual machines and prevent unauthorized access to resources of other virtual machines.

正解：C、E

解説：
Explanation
A hypervisor is a software that creates and runs virtual machines (VMs) by separating the operating system and resources from the physical hardware. One of the main tasks of a hypervisor is to map the resources of VMs to the resources of the host system, such as CPU, memory, disk, and network. This allows the hypervisor to allocate and manage the resources among multiple VMs and ensure that they run efficiently and independently123. Another important task of a hypervisor is to isolate the VMs and prevent unauthorized access to resources of other VMs. This ensures the security and privacy of the VMs and their data, as well as the stability and performance of the host system. The hypervisor can use various techniques to isolate the VMs, such as virtual LANs, firewalls, encryption, and access control145.
The other tasks listed are not part of a hypervisor's responsibility, but rather of the guest operating system or the application running inside the VM. A hypervisor does not create filesystems during the installation of new VMs, as this is done by the installer of the guest operating system6. A hypervisor does not provide host-wide unique PIDs to the processes running inside the VMs, as this is done by the kernel of the guest operating system7. A hypervisor does not manage authentication to network services running inside a VM, as this is done by the network service itself or by a directory service such as LDAP or Active Directory8. References: 1 (search for "What is a hypervisor?"), 2 (search for "How does a hypervisor work?"), 3 (search for "The hypervisor gives each virtual machine the resources that have been allocated"), 4 (search for "Benefits ofhypervisors"), 5 (search for "Isolate the virtual machines and prevent unauthorized access"), 6 (search for "Create filesystems during the installation of new virtual machine quest operating systems"), 7 (search for "Provide host-wide unique PIDs to the processes running inside the virtual machines"), 8 (search for "Manage authentication to network services running inside a virtual machine").


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

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

正解：C


質問 # 52
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. namespace
  • C. kvm
  • D. proc
  • E. cgroup

正解：A、C

解説：
Explanation
The type attribute of a <domain> element in a libvirt domain definition specifies the hypervisor used for running the domain. The allowed values are driver specific, but include "xen", "kvm", "hvf" (since 8.1.0 and QEMU 2.12), "qemu" and "lxc"1. Therefore, the valid values among the options are C. kvm and E. lxc. KVM stands for Kernel-based Virtual Machine, which is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V)2. LXC stands for Linux Containers, which is an operating system-level virtualization method for running multiple isolated Linux systems (containers) on a single control host3. The other options are not valid values for the type attribute, asthey are either not hypervisors or not supported by libvirt. References:http://libvirt.org/formatdomain.html
https://libvirt.org/formatcaps.html


質問 # 53
Which of the following statements are true regarding resource management for full virtualization? (Choose two.)

  • A. The hygervisor may provide fine-grained limits to internal elements of the guest operating system such as the number of processes.
  • B. The hypervisor provides each virtual machine with hardware of a defined capacity that limits the resources of the virtual machine.
  • C. All processes created within the virtual machines are transparently and equally scheduled in the host system for CPU and I/O usage.
  • D. Full virtualization cannot pose any limits to virtual machines and always assigns the host system's resources in a first-come-first-serve manner.
  • E. It is up to the virtual machine to use its assigned hardware resources and create, for example, an arbitrary amount of network sockets.

正解：B、E

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


質問 # 54
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 creates a clone of a container.
  • D. It only works on stopped containers.
  • 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


質問 # 55
What does IaaS stand for?

  • A. Instances as a Service
  • B. Integration as a Service
  • C. Intelligence as a Service
  • D. Infrastructure as a Service
  • E. Information as a Service

正解：D

解説：
Explanation
IaaS is a type of cloud computing service that offers essential compute, storage, and networking resources on demand, on a pay-as-you-go basis. IaaS is one of the four types of cloud services, along with software as a service (SaaS), platform as a service (PaaS), and serverless12. IaaS eliminates the need for enterprises to procure, configure, or manage infrastructure themselves, and they only pay for what they use23. Some examples of IaaS providers are Microsoft Azure, Google Cloud, and Amazon Web Services.


質問 # 56
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 each virtual machine to provide Para virtualization which is required by QEMU.
  • C. 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
  • D. It must be loaded into the Kernel of the host system in order to use the visualization extensions of the host system's CPU
  • E. 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


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

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

正解：C


質問 # 58
......


Lpi 305-300試験は、仮想化およびコンテナ化の専門知識を開発したいLinuxプロフェッショナルにとって重要な認定試験です。この試験は、インストール、設定、管理、セキュリティ、およびパフォーマンス最適化など、これらの技術に関連するさまざまなトピックをカバーしています。候補者は、Linux管理およびネットワーキング、ストレージ技術についての堅固な理解力、および仮想化およびコンテナ化技術での経験を持つ必要があります。適切な準備をすることで、この試験に合格することで、Linuxプロフェッショナルはキャリアアップし、雇用主に自分の専門知識を証明できます。

 

2024年最新のGoShiken 305-300のPDFで最近更新された問題です：https://www.goshiken.com/Lpi/305-300-mondaishu.html

Lpi 305-300問題集にはリアル試験問題解答：https://drive.google.com/open?id=1HA7Ab9KWSGAhQX_3BgAyxaGfqobNl6UD

関するブログ

もっと
305-300無料問題集