Correct Answer:

Solution:
# Install and enable tuned
[root@node2 ~]# yum -y install tuned
[root@node2 ~]# systemctl enable tuned
[root@node2 ~]# systemctl restart tuned
# Check the recommended configuration scheme for the system
[root@node2 ~]# tuned-adm recommend
virtual-guest
# Switch to the specified configuration scheme
[root@node2 ~]# tuned-adm profile virtual-guest
# Check the current configuration scheme
[root@node2 ~]# tuned-adm active
Current active profile: virtual-guest

Correct Answer:

See the solution below in Explanation.
Explanation:
Solution:
Create the Quadlet file:
mkdir -p /etc/containers/systemd
cat > /etc/containers/systemd/sleepy.container < < 'EOF'
[Container]
Image=registry.access.redhat.com/ubi10/ubi
ContainerName=sleepy
Exec=sleep 3600
[Install]
WantedBy=multi-user.target
EOF
Reload and enable:
systemctl daemon-reload
systemctl enable --now sleepy.service
systemctl status sleepy.service
Detailed Explanation:
* Quadlet is the preferred modern way to manage Podman containers with systemd for new configurations.
* The .container file is translated into a systemd-managed service.
* RHEL 10 documentation notes that podman generate systemd still exists, but Quadlets are preferred for new setups. ( Red Hat Documentation )

Correct Answer:

See the solution below in Explanation.
Explanation:
Solution:
lvextend -L +500M /dev/vgdata/lvbackup
xfs_growfs /backup
df -h /backup
Detailed Explanation:
* lvextend increases the LV size.
* xfs_growfs expands the XFS filesystem while mounted.
* This is a classic RHCSA storage task and aligns with RHEL 10 LVM/XFS workflows. ( Red Hat
Documentation )

Correct Answer:

Solution:
# Note: Perform the following operations by SSHing into localhost as the user "wallah"
[root@node1 ~]# ssh wallah@localhost
# Prepare the relevant mapping directories
[wallah@node1 ~]$ sudo mkdir /opt/{file,progress}
[wallah@node1 ~]$ sudo chown wallah:wallah /opt/{file,progress}
# Start the container and map directories
# :Z changes the SELinux security context of the directory to allow container access.
[wallah@node1 ~]$ podman run -d --name ascii2pdf -v /opt/file:/dir1:Z -v /opt/progress:/dir2:Z pdf
[wallah@node1 ~]$ podman ps -a
# Create systemd service file
[wallah@node1 ~]$ mkdir -p ~/.config/systemd/user
[wallah@node1 ~]$ cd ~/.config/systemd/user/
[wallah@node1 ~]$ podman generate systemd -n ascii2pdf -f --new
[wallah@node1 user]$ ll
total 4
-rw-r--r--. 1 wallah wallah 770 Dec 13 01:07 container-ascii2pdf.service
# Stop and remove the existing ascii2pdf container
[wallah@node1 ~]$ podman stop ascii2pdf
[wallah@node1 ~]$ podman rm ascii2pdf
[wallah@node1 ~]$ podman ps -a
# Enable and start the container-ascii2pdf service
[wallah@node1 ~]$ systemctl --user daemon-reload
[wallah@node1 ~]$ systemctl --user enable --now container-ascii2pdf
# Check container status
[wallah@node1 ~]$ systemctl --user status container-ascii2pdf
[wallah@node1 ~]$ podman ps
# On node1, switch to the root user to perform the following operations
# Ensure that the services for the wallah user start automatically at system boot
[root@node1 ~]# loginctl enable-linger
[root@node1 ~]# loginctl show-user wallah
# Check to ensure the container starts on boot (mandatory operation)
[root@node1 ~]# reboot
[root@node1 ~]# ssh wallah@node1
[wallah@node1 ~]# podman ps

Correct Answer:

Solution:
[root@node1 ~]# visudo
...
%wheel ALL=(ALL) NOPASSWD: ALL
%sysmgrs ALL=(ALL) NOPASSWD: ALL
# Verification (mandatory operation)
[root@node1 ~]# su - natasha
[natasha@node1 ~]# sudo cat /etc/shadow