304-200 Practice Exam Questions with Answers LPI Level 3 Exam 304 Certification

ocfs2.setprops

ocfs2tool

crm_edit

tunefs.ocfs2

o2cbtool

qcow

dmg

qed

qcow2

raw

The hypervisor may provide fine-grained limits to internal elements of the guest operating system such as the number of processes.

Full virtualization cannot pose any limits to virtual machines and always assigns the host system's resources in a first-come-first-serve manner.

It is up to the virtual machine to use its assigned hardware resources and create, for example, an arbitrary amount of network sockets.

The hypervisor provides each virtual machine with hardware of a defined capacity that limits the resources of the virtual machine.

All processes created within the virtual machines are transparently and equally scheduled in the host system for CPU and I/O usage.

An identity manager used to provide Single-Sign-On for different operating systems.

A driver package used to support 3D printers.

A cluster manager used to handle node access to shared storage.

A combined interface to several virtualization products.

A Linux-based virtualization hypervisor.

More than one container requires access to block devices available in the host system.

Remote access via SSH is required to all containers.

Each container needs to have its own user accounts and user groups.

Administrators of containers must be able to install customized Linux kernels.

Different operating systems are to be used within containers on the same virtualization host.

Full virtualization does not require changes to the guest operating systems.

Full virtualization has no performance impact compared to a non-virtualized bare-metal installation on the same machine.

Full virtualization has a severe performance impact and should not be used in production environments.

Full virtualization may be supported by special CPU extensions that provide better performance.

Full virtualization always requires additional software components and cannot be done using Linux only.

Balancing network connections across several backend servers.

Automatically taking over the services of failed nodes.

Restarting failed services on the backend servers.

Checking the integrity of services on backend servers.

Starting and stopping backend servers as needed.

Uninterruptable Power Supplies, UPS

CPU frequency management tools

Blade Control Devices

Remote Management Services like iLO or DRAC

Local node storage

-1

0

1

FORCE

INFINITY

Regular backups become generally unnecessary as any data loss or corruption is automatically recovered by the high availability cluster.

Regular backups remain vital as they allow restoration of data that was accidentally deleted or corrupted.

Regular backups may be reduced to the cluster configuration and cluster state data as this information is sufficient to recover any state of the cluster, including data, at any time.

Backups should be located only on the local storage of the cluster and should not be backed up in order to prevent bandwidth congestion.

Backup procedures may have to be adapted to the cluster to ensure complete and recoverable backups.

The load balancer of a load balanced cluster fails.

The communication between the cluster nodes is interrupted.

Cluster services are moved between cluster nodes.

More than one node is active in a load balanced cluster.

A cluster node has successfully been fenced.

option reverseproxy

option forwardfor

option clientlog

option exposeclient