Solution:
# Connect to servera via console for IP modification, then check using the ip addr command.
# After confirming no issues, SSH to servera for hostname modification. This way, you can copy the hostname to avoid typos.
[root@clear ~] nmcli con show
[root@clear ~] nmcli con mod 'network configuration name' ipv4.method manual ipv4.addresses 172.25.0.25/24 ipv4.gateway 172.25.0.254 ipv4.dns 172.25.0.254
autoconnect yes
[root@clear ~] nmcli con up 'network configuration name'
[root@clear ~] ip a
[root@clear ~] ssh [email protected]
[root@clear ~] hostnamectl set-hostname red.lab0.example.com
# Verification
[root@node1 ~] ip a //Check if the IP is correct
[root@node1 ~] hostname //Check if the hostname is correct

See the solution below in Explanation.
Explanation:
Solution:
pvcreate /dev/sdb3
vgcreate -s 16M VG1 /dev/sdb3
lvcreate -l 30 -n LV1 VG1
mkfs.ext4 /dev/VG1/LV1
Detailed Explanation:
* vgcreate -s 16M sets PE size to 16 MB.
* lvcreate -l 30 allocates 30 extents.
* 30 x 16 MB = 480 MB total LV size.
* mkfs.ext4 creates the filesystem.

See the solution below in Explanation.
Explanation:
Solution:
dd if=/dev/zero of=/swapfile bs=1M count=512
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
echo "/swapfile swap swap defaults 0 0" > > /etc/fstab
swapon --show
Detailed Explanation:
* dd creates the file.
* chmod 600 protects swap contents.
* mkswap prepares the file as swap.
* swapon activates it now.
* /etc/fstab ensures it is enabled at boot.

See the solution below in Explanation.
Explanation:
Solution:
subscription-manager config --rhsm.manage_repos=0
Detailed Explanation:
* This disables repository management by Subscription Manager, exactly as shown in the lab dataset.
* Use this when a task wants system repositories disabled so custom repos can be managed manually.

See the solution below in Explanation.
Explanation:
Solution:
* Reboot the system.
* Interrupt GRUB boot.
* Press e to edit the boot entry.
* On the linux line, append:
rd.break
* Boot with Ctrl+x.
* At the emergency shell:
mount -o remount,rw /sysroot
chroot /sysroot
passwd root
touch /.autorelabel
exit
exit
Detailed Explanation:
* rd.break drops you into an early emergency environment.
* /sysroot contains the real root filesystem.
* mount -o remount,rw /sysroot makes it writable.
* chroot /sysroot changes into the installed system.
* passwd root resets the password.
* touch /.autorelabel is critical so SELinux relabels files on next boot.