최신 EX200日本語 무료덤프 - RedHat Red Hat Certified System Administrator - RHCSA (EX200日本語版)
/dev/sdb上に、1つのパーティション、物理ボリューム、ボリュームグループ、論理ボリューム、およびXFSファイルシステムを含むLVMストレージを作成します。
정답:
See the solution below in Explanation.
Explanation:
Solution:
* Partition the disk:
fdisk /dev/sdb
Inside fdisk:
* n = new partition
* p = primary
* 1 = partition number
* accept defaults
* size +700M
* t = change type
* set Linux LVM type
* w = write changes
* Create the physical volume:
pvcreate /dev/sdb1
* Create the volume group:
vgcreate vg_data /dev/sdb1
* Create the logical volume:
lvcreate -L 500M -n lv_data vg_data
* Create the filesystem:
mkfs.xfs /dev/vg_data/lv_data
Detailed Explanation:
* The lab specifies a 700 MB partition and a 500 MB logical volume.
* pvcreate initializes the partition for LVM.
* vgcreate builds the storage pool.
* lvcreate allocates space from the volume group.
* mkfs.xfs creates the filesystem, which is standard on RHEL.
Explanation:
Solution:
* Partition the disk:
fdisk /dev/sdb
Inside fdisk:
* n = new partition
* p = primary
* 1 = partition number
* accept defaults
* size +700M
* t = change type
* set Linux LVM type
* w = write changes
* Create the physical volume:
pvcreate /dev/sdb1
* Create the volume group:
vgcreate vg_data /dev/sdb1
* Create the logical volume:
lvcreate -L 500M -n lv_data vg_data
* Create the filesystem:
mkfs.xfs /dev/vg_data/lv_data
Detailed Explanation:
* The lab specifies a 700 MB partition and a 500 MB logical volume.
* pvcreate initializes the partition for LVM.
* vgcreate builds the storage pool.
* lvcreate allocates space from the volume group.
* mkfs.xfs creates the filesystem, which is standard on RHEL.
デフォルトのパスワードポリシーを設定します
新規作成ユーザーに対してパスワードポリシーを設定し、ユーザー作成時にパスワードがデフォルトで25日後に期限切れになるようにします。
新規作成ユーザーに対してパスワードポリシーを設定し、ユーザー作成時にパスワードがデフォルトで25日後に期限切れになるようにします。
정답:
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
[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
NTPの設定
システムをmaterials.example.comのNTPサーバーと同期するように設定してください(注：materials.example.comはclassroom.example.comの別名です)。
システムをmaterials.example.comのNTPサーバーと同期するように設定してください(注：materials.example.comは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
# 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
ファイルを探す
ユーザー「jacques」に属するすべてのファイルを検索し、それらをルートディレクトリの下にあるディレクトリ /root/findfiles に移動します。
ユーザー「jacques」に属するすべてのファイルを検索し、それらをルートディレクトリの下にあるディレクトリ /root/findfiles に移動します。
정답:
Solution:
[root@node1 ~]# mkdir /root/findfiles
[root@node1 ~]# find / -user jacques
[root@node1 ~]# find / -user jacques -exec cp -a {} /root/findfiles \;
# Verification
[root@node1 ~]# ll /root/findfiles/
[root@node1 ~]# mkdir /root/findfiles
[root@node1 ~]# find / -user jacques
[root@node1 ~]# find / -user jacques -exec cp -a {} /root/findfiles \;
# Verification
[root@node1 ~]# ll /root/findfiles/
Podmanイメージを作成し、ユーザーalexの永続化を有効にし、ユーザーコンテナ用のsystemdユニットを生成して有効にします。
정답:
See the solution below in Explanation.
Explanation:
Solution:
podman build -t myimage -f Containerfile .
loginctl enable-linger alex
cd ~/.config/systemd/user/
podman generate systemd --name mycontainer --files --new
systemctl --user daemon-reload
systemctl --user enable --now container-mycontainer.service
Detailed Explanation:
* podman build creates the container image.
* loginctl enable-linger alex allows user services to keep running without an active login session.
* podman generate systemd creates a systemd unit file for the container.
* systemctl --user manages the unit in the user session scope.
* On newer Podman releases, behavior and defaults have changed in RHEL 10, but the lab's workflow is
still conceptually valid.
Explanation:
Solution:
podman build -t myimage -f Containerfile .
loginctl enable-linger alex
cd ~/.config/systemd/user/
podman generate systemd --name mycontainer --files --new
systemctl --user daemon-reload
systemctl --user enable --now container-mycontainer.service
Detailed Explanation:
* podman build creates the container image.
* loginctl enable-linger alex allows user services to keep running without an active login session.
* podman generate systemd creates a systemd unit file for the container.
* systemctl --user manages the unit in the user session scope.
* On newer Podman releases, behavior and defaults have changed in RHEL 10, but the lab's workflow is
still conceptually valid.
ユーザーjohnのcronアクセスを拒否します。
정답:
See the solution below in Explanation.
Explanation:
Solution:
echo "john" > > /etc/cron.deny
Detailed Explanation:
* cron.deny blocks listed users from using cron.
* This is the simplest way to deny scheduled-job access for one user.
Explanation:
Solution:
echo "john" > > /etc/cron.deny
Detailed Explanation:
* cron.deny blocks listed users from using cron.
* This is the simplest way to deny scheduled-job access for one user.
registry.access.redhat.com/ubi10/ubi イメージをプルし、webtest という名前のルートレスコンテナを実行して、
3600秒間眠る。
3600秒間眠る。
정답:
See the solution below in Explanation.
Explanation:
Solution:
podman pull registry.access.redhat.com/ubi10/ubi
podman run -d --name webtest registry.access.redhat.com/ubi10/ubi sleep 3600
podman ps
Detailed Explanation:
* podman pull downloads the image.
* podman run -d starts the container in the background.
* Rootless Podman is a normal RHEL container workflow.
* RHEL 10 container documentation continues to center on Podman for image and container
management. ( Red Hat Documentation )
Explanation:
Solution:
podman pull registry.access.redhat.com/ubi10/ubi
podman run -d --name webtest registry.access.redhat.com/ubi10/ubi sleep 3600
podman ps
Detailed Explanation:
* podman pull downloads the image.
* podman run -d starts the container in the background.
* Rootless Podman is a normal RHEL container workflow.
* RHEL 10 container documentation continues to center on Podman for image and container
management. ( Red Hat Documentation )