304-200 Exam Dumps - LPI Level 3 Exam 304

ifconfig

brctl

tunctl

ipconfig

ebtables

KVM

Linux VServer

LXC

OpenVZ

Xen

It supports only Linux as a guest operating system.

It is available for Linux only.

It provides both a graphical user interface and command line tools to administer virtual machines.

It requires dedicated shared storage as it cannot store virtual machine disk images locally on block devices of the virtualization host.

It is a special kernel booted before the first regular operating system.

Clusters with one or two nodes cannot have a quorum and require no quorum configuration.

In a two node cluster, quorum can be determined and handled just as in a cluster with a higher number of nodes.

In a two node cluster the quorum is always held by the node that first started the cluster software.

The default quorum policy in a two node cluster must be set to ignore in order to configure a working cluster.

Load balancers cannot be protected against outages which is why they should always be built on dedicated hardware.

No actions are necessary as a load balancer cannot become a single point of failure.

Two or more load balancers should be deployed as a cascade that passes packets from one to the other.

Two load balancers should be deployed as a failover cluster.

Load balancers are used for performance and scalability reasons only and cannot be used to archive high availability clusters.

It is a web interface used to provide self-service domain provisioning to users with sufficient privileges.

It saves the persistent configuration of all defined Xen domains and restores them when the host system is started.

It manages disk file images on behalf of all virtual machines and provides them as virtual devices to guest domains.

It stores run time information regarding Xen and its domains using hierarchical namespaces shared between domains.

It is a software repository located within the host system used to provide software packages to the guest domains.

By providing a public SSH key to the cloud management system and using the matching private SSH key to log into the instances.

Usually computing instances are accessed through a web frontend and do not allow command line access.

By either telnet or SSH using the credentials of the cloud management system account with administrative privileges.

By using a telnet session with the credentials set and publicized by the creator of the computing instance's system image.

By using a VNC console which does not require authentication when it is invoked via the cloud management system.