2025年最新の本日更新された最新の305-300のPDFには305-300テスト限定無料！ [Q10-Q34]

2025年最新の本日更新された最新の305-300のPDFには305-300テスト限定無料！

完全版最新の問題集PDFで最新305-300試験問題と解答

この試験では、合計60の質問で構成されており、これは複数選択と空白の質問の組み合わせです。候補者は試験を完了するのに90分あり、合格スコアは800のうち500分の500です。この試験は、グローバルなピアソンVUEテストセンターで行うことができます。

 

質問 # 10
Which of the following are true regarding the CPU of a QEMU virtual machine? (Choose two.)

• A. QEMU virtual machines support multiple virtual CPUs in order to run SMP systems.
• B. Each QEMU virtual machine can only have one CPU with one core.
• C. QEMU uses the concept of virtual CPUs to map the virtual machines to physical CPUs.
• D. The CPU architecture of a QEMU virtual machine is independent of the host system's architecture.
• E. For each QEMU virtual machine, one dedicated physical CPU core must be reserved.

正解：A、D

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

正解：C

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

正解：B

解説：
Explanation
The option dom0_mem is used to set the initial and maximum memory size of the Domain-0, which is the privileged domain that starts first and manages the unprivileged domains (DomU) in Xen. The option dom0_mem must be specified in the bootloader configuration, such as GRUB or GRUB2, when Xen is booted.
This ensures that the Domain-0 kernel can allocate memory for storing memory metadata and network related parameters based on the boot time amount of memory. If the option dom0_mem is not specified in the bootloader configuration, the Domain-0 will use all the available memory on the host system by default, which may cause performance and security issues. References:
* Managing Xen Dom0s CPU and Memory
* Xen Project Best Practices
* Dom0 Memory - Where It Has Not Gone

質問 # 13
What is the purpose of thekubeletservice in Kubernetes?

• A. Run containers on the worker nodes according to the Kubernetes configuration.
• B. Manage permissions of users when interacting with the Kubernetes API.
• C. Build a container image as specified in a Dockerfile.
• D. Provide a command line interface to manage Kubernetes.
• E. Store and replicate Kubernetes configuration data.

正解：A

質問 # 14
What is true aboutcontainerd?

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

正解：A

解説：
Explanation
Containerd is an industry-standard container runtime that uses Runc (a low-level container runtime) by default, but can be configured to use others as well1. Containerd manages the complete container lifecycle of its host system, from image transfer and storage to containerexecution and supervision1. It supports the standards established by the Open Container Initiative (OCI)1. Containerd does not require the Docker engine and Docker CLI to be installed, as it can be used independently or with other container platforms2. Containerd is not a text file format, nor does it run in each Docker container or provide DHCP client functionality. Containerd is not the initial process run at the start of any Docker container, as that is the role of the container runtime, such as Runc3. References: 1 (search for "containerd"), 2 (search for "Containerd is an open source"), 3 (search for "It uses rune to start containers").

質問 # 15
How does Packer interact with system images?

• A. Packer has to be installed within the target image and is executed during the image's first boot in order to execute preparation tasks.
• B. Packer installs a client within the image which has to be run periodically via cron in order to retrieve the latest template from the Packer server and apply it locally.
• C. Packer downloads and extracts an image in order to make changes to the image's file system, repack the modified image and upload it again.
• D. Packer creates an instance based on a source image, prepares the instance through a network connection and bundles the resulting instance as a new system image.
• E. Packer periodically connects through the network to the Packer daemons of all running Packer images in order to re-apply the whole template to the running instance.

正解：D

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

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

正解：A、C、D

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

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

質問 # 18
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. qemu-img pool vms:/vms
• D. virsh pool-create-as vms dir --target /vms
• E. touch /vms/.libvirtpool

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

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

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

正解：A、C、E

解説：
* Both Vagrant and Docker can share directories from the host file system to a guest. This allows the guest to access files and folders from the host without copying them. Vagrant uses the config.vm.synced_folder option in the Vagrantfile to specify the shared folders1. Docker uses the -v or --volume flag in the docker run command to mount a host directory as a data volume in the container2.
* Both Vagrant and Docker can download required base images. Base images are the starting point for creating a guest environment. Vagrant uses the config.vm.box option in the Vagrantfile to specify the base image to use1. Docker uses the FROM instruction in the Dockerfile to specify the base image to use2. Both Vagrant and Docker can download base images from public repositories or local sources.
* Both Vagrant and Docker can apply changes to a base image. Changes are modifications or additions to the base image that customize the guest environment. Vagrant uses provisioners to run scripts or commands on the guest after it is booted1. Docker uses instructions in the Dockerfile to execute commands on the baseimage and create a new image2. Both Vagrant and Docker can save the changes to a new image or discard them after the guest is destroyed.
* Vagrant and Docker differ in how they start system images. Vagrant starts system images as virtual machines by default, using a provider such as VirtualBox, VMware, or Hyper-V1. Docker starts system images as containers by default, using the native containerization functionality on macOS, Linux, and Windows2. Containers are generally more lightweight and faster than virtual machines, but less secure and flexible. References: 1: Vagrant vs. Docker | Vagrant | HashiCorp Developer 2: Vagrant vs Docker:
Which Is Right for You? (Could Be Both) - Kinsta Web Development Tools

質問 # 20
Which file format is used by libvirt to store configuration data?

• A. Text files containing key/value pairs
• B. INI-style text files
• C. Java-like properties files
• D. SQLite databases
• E. XML files

正解：E

質問 # 21
How does Packer interact with system images?

• A. Packer has to be installed within the target image and is executed during the image's first boot in order to execute preparation tasks.
• B. Packer installs a client within the image which has to be run periodically via cron in order to retrieve the latest template from the Packer server and apply it locally.
• C. Packer downloads and extracts an image in order to make changes to the image's file system, repack the modified image and upload it again.
• D. Packer creates an instance based on a source image, prepares the instance through a network connection and bundles the resulting instance as a new system image.
• E. Packer periodically connects through the network to the Packer daemons of all running Packer images in order to re-apply the whole template to the running instance.

正解：D

解説：
Explanation
Packer is a tool that automates the creation of identical machine images for multiple platforms from a single source configuration. Packer works by creating an instance based on a source image, which is a pre-existing image that serves as a starting point. Packer then connects to the instance through a network connection, such as SSH or WinRM, and runs various commands and scripts to install and configure software within the instance. Packer then shuts down the instance and creates a new system image from it, which can be used to launch new instances. Packer supports many platforms, such as AWS, Azure, VMware, Docker, and others.
Packer does not install any software or run any daemon within the target image, nor does it periodically connect to the running instances to re-apply the template. Packer also does not modify the source image directly, but creates a new image from the modified instance. References:
* Packer by HashiCorp
* HashiCorp Packer - Build Automated Machine Images
* Introduction | Packer | HashiCorp Developer

質問 # 22
How can data be shared between several virtual machines running on the same Linux-based host system?

• A. By attaching the same virtual hard disk to all virtual machines and activating EXT4 sharing extensions on it.
• B. By setting up a ramdisk in one virtual machine and mounting it using its UUID in the other VMs.
• C. By using a network file system or file transfer protocol.
• D. By mounting other virtual machines' file systems from /dev/virt-disks/remote/.
• E. By writing data to the file system since all virtual machines on the same host system use the same file system.

正解：C

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

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

正解：B

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

質問 # 24
After setting up a data container using the following command:
docker create -v /data --name datastore debian /bin/true
how is an additional new container started which shares the/datavolume with the datastore container?

• A. docker run -v /data --name service debian bash
• B. docker run --volume-backend datastore -v /data --name service debian bash
• C. docker run --share-with datastore --name service debian bash
• D. docker run --volumes-from datastore --name service debian bash
• E. docker run -v datastore:/data --name service debian bash

正解：D

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

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

正解：B

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

質問 # 26
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" ]

正解：D、E

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

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

正解：C

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

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

質問 # 29
Which of the following statements are true about sparse images in the context of virtual machine storage?
(Choose two.)

• A. Sparse images are automatically shrunk when files within the image are deleted.
• B. Sparse images may consume an amount of space different from their nominal size.
• C. Sparse images can only be used in conjunction with paravirtualization.
• D. Sparse images allocate backend storage at the first usage of a block.
• E. Sparse images are automatically resized when their maximum capacity is about to be exceeded.

正解：B、D

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

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

正解：D

質問 # 31
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 passes the images to the Swarm master which distributes the images to all other Swarm nodes.
• 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 transfers the image from its local Docker cache to each Swarm node.

正解：D

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

質問 # 32
What is the purpose of the commandvagrant init?

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

正解：E

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

質問 # 33
In an IaaS cloud, what is a common method for provisioning new computing instances with an operating system and software?

• A. 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.
• 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 is connected via a VPN with the computer that started the provisioning and tries to PXE boot from that machine.
• D. 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. Each new instance is connected to the installation media of a Linux distribution and provides access to the installer by logging in via SSH.

正解：D

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

質問 # 34
......

無料305-300試験問題305-300実際の無料試験問題：https://www.goshiken.com/Lpi/305-300-mondaishu.html

無料305-300試験を簡単に100%合格できる試験問題集：https://drive.google.com/open?id=1XC_pXM8bAGsGVqXk5u7WNbXMyvMZyNdS