LPI 305-300 Practice Exam Questions & Answers

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. Reference:

Docker daemon configuration file - Medium3

Docker daemon configuration overview | Docker Docs4

docker daemon | Docker Docs5

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. Reference:

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

: 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, as they are either not hypervisors or not supported by libvirt. Reference: http://libvirt.org/formatdomain.html

https://libvirt.org/formatcaps.html

Packer is an image automation and building tool developed by HashiCorp. According to virtualization and DevOps documentation, Packer is used to create machine images for multiple platforms from a single configuration file.

Packer is not an orchestration platform, configuration management tool, or hypervisor. Its primary role is to ensure consistent, repeatable, and automated image creation, making B the correct answer.

Container orchestration platforms are responsible for deploying, scaling, networking, and managing containerized applications across multiple hosts. According to containerization documentation, Docker Swarm and Kubernetes are recognized container orchestration platforms.

Docker Swarm is Docker's native orchestration solution, providing clustering, service discovery, load balancing, and rolling updates. Kubernetes is the industry-standard orchestration platform, offering advanced scheduling, self-healing, horizontal scaling, and declarative configuration.

Docker Compose is not considered a full orchestration platform; it is primarily designed for defining and running multi-container applications on a single host, mainly for development and testing. LXC is a container runtime and system container technology, not an orchestration framework.

Container documentation clearly distinguishes orchestration platforms from runtimes and local development tools. Therefore, the correct answers are B and D.

Kernel-based Virtual Machine (KVM) relies on hardware-assisted virtualization features provided by modern CPUs. On Intel CPU architectures, this support is enabled through the kvm_intel kernel module. Official KVM and Linux virtualization documentation clearly states that the required module for Intel processors is named kvm_intel, with the optional .ko suffix when referring to the kernel object file.

The provided solution lists multiple acceptable representations of the module name, including kvm_intel and kvm_intel.ko, both of which are valid and correct. Linux kernel module naming conventions allow the module to be referenced with or without the .ko suffix when loading it using tools such as modprobe or lsmod.

Although variants using a hyphen (kvm-intel) are not the canonical kernel module name, the solution explicitly includes the correct and documented module name. Therefore, the solution correctly identifies the required kernel module for enabling KVM on Intel CPUs.

Virtualization documentation emphasizes that KVM functionality requires both the generic kvm module and the CPU-specific module (kvm_intel for Intel or kvm_amd for AMD). Hence, the determination that the solution is correct aligns with verified documentation.

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. Reference:

Oracle VM VirtualBox: Features Overview