LPI 305-300 Exam Questions Instant Access

Question 1

Which sub-command of xl changes the media inside a virtual CD-ROM drive of a Xen guest domain?

(Specify ONLY the sub-command without any path or parameters.)

Solution:

block-attach -- or -- xl cd-insert -- or -- cd-eject -- or -- xl cd-eject -- or -- cd-insert -- or -- xl block-attach -- or -- block-detach -- or -- xl block-detach

Determine whether the given solution is correct?

ACorrect

BIncorrect

Answer : B

According to official Xen xl toolstack documentation, the correct sub-commands used to change media in a virtual CD-ROM drive are cd-insert and cd-eject. These commands are specifically designed for inserting or ejecting ISO media from a Xen guest's virtual CD-ROM device.

While commands such as block-attach and block-detach are valid xl sub-commands, they are used for attaching and detaching block devices in general and are not specific to CD-ROM media operations. The provided solution lists multiple commands, including incorrect and unrelated ones, rather than specifying the correct sub-command precisely.

Because the solution does not accurately and exclusively identify the correct xl sub-command, it is considered incorrect. Therefore, the correct determination is B.

Question 2

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.)

Alxctop

Answer : A

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

Question 3

What is the same of the global configuration file for the xl tool stack?

Aetcxenxlconf

Answer : A

The xl toolstack is the modern command-line management interface used for administering the Xen hypervisor, replacing the older xm toolstack. According to official Xen virtualization documentation, the global configuration file for the xl toolstack is /etc/xen/xl.conf.

This configuration file defines default behaviors and policies for the xl management commands. It allows administrators to configure global settings such as default CPU scheduling behavior, memory handling, device model settings, and other operational parameters that affect how virtual machines (domains) are managed on a Xen host. These settings apply system-wide and influence the behavior of all xl commands unless overridden by per-domain configuration files.

The file /etc/xen/xl.conf is read by the xl toolstack at runtime and is part of the standard Xen configuration directory structure. Individual virtual machine definitions are typically stored as separate configuration files in /etc/xen/, but xl.conf serves as the central, global configuration reference.

Virtualization notes emphasize that proper configuration of xl.conf is important for performance tuning, stability, and compliance in Xen-based environments. While many default installations function correctly without modifying this file, enterprise deployments often customize it to align with workload requirements and hardware capabilities.

Therefore, the correct and documented global configuration file for the xl toolstack is /etc/xen/xl.conf.

Question 4

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

AEach container runs its own operating system kernel.

BDifferent containers may use different distributions of the same operating system.

CContainer-based virtualization relies on hardware support from the host system's CPU.

DAll containers run within the operating system kernel of the host system.

ELinux does not support container-based virtualization because of missing kernel APIs.

Answer : B, D

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

1: Containerization (computing) - Wikipedia.

2: What are containers? | Google Cloud.

3: What is Container-Based Virtualization? - StackHowTo.

Question 5

Which of the following commands are needed to establish a private network between two (or more) KVM virtual machines that is not visible to other KVM instances on the same KVM host? (Choose THREE correct answers.)

Aebtables

Bbrctl

Cipconfig

Dtunctl

Eifconfig

Answer : B, D, E

To establish a private, isolated network between KVM virtual machines on the same host, Linux networking tools are used to create and manage virtual network bridges and TAP interfaces. According to KVM and Linux virtualization documentation, the core components required are brctl, tunctl, and ifconfig (or the modern ip command).

The brctl utility is used to create and manage Linux bridge interfaces, which act as virtual switches connecting multiple virtual machines. tunctl is used to create TAP interfaces that allow virtual machines to connect to the bridge. ifconfig is used to bring interfaces up and assign network parameters.

ebtables is not strictly required for creating a private network; it is used for filtering Ethernet frames. ipconfig is a Windows networking command and is not applicable to Linux systems.

Therefore, the correct and documented answers are B, D, and E.

Question 6

Which of the following tasks is performed by Vagrant?

AIt automates the installation of a virtual machine according to a configuration file describing the desired VM

BIt monitors the functionality of a virtual machine and restarts the VM in case of failure

CIt is a programming interface used to create reports from collected performance data

DIt is a hypervisor optimized for embedded ARM systems

EIt migrates virtual machines automatically between host systems

Answer : A

Vagrant is a tool designed to automate the creation and provisioning of development virtual machines using a declarative configuration file called a Vagrantfile. According to virtualization documentation, Vagrant simplifies setting up reproducible environments by automatically installing and configuring virtual machines based on this file.

Vagrant does not perform monitoring, reporting, hypervisor functions, or automatic VM migration. It integrates with providers such as VirtualBox, KVM, and VMware but is not itself a hypervisor.

Therefore, the correct answer is A.

Question 7

In order to determine if a virtualization host offers Intel VT-x support, which CPU flag must be searched for in the file /proc/cpuinfo?

Avmx

Answer : A

Intel VT-x is Intel's hardware-assisted virtualization technology and is required to run hypervisors such as KVM efficiently. According to Linux and KVM documentation, support for Intel VT-x can be verified by checking the CPU flags listed in the /proc/cpuinfo file.

The specific flag that indicates Intel VT-x support is vmx. This flag appears in the flags section for each processor core if VT-x is available and enabled in the system firmware (BIOS or UEFI). The presence of vmx confirms that the CPU supports hardware virtualization extensions required by KVM.

If the flag is absent, virtualization may either be unsupported by the CPU or disabled in the firmware settings. For AMD processors, a different flag (svm) is used.

Virtualization documentation consistently references the vmx flag as the authoritative indicator for Intel VT-x support. Therefore, the correct and documented answer is vmx.

LPIC-3: Virtualization and Containerization - Exam 305, (version 3.0) 305-300 Exam Questions