304-200 Sample Questions & Answers

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.

It restores a virtual machine from a state file.

It reverts a virtual machine, including its storage devices, to a previously saved state.

It wakes up a virtual machine that was hibernated by the operating system running inside the virtual machine.

It restores a virtual machine that was stopped by a kernel panic.

By mounting other VM's file systems from /dev/virt-disks/remote/.

By using a network file system or file transfer protocol.

By default, Linux-based virtualization products provide full access to the host system to all virtual machines.

By setting up a ramdisk in one virtual machine and mounting it using its UUID in the other VMs.

By attaching the same virtual hard disk to all virtual machines and activating EXT4 sharing extensions on it.

Creation of new instances can be automated by using scripts or APIs and service interfaces.

The root file system of a computing instance is always persistent and can be accessed after the instance is destroyed.

Each and every user of an laaS cloud has exactly one computing instance.

Once created, computing instances are seldom deleted in order to ensure the accessibility of the instance's data.

Instances may be created when needed and destroyed when they become obsolete.

The addresses of backend servers thatwere overloaded in the past and should be scheduled with a reduced priority.

The hostnames of the servers that, despite the remaining configuration, should always be scheduled by the Serial Operation Round Robin algorithm.

The addresses of backend servers that should not get assigned any new connections.

The defaultvirtual hostthat is assigned to incoming HTTP requests missing a Host: header before forwarding them to a backend server.

The address of a server to which requests are redirected in case no real server is available.

/etc/ocfs2cIuster.conf

/etc/ocfs2.conf

/etc/cluster.conf

/etc/ocfs/cIuster.conf