See the solution below in Explanation.
Explanation:
Solution:
lvcreate -L 1G -n lvbackup vgdata
mkfs.xfs /dev/vgdata/lvbackup
mkdir -p /backup
echo "/dev/vgdata/lvbackup /backup xfs defaults 0 0" > > /etc/fstab
mount -a
df -h /backup
Detailed Explanation:
* lvcreate allocates a new LV from the existing VG.
* mkfs.xfs creates the filesystem.
* /etc/fstab makes the mount persistent across reboot.
* mount -a tests the fstab entry immediately.
* RHEL 10 storage documentation continues to use LVM and XFS as core administration topics. ( Red
Hat Documentation )

See the solution below in Explanation.
Explanation:
Solution:
* Set the hostname:
hostnamectl set-hostname server1.example.com
* Configure the existing connection with a static IP:
nmcli connection modify ens160 ipv4.address 192.168.1.2/24 ipv4.gateway 192.168.1.1 ipv4.dns 1.1.1.1 ipv4.
method manual connection.autoconnect yes
* Bring the connection up:
nmcli connection up ens160
Detailed Explanation:
* hostnamectl is the correct modern command for changing the system hostname.
* nmcli is the correct tool for RHEL 10 network configuration because the old ifcfg style is removed in
RHEL 10, and NetworkManager keyfiles are the supported model.
* ipv4.method manual tells NetworkManager to use static addressing.
* connection.autoconnect yes ensures the profile activates automatically after reboot.
* nmcli connection up ens160 applies the changes immediately.

See the solution below in Explanation.
Explanation:
Solution:
* Reboot the server.
* At the GRUB menu, highlight the kernel entry and press e.
* Find the line starting with linux.
* Append:
systemd.unit=emergency.target
* Press Ctrl+x to boot.
Detailed Explanation:
* This changes the boot target only for the current boot.
* Emergency mode is useful for rescue and maintenance tasks.
* Red Hat's RHEL 10 systemd guidance documents booting with systemd.unit= < name > .target from
GRUB. ( Red Hat Documentation )

Solution:
[root@node1 ~]# yum -y install bzip2
[root@node1 ~]# tar -jcvPf /root/backup.tar.bz2 /usr/local
# Verification
[root@node1 ~]# file /root/backup.tar.bz

Solution:
[root@node1 ~]# grep ng /usr/share/xml/iso-codes/iso_639_3.xml
[root@node1 ~]# grep ng /usr/share/xml/iso-codes/iso_639_3.xml > /root/list
# Verification
[root@node1 ~]# cat /root/list