SUSE Certified Linux Administrator 12 Free Sample Questions

The rpm -F (freshen) command updates only packages that are already installed on the system, making it safer for updating existing software without accidentally installing new packages. The rpm -U (upgrade) command will either install a new package if it doesn't exist or upgrade it if already present. Other options like rpm -e (erase), rpm -q (query), and rpm -i (install) perform different functions. Both -F and -U are correct for updating packages, with -F being more conservative. Reference: http://www.rpm.org/max-rpm/rpm.8.html

The rpm -U (upgrade) command installs the package if not present or upgrades it if already installed, making it suitable for package updates. The rpm -F (freshen) command only updates packages that are already installed, making it safer for updating existing software. Other options like rpm -e (erase), rpm -q (query), and rpm -i (install) serve different purposes. Both -U and -F are valid for updating packages, with -U being more flexible. Reference: http://www.rpm.org/max-rpm/rpm.8.html

The correct LVM setup sequence is pvcreate (create physical volumes from disk partitions), vgcreate (create volume group from one or more physical volumes), then lvcreate (create logical volumes within the volume group). This hierarchical order is mandatory because volume groups require existing physical volumes, and logical volumes require an existing volume group. Other sequences would fail because dependencies aren't met - you cannot create a volume group without physical volumes or logical volumes without a volume group. Reference: http://www.thegeekstuff.com/2010/08/how-to-create-lvm/

The finger command displays comprehensive user information including the default shell from /etc/passwd, full name, home directory, login times, and other user details. Commands like w show currently logged-in users and their activity, id displays user and group IDs, and who shows logged-in users, but none of these display the user's default shell information. The finger command specifically reads from system files to provide detailed user account information including shell assignments. Reference: http://linux.about.com/library/cmd/blcmdl1_finger.htm

In SUSE Linux Enterprise Server, wicked is the network configuration framework that replaced traditional network scripts. The command "wicked ifup eth0" is the correct syntax to bring up a network interface using the wicked service. Other options use incorrect syntax - "wicked up", "wicked set", "wicked-up", and "wicked if=" are not valid wicked commands. The wicked framework provides comprehensive network management for SUSE systems with advanced features for complex network configurations. Reference: https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_basicnet_manconf.html

The zypper command is SUSE's package manager, and "zypper -i gvim" (or "zypper install gvim") is the correct syntax to install packages from repositories. The "-i" flag stands for install. "zipper" is not a valid command (misspelling), "zypper gvim" lacks the install action, and "zipper in" combines misspelling with abbreviated syntax.

The mkinitrd command creates an initial RAM filesystem (initramfs) that contains essential drivers, kernel modules, and utilities needed for the kernel to boot and successfully mount the root filesystem. This initial filesystem loads into memory before the main filesystem becomes available and contains critical components like device drivers for storage controllers, filesystem modules, and boot utilities. Without initramfs, the kernel cannot access storage devices or mount the root filesystem during boot. Reference: http://man7.org/linux/man-pages/man8/mkinitrd.8.html

The tar command with flags -czvf creates a compressed archive: -c creates a new archive, -z compresses using gzip, -v shows verbose output, and -f specifies the output filename. This command creates /tmp/backup.tgz containing the /etc/HOSTNAME file. The order of operations is create, compress, and output to the specified file, making it an effective backup solution for individual files or directories with compression for space efficiency. Reference: http://www.computerhope.com/unix/utar.htm

Standard systemd service unit files contain three primary sections: [Unit] defines dependencies, descriptions, and metadata about the service; [Service] specifies the service configuration including execution parameters, restart policies, and service type; and [Install] defines installation behavior for enabling/disabling services and setting targets. These sections provide complete service definition and management capabilities within the systemd framework for service orchestration. Reference: https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files

Standard systemd service unit files contain three primary sections: [Unit] defines dependencies, descriptions, and metadata about the service; [Service] specifies the service configuration including execution parameters, restart policies, and service type; and [Install] defines installation behavior for enabling/disabling services and setting targets. The [Service] section is crucial for defining how the service runs, including ExecStart, ExecStop, Type, and Restart directives. Reference: https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files

Standard systemd service unit files contain three primary sections: [Unit] defines dependencies, descriptions, and metadata about the service; [Service] specifies the service configuration including execution parameters, restart policies, and service type; and [Install] defines installation behavior for enabling/disabling services and setting targets. The [Install] section controls how services are enabled and which targets they belong to, using directives like WantedBy and RequiredBy. Reference: https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files

The zypper lr command lists all registered software repositories in SUSE systems, showing repository names, aliases, URLs, enabled/disabled status, and refresh settings. The "lr" stands for "list repositories" and provides essential information for package management and troubleshooting repository issues. Other commands like "zypper repos", "zypper repositories" are valid aliases, but "repo-list" and "list-repos" are not valid zypper commands. Reference: http://www.thegeekstuff.com/2012/06/zypper-examples/

The zypper removerepo command removes a repository from the system repository list, specified by name, alias, or number. You can also use the short form "zypper rr new" but "removerepo" is the explicit command. This permanently removes the repository configuration, requiring re-addition if needed later. Commands like "zypper delete-repo" or "zypper remove-repository" are not valid zypper syntax. Reference: http://www.thegeekstuff.com/2012/06/zypper-examples/