• ホーム
  • ブログ
  • 実践サンプルと問題集と指導には2024年最新の305-300有効なテスト問題集 [Q37-Q60]

実践サンプルと問題集と指導には2024年最新の305-300有効なテスト問題集 [Q37-Q60]

Share

実践サンプルと問題集と指導には2024年最新の305-300有効なテスト問題集

最新 [2024年08月23日] 100%合格率保証付きの素晴らしい305-300試験問題PDF

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

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

正解：A、B、D

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


質問 # 38
Which of the following statements are true about container-based virtualization? (Choose two.)

  • A. Each container runs its own operating system kernel.
  • B. All containers run within the operating system kernel of the host system.
  • C. Container-based virtualization relies on hardware support from the host system's CPU.
  • D. Different containers may use different distributions of the same operating system.
  • E. Linux does not support container-based virtualization because of missing kernel APIs.

正解：B、D

解説：
Explanation
Container-based virtualization is a method of operating system-level virtualization that allows multiple isolated user spaces (containers) to run on the same host system1. Each container shares the same operating system kernel as the host, but has its own file system, libraries, and processes2. Therefore, the statements A and C are false, as containers do not run their own kernels or rely on hardware support from the CPU. The statement E is also false, as Linux does support container-based virtualization through various technologies, such as cgroups, namespaces, LXC, Docker, etc12. The statement B is true, as different containers may use different distributions of the same operating system, such as Debian, Ubuntu, Fedora, etc., as long as they are compatible with the host kernel3. The statement D is also true, as all containers run within the operating system kernel of the host system, which provides isolation and resource management for them12. References:
* 1: Containerization (computing) - Wikipedia.
* 2: What are containers? | Google Cloud.
* 3: What is Container-Based Virtualization? - StackHowTo.


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

正解：E

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


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


質問 # 41
Which of the following mechanisms are used by LXC and Docker to create containers? (Choose three.)

  • A. Kernel Namespaces
  • B. Control Groups
  • C. Linux Capabilities
  • D. POSIXACLs
  • E. File System Permissions

正解：A、B、C

解説：
Explanation
LXC and Docker are both container technologies that use Linux kernel features to create isolated environments for running applications. The main mechanisms that they use are:
* Linux Capabilities: These are a set of privileges that can be assigned to processes to limit their access to certain system resources or operations. For example, a process with the CAP_NET_ADMIN capability can perform network administration tasks, such as creating or deleting network interfaces. Linux
* capabilities allow containers to run with reduced privileges, enhancing their security and isolation.
* Kernel Namespaces: These are a way of creating separate views of the system resources for different processes. For example, a process in a mount namespace can have a different file system layout than the host or other namespaces. Kernel namespaces allow containers to have their own network interfaces, process IDs, user IDs, and other resources, without interfering with the host or other containers.
* Control Groups: These are a way of grouping processes and applying resource limits and accounting to them. For example, a control group can limit the amount of CPU, memory, disk I/O, or network bandwidth that a process or a group of processes can use. Control groups allow containers to have a fair share of the system resources and prevent them from exhausting the host resources.
POSIX ACLs and file system permissions are not mechanisms used by LXC and Docker to create containers.
They are methods of controlling the access to files and directories on a file system, which can be applied to any process, not just containers.
References:
* LXC vs Docker: Which Container Platform Is Right for You?
* LXC vs Docker: Why Docker is Better in 2023 | UpGuard
* What is the Difference Between LXC, LXD and Docker Containers
* lxc - Which container implementation docker is using - Unix & Linux Stack Exchange


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

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

正解：B


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

  • A. 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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. Packer has to be installed within the target image and is executed during the image's first boot in order to execute preparation tasks.

正解：C


質問 # 44
Which of the following values would be valid in the FROM statement in aDockerfile?

  • A. ubuntu:focal
  • B. registry:ubuntu:focal
  • C. http://docker.example.com/images/ubuntu-focal.iso
  • D. docker://ubuntu: focal
  • E. file:/tmp/ubuntu/Dockerfile

正解：A

解説：
Explanation
The FROM statement in a Dockerfile specifies the base image from which the subsequent instructions are executed1. The value of the FROM statement can be either an image name, an image name with a tag, or an image ID1. The image name can be either a repository name or a repository name with a registry prefix2. For example, ubuntu is a repository name, and docker.io/ubuntu is a repository name with a registry prefix2. The tag is an optional identifier that can be used to specify a particular version or variant of an image1. For example, ubuntu:focal refers to the image with the focal tag in the ubuntu repository2. The image ID is a unique identifier that is automatically generated when an image is built or pulled1. For example, sha256:9b0dafaadb1cd1d14e4db51bd0f4c0d56b6b551b2982b2b7c637ca143ad605d2 is an image ID3.
Therefore, the only valid value in the FROM statement among the given options is ubuntu:focal, which is an image name with a tag. The other options are invalid because:
* docker://ubuntu:focal is not a valid image name format. The docker:// prefix is used to specify a transport protocol, not a registry prefix4.
* registry:ubuntu:focal is not a valid image name format. The registry prefix should be a valid hostname or IP address, not a generic term2.
* file:/tmp/ubuntu/Dockerfile is not a valid image name format. The file: prefix is used to specify a local file path, not an image name5.
* http://docker.example.com/images/ubuntu-focal.iso
is not a valid image name format.
The
http:// prefix is used to specify a web URL, not an image name
5.
References:
* 1: Dockerfile reference | Docker Docs
* 2: docker - Using FROM statement in dockerfile - Stack Overflow
* 3: How to get the image id from a docker image - Stack Overflow
* 4: skopeo - Docker Registry v2 API tool - Linux Man Pages (1)
* 5: How to build a Docker image from a local Dockerfile? - Stack Overflow


質問 # 45
Which of the following statements are true regarding a Pod in Kubernetes? (Choose two.)

  • A. A Pod is the smallest unit of workload Kubernetes can run.
  • B. Pods are always created automatically and cannot be explicitly configured.
  • C. When a Pod fails, Kubernetes restarts the Pod on another node by default.
  • D. systemd is used to manage individual Pods on the Kubernetes nodes.
  • E. All containers of a Pod run on the same node.

正解：A、E

解説：
Explanation
A Pod in Kubernetes is a collection of one or more containers that share the same network and storage resources, and a specification for how to run the containers. A Pod is the smallest unit of workload Kubernetes can run, meaning that it cannot be divided into smaller units. Therefore, option C is correct. All containers of a Pod run on the same node, which is the smallest unit of computing hardware in Kubernetes. A node is a physical or virtual machine that hosts one or more Pods. Therefore, option A is also correct. Pods are not always created automatically and cannot be explicitly configured. Pods can be created manually using YAML or JSON files, or using commands like kubectl run or kubectl create. Pods can also be created automatically by higher-level controllers, such as Deployment, ReplicaSet, or StatefulSet. Therefore, option B is incorrect.
When a Pod fails, Kubernetes does not restart the Pod on another node by default. Pods are ephemeral by nature, meaning that they can be terminated or deleted at any time. If a Pod is managed by a controller, the controller will create a new Pod to replace the failed one, but it may not be on the same node. Therefore, option D is incorrect. systemd is not used to manage individual Pods on the Kubernetes nodes. systemd is a system and service manager for Linux operating systems that can start and stop services, such as docker or kubelet. However, systemd does not interact with Podsdirectly. Pods are managed by the kubelet service, which is an agent that runs on each node and communicates with the Kubernetes control plane. Therefore, option E is incorrect. References:
* Pods | Kubernetes
* What is a Kubernetes pod? - Red Hat
* What's the difference between a pod, a cluster, and a container?
* What are Kubernetes Pods? | VMware Glossary
* Kubernetes Node Vs. Pod Vs.Cluster: Key Differences - CloudZero


質問 # 46
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. qvirt -create -drive file=debian.img -cdrom debian.iso -m 1024 -boot d -driver hvm
  • D. vm -kvm -drive file=debian.img -cdrom debian.iso -m 1024 -boot d
  • E. qemu -accel kvm -drive file-debian.img -cdrom debian.iso -m 1024 -boot d

正解：E

解説：
Explanation
The correct command to boot a QEMU virtual machine using hardware virtualization extensions is qemu
-accel kvm -drive file-debian.img -cdrom debian.iso -m 1024 -boot d. This command uses the -accel option to specify the hardware accelerator to use, which in this case is kvm. KVM is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V)1. The -drive option specifies the disk image file to use, which in this case is debian.img. The -cdrom option specifies the ISO image file to use as a CD-ROM, which in this case is debian.iso. The -m option specifies the amount of memory to allocate to the virtualmachine, which in this case is 1024 MB. The -boot option specifies the boot order, which in this case is d, meaning to boot from the CD-ROM first. References:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_
https://fedoraproject.org/wiki/Virtualization


質問 # 47
Which of the following types of guest systems does Xen support? (Choose two.)

  • A. Paravirtualized quests (PVI
  • B. Emulated guests
  • C. Container virtualized guests
  • D. Fully virtualized guests
  • E. Foreign architecture guests (FA)

正解：A、D

解説：
Explanation
Xen supports two types of guest systems: paravirtualized guests (PV) and fully virtualized guests (HVM).
* Paravirtualized guests (PV) are guests that have been modified to run on the Xen hypervisor. They use a special kernel that communicates with the hypervisor through hypercalls, and use paravirtualized drivers
* for I/O devices. PV guests can run faster and more efficiently than HVM guests, but they require the guest operating system to be ported to Xen and to support the Xen ABI12.
* Fully virtualized guests (HVM) are guests that run unmodified operating systems on the Xen hypervisor.
They use hardware virtualization extensions, such as Intel VT-x or AMD-V, to create a virtual platform for the guest. HVM guests can run any operating system that supports the hardware architecture, but they incur more overhead and performance penalties than PV guests. HVM guests can also use paravirtualized drivers for I/O devices to improve their performance12.
The other options are not correct. Xen does not support foreign architecture guests (FA), emulated guests, or container virtualized guests.
* Foreign architecture guests (FA) are guests that run on a different hardware architecture than the host.
For example, running an ARM guest on an x86 host. Xen does not support this type of virtualization, as it would require emulation or binary translation, which are very complex and slow techniques3.
* Emulated guests are guests that run on a software emulator that mimics the hardware of the host or another platform. For example, running a Windows guest on a QEMU emulator. Xen does not support this type of virtualization, as it relies on the emulator to provide the virtual platform, not the hypervisor. Xen can use QEMU to emulate some devices for HVM guests, but not the entire platform14.
* Container virtualized guests are guests that run on a shared kernel with the host and other guests, using namespaces and cgroups to isolate them. For example, running a Linux guest on a Docker container. Xen does not support this type of virtualization, as it requires the guest operating system to be compatible with the host kernel, and does not provide the same level of isolation and security as hypervisor-based virtualization56.
References:
* Xen Project Software Overview - Xen
* Xen ARM with Virtualization Extensions - Xen
* Xen Project Beginners Guide - Xen
* QEMU - Xen
* Docker overview | Docker Documentation
* What is a Container? | App Containerization | VMware


質問 # 48
What is the purpose of a .dockerignore file?

  • A. It specifies files that Docker does not submit to the Docker daemon when building a Docker image
  • B. It specifies which parts of a Dockerfile should be ignored when building a Docker image.
  • C. It exists in the root file system of containers that should ignore volumes and ports provided by Docker.
  • D. It must be placed in the top level directory of volumes that Docker should never attach automatically to a container
  • E. It lists files existing in a Docker image which should be excluded when building a derivative image.

正解：A


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

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

正解：B、C、E


質問 # 50
Which of the following values would be valid in the FROM statement in aDockerfile?

  • A. ubuntu:focal
  • B. registry:ubuntu:focal
  • C. http://docker.example.com/images/ubuntu-focal.iso
  • D. docker://ubuntu: focal
  • E. file:/tmp/ubuntu/Dockerfile

正解：A


質問 # 51
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 contains a minimal live system running from a virtual CD as the basis from which the administrator deploys the target operating system.
  • 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 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 a clone of another currently running instance that includes all the software, data and state of the original instance.

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


質問 # 52
Which of the following commands lists all differences between the disk images vm1-snap.img and vm1.img?

  • A. virt-cmp -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-diff -a vm1-snap.img -A vm1.img
  • E. virt-history -a vm1-snap.img -A vm1.img

正解：D

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


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


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


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

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

正解：A、C、E

解説：
Explanation
LXC (Linux Containers) is a lightweight virtualization technology that allows multiple isolated Linux systems (containers) to run on the same host. LXC uses Linux kernel features such as namespaces, cgroups, and AppArmor to create and manage containers. Each container has its own file system, network interfaces, process tree, and resource limits. However, containers share the same kernel and hardware with the host, which makes them more efficient and faster than full virtualization.
By default, an LXC container has a minimal set of devices that are needed for its operation. These devices are created by the LXC library when the container is started, and are removed when the container is stopped. The default devices are:
* /dev/log: This is a Unix domain socket that connects to the syslog daemon on the host. It allows the container to send log messages to the host's system log1.
* /dev/console: This is a character device that provides access to the container's console. It is usually connected to the host's terminal or a file. It allows the container to interact with the user or the host's init system12.
* /dev/urandom: This is a character device that provides an unlimited source of pseudo-random numbers. It is used by various applications and libraries that need randomness, such as cryptography, UUID generation, and hashing13.
The other devices listed in the question do not exist by default in an LXC container. They are either not needed, not allowed, or not supported by the container's namespace or cgroup configuration. These devices are:
* /dev/kmem: This is a character device that provides access to the kernel's virtual memory. It is not needed by the container, as it can access its own memory through the /proc filesystem. It isalso not allowed by the container, as it would expose the host's kernel memory and compromise its security4.
* /dev/root: This is a symbolic link that points to the root device of the system. It is not supported by the container, as it does not have a separate root device from the host. The container's root file system is mounted from a directory, an image file, or a loop device on the host5.
References:
* Linux Containers - LXC - Manpages - lxc.container.conf.5
* Linux Containers - LXC - Getting started
* Random number generation - Wikipedia
* /dev/kmem - Wikipedia
* Linux Containers - LXC - Manpages - lxc.container.conf.5


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

正解：C

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


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

正解：C


質問 # 58
Which of the following mechanisms are used by LXC and Docker to create containers? (Choose three.)

  • A. Kernel Namespaces
  • B. Control Groups
  • C. Linux Capabilities
  • D. POSIXACLs
  • E. File System Permissions

正解：A、B、C


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

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

正解：B、C、E

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


質問 # 60
......

305-300時間限定！無料アクセス：https://www.passtest.jp/Lpi/305-300-shiken.html

305-300認定有効な試験問題集と解答学習ガイド：https://drive.google.com/open?id=13U1fx5R--GOBRfdwt1-w54K7uikCfUHC

関するブログ

もっと
305-300 無料問題集