050-733 Sample Questions & Answers

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/

The newgrp command temporarily switches the user's primary group without logging out, creating a new shell session with the specified group as the primary group. This affects file creation permissions and group ownership for new files. The command requires the user to be a member of the target group. Commands like "chgrp" change file group ownership, "usermod" modifies user account properties, but only "newgrp" changes the active primary group. Reference: http://man7.org/linux/man-pages/man1/newgrp.1.html

Symbolic links can point to files on different filesystems, unlike hard links which must reside on the same filesystem due to inode limitations. Symbolic links store the path to the target file as text, making cross-filesystem linking possible. Hard links share the same inode number and must be on the same filesystem, while symbolic links are separate files containing path information. Reference: http://www.cyberciti.biz/tips/understanding-unixlinux-symbolic-soft-and-hard-links.html

If the original file is deleted, the symbolic link becomes a "dangling" or "broken" link pointing to a non-existing file, resulting in errors when accessed. Unlike hard links which maintain file data even when the original filename is deleted, symbolic links only store path information. The symbolic link file itself remains but points to nothing, making it unusable until the target is recreated or the link is updated. Reference: http://www.cyberciti.biz/tips/understanding-unixlinux-symbolic-soft-and-hard-links.html

SUSE Linux Enterprise Server 12 supports multiple authentication methods including NIS (Network Information Service) for centralized user management across Unix/Linux networks, PAM (Pluggable Authentication Modules) for flexible authentication frameworks, LDAP for directory-based authentication, and Windows Domain integration for Active Directory environments. NIS provides centralized user account management but is considered less secure than LDAP for modern environments. Reference: https://www.suse.com/documentation/sles-12/book_sle_admin/data/cha_nis.html

SUSE Linux Enterprise Server 12 supports PAM (Pluggable Authentication Modules) which provides a flexible framework for authentication, authorization, session management, and password policies. PAM allows different authentication methods to be configured without modifying applications. Other supported methods include NIS for network user management, LDAP for directory services, and Windows Domain integration for Active Directory authentication in mixed environments. Reference: https://www.suse.com/documentation/sles-12/book_sle_admin/data/part_auth.html

SUSE Linux Enterprise Server 12 supports LDAP (Lightweight Directory Access Protocol) authentication for centralized user management using directory services like OpenLDAP or Active Directory. LDAP provides secure, scalable authentication with advanced features like group management, access controls, and encrypted communications. Other supported methods include NIS, PAM frameworks, and Windows Domain integration for comprehensive authentication solutions. Reference: https://www.suse.com/documentation/sles-12/book_sle_admin/data/cha_ldap.html

SUSE Linux Enterprise Server 12 supports Windows Domain authentication through Samba and Winbind integration, allowing Linux systems to join Active Directory domains and authenticate users against Windows domain controllers. This enables seamless integration in mixed Windows/Linux environments with centralized user management. Other supported methods include NIS for Unix environments, PAM for flexible authentication, and LDAP for directory-based authentication. Reference: https://www.suse.com/documentation/sles-12/book_sle_admin/data/cha_winbind.html

The ip addr add command with CIDR notation "192.168.0.10/24" automatically calculates network and broadcast addresses for the interface. The "/24" specifies the subnet mask (255.255.255.0), "dev eth0" specifies the network device, and "brd +" automatically sets the broadcast address based on the network. This modern ip command replaces older ifconfig for network configuration with more precise control and better IPv6 support. Reference: http://man7.org/linux/man-pages/man8/ip.8.html

The pwd (print working directory) command displays the complete absolute path of the current directory you are working in, essential for navigation and understanding your location within the filesystem hierarchy. This command shows the full path from the root directory to your current location. Commands like "ls" list directory contents, "cd" changes directories, and "dir" (not standard on Linux) lists contents, but only "pwd" shows your current location path. Reference: http://man7.org/linux/man-pages/man1/pwd.1.html