Explanation
Firewalld uses two separated configuration sets, runtime, and permanent configuration.
The runtime configuration is the actual running configuration and it is not persistent on reboots. When the firewalld service starts it loads the permanent configuration which becomes the runtime configuration.
https://www.supportsages.com/everything-you-need-to-know-about-firewalld/#:~:text=Firewalld%20uses%20tw Firewalld maintains two separate configurations: runtime and permanent. The runtime configuration is the current state of the firewall that is applied to the system. It can be changed by various commands and tools without affecting the permanent configuration. The permanent configuration is the persistent state of the firewall that is stored in configuration files. It can be changed by various commands and tools with the
--permanent option. The permanent configuration will take effect after reloading firewalld or rebooting the system.
References:https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-firewall-firewalld.html#sec-firewall-

Explanation
By default, the VNC Client and the VNC server daemon use a self-signed SSL certificate for secure communications. The VNC server generates a self-signed certificate when it is started for the first time. The VNC Client will prompt the user to accept or reject the certificate when connecting to the server.
Alternatively, the user can provide a custom certificate for the VNC server or disable encryption if desired.
References:https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-vnc-security.html

Explanation
You can view manual pages by running the man command followed by a specific command name. If the man command is not installed on your system, install it by runningzypper install man.
https://documentation.suse.com/sles/15-GA/html/SLES-all/pre-sle.html
The command that is used to view the manual pages is man. The man command will display the formatted documentation for a given command, function, or file. The manual pages are organized into sections based on their type and purpose. The user can specify the section number and the name of the item to view its manual page.
References:https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-cli-help.html#sec-cli-help-man

Explanation
The configuration files that have a format that is compatible with the system logging facility in SUSE Linux Enterprise are /etc/syslog.conf and /etc/rsyslog.conf. These files contain rules that specify how to filter and process log messages from different sources and destinations. The /etc/syslog.conf file is used by the traditional syslogd daemon, while the /etc/rsyslog.conf file is used by the more advanced rsyslogd daemon.
SUSE Linux Enterprise uses rsyslogd by default, but it can also read /etc/syslog.conf for backward compatibility.
References:https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-syslog.html#sec-syslog-config

Explanation
To add additional physical volumes to an existing volume group, use the vgextend command. The vgextend command increases a volume group's capacity by adding one or more free physical volumes.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/4/html/cluster_logical_volume_manage The command that is used to add new physical volumes to an existing volume group is vgextend. This command will extend a volume group by adding one or more physical volumes to it. The physical volumes must be initialized with pvcreate before they can be added to a volume group.
References:https://documentation.suse.com/sles/15-SP3/html/SLES-all/sec-lvm-vgs.html#sec-lvm-vgs-add-pv