정답:

Solution:
# Install container management tools
[root@node1 ~]# dnf -y install container-tools
# Execute operations as the user wallah
[root@node1 ~]# ssh wallah@localhost
# Download the container build file
[wallah@node1 ~]# wget http://classroom/Containerfile
# Log in to the image registry
[wallah@node1 ~]# podman login -u admin -p redhat321 registry.lab.example.com
# Build the container image using the Containerfile in the current directory, with the image name "pdf"
[wallah@node1 ~]# podman build -t pdf .
# View the images
[wallah@node1 ~]$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/pdf latest 1d6e7ea71460 31 seconds ago 300 MB
registry.lab.example.com/ubi9-beta/ubi latest 28b0a4b69d9b 2 years ago 229 MB

정답:

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:
groupadd ops
visudo -f /etc/sudoers.d/ops-restart-httpd
Add this line to the file:
%ops ALL=(ALL) NOPASSWD: /usr/bin/systemctl restart httpd
Set correct permissions:
chmod 440 /etc/sudoers.d/ops-restart-httpd
visudo -cf /etc/sudoers.d/ops-restart-httpd
Detailed Explanation:
* Using /etc/sudoers.d/ is the standard safe approach.
* visudo validates syntax and helps prevent syntax errors.
* %ops applies the rule to the whole group.
* Restricting the exact command is better than granting broad sudo access. Red Hat's RHEL 10 security
hardening guide documents sudo configuration through sudoers. ( Red Hat Documentation )

정답:

Solution:
[root@node1 ~]# vim /etc/login.defs +25
Type / and search for PASS_MAX_DAYS.
Modify it to:
PASS_MAX_DAYS 25
Verify:
[root@node1 ~]# useradd user1
[root@node1 ~]# chage -l user1