[2024年11月11日] 手に入れよう！最新305-300認定された有効な試験問題集解答 [Q28-Q46]

[2024年11月11日] 手に入れよう！最新305-300認定された有効な試験問題集解答

100%合格率保証付きの素晴らしい305-300試験問題PDF

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

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

正解：A

質問 # 29
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
Explanation
The subcommand of virsh that opens the XML configuration of a virtual network in an editor in order to make changes to that configuration is net-edit1. This subcommand takes the name or UUID of the network as a parameter and opens the network XML file in the default editor, which is specified by the $EDITOR shell variable1. The changes made to the network configuration are applied immediately after saving and exiting the editor1.
References:
* 1: net-edit - libvirt.

質問 # 30
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. dd if=/dev/zero of=/vms bs=1 count=0 flags=name:vms
• B. libvirt-poolctl new --name=/vms --type=dir --path=/vms
• C. touch /vms/.libvirtpool
• D. virsh pool-create-as vms dir --target /vms
• E. qemu-img pool vms:/vms

正解：D

解説：
Explanation
The command virsh pool-create-as vms dir --target /vms creates and starts a transient storage pool named vms of type dir with the target directory /vms12. This command resolves the issue of the storage pool not found error, as it makes the existing directory /vms visible to libvirt as a storage pool. The other commands are invalid because:
* dd if=/dev/zero of=/vms bs=1 count=0 flags=name:vms is not a valid command syntax. The dd command does not take a flags argument, and the output file /vms should be a regular file, not a directory3.
* libvirt-poolctl new --name=/vms --type=dir --path=/vms is not a valid command name. There is no such command as libvirt-poolctl in the libvirt package4.
* qemu-img pool vms:/vms is not a valid command syntax. The qemu-img command does not have a pool subcommand, and the vms:/vms argument is not a valid image specification5.
* touch /vms/.libvirtpool is not a valid command to create a storage pool. The touch command only creates an empty file, and the .libvirtpool file is not recognized by libvirt as a storage pool configuration file6.
References:
* 1: virsh - difference between pool-define-as and pool-create-as - Stack Overflow
* 2: dd(1) - Linux manual page - man7.org
* 3: 12.3.3. Creating a Directory-based Storage Pool with virsh - Red Hat Customer Portal
* 4: libvirt - Linux Man Pages (3)
* 5: qemu-img(1) - Linux manual page - man7.org
* 6: touch(1) - Linux manual page - man7.org

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

正解：A

解説：
Explanation
Sysprep is a tool that removes all your personal account and security information, and then prepares the machine to be used as an image. It is supported by Windows and some Linux distributions. It can also remove drivers and other machine-specific settings. Sysprep is required when creating a managed image outside of a gallery in Azure
https://learn.microsoft.com/en-us/azure/virtual-machines/generalize

質問 # 32
Which of the following network interface types are valid in an LXD container configuration? (Choose three.)

• A. physical
• B. macvlan
• C. bridged
• D. ipsec
• E. wifi

正解：A、B、C

解説：
Explanation
LXD supports the following network interface types in an LXD container configuration1:
* macvlan: Creates a virtual interface on the host with a unique MAC address and attaches it to an existing physical interface. This allows the container to have direct access to the physical network, but prevents communication with the host and other containers on the same host2.
* bridged: Connects the container to an existing bridge interface on the host. This allows the container to communicate with the host and other containers on the same bridge, as well as the external network if the bridge is connected to a physical interface3.
* physical: Passes an existing physical interface on the host to the container. This allows the container to have exclusive access to the physical network, but removes the interface from the host4.
The other network interface types, ipsec and wifi, are not valid in an LXD container configuration. Ipsec is a protocol for secure communication over IP networks, not a network interface type. Wifi is a wireless technology for connecting devices to a network, not a network interface type. References:
* About networking - Canonical LXD documentation
* Macvlan network - Canonical LXD documentation
* Bridge network - Canonical LXD documentation
* Physical network - Canonical LXD documentation

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

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

正解：C、D

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

質問 # 34
What happens when the following command is executed twice in succession?
docker run -tid -v data:/data debian bash

• A. Each container is equipped with its own independent data volume, available at /data/ in the respective container.
• B. The second command invocation fails with an error stating that the volume data is already associated with a running container.
• C. Both containers share the contents of the data volume, have full permissions to alter its content and mutually see their respective changes.
• D. The container resulting from the second invocation can only read the content of /data/ and cannot change it.
• E. The original content of the container image data is available in both containers, although changes stay local within each container.

正解：C

質問 # 35
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-cp-in -a vm1-snap.img -A vm1.img
• C. virt-delta -a vm1-snap.img -A vm1.img
• D. virt-history -a vm1-snap.img -A vm1.img
• E. virt-cmp -a vm1-snap.img -A vm1.img

正解：A

解説：
Explanation
The virt-diff command-line tool can be used to list the differences between files in two virtual machines or disk images. The output shows the changes to a virtual machine's disk images after it has been running. The command can also be used to show the difference between overlays1. To specify two guests, you have to use the -a or -d option for the first guest, and the -A or -D option for the second guest. For example: virt-diff -a old.img -A new.img1. Therefore, the correct command to list all differences between the disk images vm1-snap.img and vm1.img is: virt-diff -a vm1-snap.img -A vm1.img. The other commands are not related to finding differences between disk images. virt-delta is a tool to create delta disks from two disk images2. virt-cp-in is a tool to copy files and directories into a virtual machine disk image3. virt-cmp is a tool to compare two files or directories in a virtual machine disk image4. virt-history is a tool to show the history of a virtual machine disk image5. References:
* 21.13. virt-diff: Listing the Differences between Virtual Machine Files ...
* 21.14. virt-delta: Creating Delta Disks from Two Disk Images ...
* 21.6. virt-cp-in: Copying Files and Directories into a Virtual Machine Disk Image ...
* 21.7. virt-cmp: Comparing Two Files or Directories in a Virtual Machine Disk Image ...
* 21.8. virt-history: Showing the History of a Virtual Machine Disk Image ...

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

正解：

解説：
lxc-top
Explanation
LXD supports the following network interface types for containers: macvlan, bridged, physical, sriov, and ovn1. Macvlan creates a virtual interface on the host that is connected to the same network as the parent interface2. Bridged connects the container to a network bridge that acts as a virtual switch3. Physical attaches the container to a physical network interface on the host2. Ipsec and wifi are not valid network interface types for LXD containers. References:
* 1: Bridge network - Canonical LXD documentation
* 2: How to create a network - Canonical LXD documentation
* 4: LXD containers and networking with static IP - Super User

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

正解：C

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

質問 # 38
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 a clone of another currently running instance that includes all the software, data and state of the original instance.
• B. Each new instance is connected to the installation media of a Linux distribution and provides access to the installer by logging in via SSH.
• C. Each new instance is connected via a VPN with the computer that started the provisioning and tries to PXE boot from that machine.
• D. 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.
• E. 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.

正解：E

質問 # 39
What is true aboutcontainerd?

• A. It is a text file format defining the build process of containers.
• B. It is the initial process run at the start of any Docker container.
• C. It runs in each Docker container and provides DHCP client functionality
• D. It requires the Docker engine and Docker CLI to be installed.
• E. It uses rune to start containers on a container host.

正解：E

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

正解：B

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

• A. namespace
• B. kvm
• C. proc
• D. cgroup
• E. Ixc

正解：B、E

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

質問 # 42
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 --volumes-from datastore --name service debian bash
• B. docker run -v /data --name service debian bash
• C. docker run --share-with datastore --name service debian bash
• D. docker run --volume-backend datastore -v /data --name service debian bash
• E. docker run -v datastore:/data --name service debian bash

正解：A

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

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

正解：C、D

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

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

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

正解：A

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

質問 # 45
Which of the following commands boots a QEMU virtual machine using hardware virtualization extensions?

• A. qvm start -vmx -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
• B. qemu-hw -create -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 -accel kvm -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

正解：D

質問 # 46
......

LPIC-3 Exam 305は、仮想化およびコンテナ化に関連する広範なトピックをカバーしており、仮想化の概念、仮想化の実装と管理、コンテナ化の概念、コンテナ化の実装と管理などが含まれます。この試験は、Linux環境での仮想化およびコンテナ化技術の計画、展開、管理、トラブルシューティング能力を評価することを目的としています。

 

無料305-300別格な問題集をダウンロード：https://www.passtest.jp/Lpi/305-300-shiken.html

305-300問題集で2024年最新のLpi試験問題：https://drive.google.com/open?id=1yEymCfthoanqUYtpWCTcFFO-Jh9gz20k