Create Archive
Create a tar archive named /root/backup.tar.bz2, which should contain the contents of /usr/local. The tar archive must be compressed using bzip2.
正解:
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
質問 2:
Configure an NFS export /srv/nfs/projects so clients on 192.168.50.0/24 can mount it read-write.
正解:
See the solution below in Explanation.
Explanation:
Solution:
dnf install -y nfs-utils
mkdir -p /srv/nfs/projects
echo "/srv/nfs/projects 192.168.50.0/24(rw,sync)" > > /etc/exports
exportfs -rav
systemctl enable --now nfs-server
firewall-cmd --permanent --add-service=nfs
firewall-cmd --reload
exportfs -s
Detailed Explanation:
* nfs-utils provides the NFS server tools.
* /etc/exports defines the exported directory and allowed client network.
* exportfs -rav reloads exports.
* nfs-server must be enabled and started.
* If a firewall is enabled, the NFS service must be allowed.
* RHEL 10 network file services documentation covers NFS server configuration. ( Red Hat
Documentation )
質問 3:
Configure NTP
Configure your system to synchronize with the NTP server of materials.example.com (Note: materials.example.com is an alias for classroom.example.com).
正解:
Solution:
# Install the chrony service for configuring NTP server
[root@node1 ~]# yum -y install chrony
[root@node1 ~]# vim /etc/chrony.conf
server materials.example.com iburst
[root@node1 ~]# systemctl restart chronyd
[root@node1 ~]# systemctl enable chronyd
# Check
# Set an arbitrary time
[root@node1 ~]# date -s "1982-1-1"
Fri Jan 1 12:00:00 AM EST 1982
# Restart the NTP server
[root@node1 ~]# systemctl restart chronyd
# Check if the time is synchronized
# Execute after 3-5 seconds, too fast won't synchronize the time
[root@node1 ~]# date
Tue Dec 12 11:40:19 PM EST 2023
# Use the chronyc command to check synchronization status
[root@node1 ~]# chronyc sources -v
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| / 'x' = may be in error, '~' = too variable, '?' = unusable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
^* classroom.lab.example.com 8 6 17 42 -14us[ -11us] +/- 463us
質問 4:
Configure Network Settings
Configure node1 with the following network settings:
Hostname: node1.domain250.example.com
IP address: 172.25.250.100
Subnet mask: 255.255.255.0
Gateway: 172.25.250.254
正解:
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
質問 5:
Configure AutoFS so that accessing /shares/projects mounts server1:/srv/nfs/projects.
正解:
See the solution below in Explanation.
Explanation:
Solution:
dnf install -y autofs
mkdir -p /shares
echo "/shares /etc/auto.shares" > > /etc/auto.master
echo "projects -fstype=nfs,rw server1:/srv/nfs/projects" > /etc/auto.shares
systemctl enable --now autofs
ls /shares/projects
Detailed Explanation:
* /etc/auto.master defines the main map.
* /etc/auto.shares defines the indirect mount entry.
* The mount happens on demand when /shares/projects is accessed.
* RHEL 10 file-system documentation includes AutoFS for on-demand mounts. ( Red Hat
Documentation )
質問 6:
Configure autofs
Configure autofs to automatically mount the home directory of a remote user as described below:
- materials.example.com (172.25.254.254) exports /rhome via NFS to your system. This filesystem contains a pre-configured home directory for the user
remoteuser1.
- The home directory of remoteuser1 is materials.example.com:/rhome/remoteuser1.
- The home directory of remoteuser1 should be automatically mounted locally at /rhome/remoteuser1.
- The home directory must be writable by the user.
- The password for remoteuser1 is "flectrag".
正解:
Solution:
# Preparations (not required for the exam)
# Go back to foundation0, remote into classroom, create the remoteuser1 user and directory.
# This step is necessary to avoid issues with autofs mounting during testing.
[kiosk@foundation0 ~]$ ssh root@classroom 'useradd -u 1010 remoteuser1 && mkdir -p /rhome/remoteuser1 && chown remoteuser1: /rhome/remoteuser1'
# Install nfs-utils and autofs
[root@node1 ~]# yum -y install nfs-utils autofs
[root@node1 ~]# vim /etc/auto.master
/rhome /etc/auto.rhome
[root@node1 ~]# vim /etc/auto.rhome
remoteuser1 -rw materials.example.com:/rhome/remoteuser1
[root@node1 ~]# systemctl enable --now autofs
# Verification
[root@node1 ~]# ll /rhome/
[root@node1 ~]# ssh remoteuser1@localhost
remoteuser1@localhost\'s password: `flectrag`
$ pwd
/rhome/remoteuser1
$ touch my.file
$ mount | grep rhome
...
materials.example.com:/rhome/remoteuser1 on /rhome/remoteuser1 type nfs4
(`rw`,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.25.250.100,local_lock=none,addr=1
72.25.254.254)
質問 7:
Configure User Account
Configure the user account "manalo" with the user ID 3533. The password for this user should be "flectrag".
正解:
Solution:
[root@node1 ~]# useradd -u 3533 manalo
[root@node1 ~]# echo flectrag | passwd --stdin manalo
901 お客様のコメント
クリック」





藤*绫 -
実際にEX200試験は、どの本でもあてはまることかと思いますが、載っている内容の五分のよんぐらいが出る印象でした。Pass4Testさんすごっす