最新的RedHat Red Hat Certified System Administrator - RHCSA (EX200 Korean Version) - EX200 Korean免費考試真題
問題1
/share/projects 디렉토리를 생성하고, Alex를 소유자로 설정한 다음, 사용자들이 서로의 파일을 삭제할 수 없도록 스티키 비트를 구성하세요.
正確答案:
See the solution below in Explanation.
Explanation:
Solution:
mkdir -p /share/projects
chown alex /share/projects/
chmod a+rwx,+t /share/projects/
ls -ld /share/projects/
Detailed Explanation:
* chmod a+rwx gives read, write, and execute to everyone.
* +t sets the sticky bit.
* Sticky bit on a shared directory means users can create files, but only the file owner, directory owner, or
root can delete them.
* This is the same model used on /tmp.
Explanation:
Solution:
mkdir -p /share/projects
chown alex /share/projects/
chmod a+rwx,+t /share/projects/
ls -ld /share/projects/
Detailed Explanation:
* chmod a+rwx gives read, write, and execute to everyone.
* +t sets the sticky bit.
* Sticky bit on a shared directory means users can create files, but only the file owner, directory owner, or
root can delete them.
* This is the same model used on /tmp.
問題2
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.
問題3
시스템 시간 동기화 설정을 time.example.com을 NTP 소스로 사용하도록 구성하고 동기화가 완료되었는지 확인하십시오.
正確答案:
See the solution below in Explanation.
Explanation:
Solution:
sed -i '/^pool /d;/^server /d' /etc/chrony.conf
echo "server time.example.com iburst" > > /etc/chrony.conf
systemctl enable --now chronyd
systemctl restart chronyd
chronyc sources -v
chronyc tracking
Detailed Explanation:
* chronyd is the RHEL 10 NTP implementation.
* iburst speeds up initial synchronization.
* chronyc sources -v and chronyc tracking confirm the sync state.
* Red Hat's RHEL 10 time synchronization documentation uses chrony as the supported NTP
implementation. ( Red Hat Documentation )
Explanation:
Solution:
sed -i '/^pool /d;/^server /d' /etc/chrony.conf
echo "server time.example.com iburst" > > /etc/chrony.conf
systemctl enable --now chronyd
systemctl restart chronyd
chronyc sources -v
chronyc tracking
Detailed Explanation:
* chronyd is the RHEL 10 NTP implementation.
* iburst speeds up initial synchronization.
* chronyc sources -v and chronyc tracking confirm the sync state.
* Red Hat's RHEL 10 time synchronization documentation uses chrony as the supported NTP
implementation. ( Red Hat Documentation )
問題4
사용자가 생성한 파일에 대한 기본 UMASK를 설정합니다.
사용자 natasha님께:
* 새로 생성되는 파일의 기본 권한은 r--r--r--이어야 합니다.
* 새로 생성되는 디렉터리의 기본 권한은 r-xr-xr-x여야 합니다.
사용자 natasha님께:
* 새로 생성되는 파일의 기본 권한은 r--r--r--이어야 합니다.
* 새로 생성되는 디렉터리의 기본 권한은 r-xr-xr-x여야 합니다.
正確答案:
Solution:
# su - natasha
Write the umask setting into the user's .bashrc file in the home directory:
bash
Copy code
echo 'umask 222' >> .bashrc
source .bashrc
Command explanation:
umask is used to control the default permissions for files and directories created by a user.
In umask:
The first digit is for special permissions and is usually 0 (can be omitted if not needed).
The second digit controls owner permissions.
The third digit controls group permissions.
The fourth digit controls permissions for others.
# su - natasha
Write the umask setting into the user's .bashrc file in the home directory:
bash
Copy code
echo 'umask 222' >> .bashrc
source .bashrc
Command explanation:
umask is used to control the default permissions for files and directories created by a user.
In umask:
The first digit is for special permissions and is usually 0 (can be omitted if not needed).
The second digit controls owner permissions.
The third digit controls group permissions.
The fourth digit controls permissions for others.
問題5
논리 볼륨 크기 조정
논리 볼륨 "vo"와 해당 파일 시스템의 크기를 300MiB로 조정하되, 파일 시스템 내용은 변경하지 않도록 하십시오.
참고: 파티션 크기는 요청된 크기와 정확히 일치하는 경우가 드물기 때문에 290MiB에서 310MiB 사이의 범위는 허용됩니다.
ext4 파일 시스템의 경우 resize2fs를 사용하면 즉시 적용되고, xfs 파일 시스템의 경우 xfs_growfs를 사용하면 즉시 적용됩니다.
논리 볼륨 "vo"와 해당 파일 시스템의 크기를 300MiB로 조정하되, 파일 시스템 내용은 변경하지 않도록 하십시오.
참고: 파티션 크기는 요청된 크기와 정확히 일치하는 경우가 드물기 때문에 290MiB에서 310MiB 사이의 범위는 허용됩니다.
ext4 파일 시스템의 경우 resize2fs를 사용하면 즉시 적용되고, xfs 파일 시스템의 경우 xfs_growfs를 사용하면 즉시 적용됩니다.
正確答案:
Solution:
# Scan logical volumes
[root@node2 ~]# lvscan
# Extend the logical volume. With -rL, the filesystem space is adjusted immediately after extending the volume.
[root@node2 ~]# lvextend -rL 300M /dev/myvol/vo
# Check the changes
[root@node2 ~]# lsblk
[root@node2 ~]# lvs
# Verification
[root@node2 ~]# df -h
# Scan logical volumes
[root@node2 ~]# lvscan
# Extend the logical volume. With -rL, the filesystem space is adjusted immediately after extending the volume.
[root@node2 ~]# lvextend -rL 300M /dev/myvol/vo
# Check the changes
[root@node2 ~]# lsblk
[root@node2 ~]# lvs
# Verification
[root@node2 ~]# df -h
問題6
HTTP 서비스를 영구적으로 허용하도록 방화벽 규칙을 구성하십시오.
正確答案:
See the solution below in Explanation.
Explanation:
Solution:
firewall-cmd --permanent --add-service=http
firewall-cmd --reload
firewall-cmd --list-services
Detailed Explanation:
* --permanent saves the rule.
* --reload applies it.
* --list-services verifies the active configuration.
* Firewalld remains the standard firewall interface in RHEL 10. ( Red Hat Documentation )
Explanation:
Solution:
firewall-cmd --permanent --add-service=http
firewall-cmd --reload
firewall-cmd --list-services
Detailed Explanation:
* --permanent saves the rule.
* --reload applies it.
* --list-services verifies the active configuration.
* Firewalld remains the standard firewall interface in RHEL 10. ( Red Hat Documentation )
問題7
GRUB에서 비상 모드로 한 번 부팅하십시오.
正確答案:
See the solution below in Explanation.
Explanation:
Solution:
* Reboot the server.
* At the GRUB menu, highlight the kernel entry and press e.
* Find the line starting with linux.
* Append:
systemd.unit=emergency.target
* Press Ctrl+x to boot.
Detailed Explanation:
* This changes the boot target only for the current boot.
* Emergency mode is useful for rescue and maintenance tasks.
* Red Hat's RHEL 10 systemd guidance documents booting with systemd.unit= < name > .target from
GRUB. ( Red Hat Documentation )
Explanation:
Solution:
* Reboot the server.
* At the GRUB menu, highlight the kernel entry and press e.
* Find the line starting with linux.
* Append:
systemd.unit=emergency.target
* Press Ctrl+x to boot.
Detailed Explanation:
* This changes the boot target only for the current boot.
* Emergency mode is useful for rescue and maintenance tasks.
* Red Hat's RHEL 10 systemd guidance documents booting with systemd.unit= < name > .target from
GRUB. ( Red Hat Documentation )
