For programs to leverage PolKit they are split into two separate processes. The statements below that are true regarding these two PolKit processes are:

The Mechanism process runs in the System Context.

The Policy Agent process runs in the User Session.

The Mechanism process is responsible for performing privileged actions on behalf of unprivileged users. It runs as root in the System Context and communicates with PolKit via D-Bus. The Policy Agent process is responsible for requesting authorization from users when they attempt to perform privileged actions. It runs as a normal user in the User Session and communicates with PolKit via D-Bus. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-polkit.html#sec-polkit-processes

If you are setting up a SLES 15 server that will require very large data volumes and journaling capabilities, the best choice for your data volumes is XFS. XFS is a high-performance and scalable file system that supports large files and file systems, online defragmentation and resizing, metadata checksums, and other features. XFS also provides journaling capabilities that ensure data consistency and integrity in case of system crashes or power failures. XFS is the default file system for data partitions in SLES 15. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-filesystems.html#sec-filesystems-xfs

Subvolumes in BtrFS are like virtual filesystems that can be mounted separately with the -o subvol= option. They can also have different attributes and quotas. Subvolumes do not have to start with “@” character, although some default subvolumes use this convention. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-btrfs.html#sec-btrfs-subvolumes

The file that contains information about secondary groups on the system is /etc/group. This file defines the group names, group IDs, group passwords, and group members for each group on the system. The primary group information for each user is stored in /etc/passwd file. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-user-group.html#sec-user-group-files

The term “action” means an action that defines where a log message ends up such as in a regular file or database table when referring to system logging in SUSE Linux Enterprise. An action is part of a rule that specifies how to process a log message based on its properties. An action can be one of the following types: file, pipe, shell, template, discard, stop, call, omusrmsg, ommysql, ompgsql, etc. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-syslog.html#sec-syslog-config-actions

The file that contains the list of DNS servers SLES will contact is /etc/resolv.conf. This file specifies one or more nameserver addresses that will be used to resolve hostnames to IP addresses. It may also contain other options such as search domains, sort lists, etc. The /etc/resolv.conf file can be generated automatically by network configuration tools or edited manually by the administrator. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-network-dns.html#sec-network-dns-resolv.conf

The file that contains the ntp configuration is /etc/ntp.conf. This file specifies the ntp server or peer addresses, synchronization options, access restrictions, logging settings, and other parameters for the ntp daemon (ntpd) that provides time synchronization services on a Linux system. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-ntp-config.html

The command that is used to manage software RAID is mdadm. This command can be used to create, assemble, monitor, and manage multiple device (md) arrays that provide RAID functionality. It can also be used to query and modify various parameters and settings of md arrays. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-raid.html#sec-raid-mdadm

When using the nice command, -15 is the higher priority than 7. The nice command can be used to run a process with a modified scheduling priority. The priority value ranges from -20 (highest priority) to 19 (lowest priority). The default priority is 0. Only root can assign negative priority values to processes. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-cli-nice.html

The command that you would use to set an Extended ACL so that the jsmith user has all permissions to just the tstparse.sh file in your scripts subdirectory under your home directory is setfacl -m u:jsmith:rwx ~/scripts/tstparse.sh. This command will modify (or create if it does not exist) the Extended ACL for the specified file and add an entry for the jsmith user with read, write, and execute permissions. You can use getfacl ~/scripts/tstparse.sh to view the Extended ACL for the file. References: https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-acl.html#sec-acl-set