EX200試験無料問題集「RedHat Red Hat Certified System Administrator - RHCSA 認定」
Configure the system synchronous as 172.24.40.10.
正解：
Graphical Interfaces:
System-->Administration-->Date & Time
OR
# system-config-date
System-->Administration-->Date & Time
OR
# system-config-date
Adjust Logical Volume Size
Adjust the size of the logical volume "vo" and its filesystem to 300 MiB, ensuring that the filesystem content remains unchanged.
Note: Partition sizes rarely match the requested size exactly, so a range of 290 MiB to 310 MiB is acceptable.
For ext4 filesystems, use resize2fs to take effect immediately; for xfs filesystems, use xfs_growfs to take effect immediately.
Adjust the size of the logical volume "vo" and its filesystem to 300 MiB, ensuring that the filesystem content remains unchanged.
Note: Partition sizes rarely match the requested size exactly, so a range of 290 MiB to 310 MiB is acceptable.
For ext4 filesystems, use resize2fs to take effect immediately; for xfs filesystems, use xfs_growfs to take effect immediately.
正解：
# 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
[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
Create a user alex with a userid of 3400. The password for this user should be redhat.
正解：
useradd -u 3400 alex
passwd alex
su -alex
passwd alex
su -alex
There is a server having 172.24.254.254 and 172.25.254.254. Your System lies on 172.24.0.0/16. Make successfully ping to 172.25.254.254 by Assigning following IP: 172.24.0.x where x is your station number.
正解：
Use netconfig command
Enter the IP Address as given station number by your examiner: example: 172.24.0.1 Enter Subnet Mask Enter Default Gateway and primary name server press on ok ifdown eth0 ifup eth0 verify using ifconfig In the lab server is playing the role of router, IP forwarding is enabled. Just set the Correct IP and gateway, you can ping to 172.25.254.254.
Enter the IP Address as given station number by your examiner: example: 172.24.0.1 Enter Subnet Mask Enter Default Gateway and primary name server press on ok ifdown eth0 ifup eth0 verify using ifconfig In the lab server is playing the role of router, IP forwarding is enabled. Just set the Correct IP and gateway, you can ping to 172.25.254.254.
Part 1 (on Node1 Server)
Task 1 [Managing Networking]
Please create new network connection with existing interface (enp1s0) using provided values:
IPv4: 172.25.X.10/255.255.255.0 (where X is your domain number: Domain15) Gateway: 172.25.X.2 DNS server: 172.25.X.2 Add the following secondary IP addresses statically to your current running connection. Do this in a way that does not compromise your existing settings:
IPv4: 10.0.0.5/24 and set the hostname node1.domain15.example.com
Task 1 [Managing Networking]
Please create new network connection with existing interface (enp1s0) using provided values:
IPv4: 172.25.X.10/255.255.255.0 (where X is your domain number: Domain15) Gateway: 172.25.X.2 DNS server: 172.25.X.2 Add the following secondary IP addresses statically to your current running connection. Do this in a way that does not compromise your existing settings:
IPv4: 10.0.0.5/24 and set the hostname node1.domain15.example.com
正解：
* [root@node1 ~]# nmcli connection show
[root@node1 ~]# nmcli connection add con-name static ifname enp1s0 type ethernet ipv4.addresses 172.25.15.10/24 ipv4.gateway 172.25.15.2 ipv4.dns 172.25.15.2
[root@node1 ~]# nmcli connection modify static ipv4.method manual connection.autoconnect yes
[root@node1 ~]# nmcli connection modify static +ipv4.addresses 10.0.0.5/24
[root@node1 ~]# nmcli connection up static
[root@node1 ~]# nmcli connection show
[root@node1 ~]# hostnamectl set-hostname node1.domain15.example.com
[root@node1 ~]# hostnamectl status
[root@node1 ~]# nmcli connection down static
* [root@node1 ~]# nmcli connection up static
[root@node1 ~]# ip addr show
[root@node1 ~]# reboot
### For checking ###
[root@node1 ~]# ip addr show
[root@node1 ~]# netstat -nr
[root@node1 ~]# cat /etc/resolv.conf
[root@node1 ~]# nmcli connection add con-name static ifname enp1s0 type ethernet ipv4.addresses 172.25.15.10/24 ipv4.gateway 172.25.15.2 ipv4.dns 172.25.15.2
[root@node1 ~]# nmcli connection modify static ipv4.method manual connection.autoconnect yes
[root@node1 ~]# nmcli connection modify static +ipv4.addresses 10.0.0.5/24
[root@node1 ~]# nmcli connection up static
[root@node1 ~]# nmcli connection show
[root@node1 ~]# hostnamectl set-hostname node1.domain15.example.com
[root@node1 ~]# hostnamectl status
[root@node1 ~]# nmcli connection down static
* [root@node1 ~]# nmcli connection up static
[root@node1 ~]# ip addr show
[root@node1 ~]# reboot
### For checking ###
[root@node1 ~]# ip addr show
[root@node1 ~]# netstat -nr
[root@node1 ~]# cat /etc/resolv.conf
Part 1 (on Node1 Server)
Task 17 [Accessing Linux File Systems]
Find all the files owned by user "alex" and redirect the output to /home/alex/files.
Task 17 [Accessing Linux File Systems]
Find all the files owned by user "alex" and redirect the output to /home/alex/files.
正解：
* root@node1 ~]# find / -user alex -type f > /home/alex/files
Make on /archive directory that only the user owner and group owner member can fully access.
正解：
chmod 770 /archive
Verify using : ls -ld /archive Preview should be like:
drwxrwx--- 2 root sysuser 4096 Mar 16 18:08 /archive
To change the permission on directory we use the chmod command. According to the question that only the owner user (root) and group member (sysuser) can fully access the directory so: chmod 770 /archive
Verify using : ls -ld /archive Preview should be like:
drwxrwx--- 2 root sysuser 4096 Mar 16 18:08 /archive
To change the permission on directory we use the chmod command. According to the question that only the owner user (root) and group member (sysuser) can fully access the directory so: chmod 770 /archive
Part 1 (on Node1 Server)
Task 15 [Running Containers]
Create a container named logserver with the image rhel8/rsyslog found from the registry registry.domain15.example.com:5000 The container should run as the root less user shangril a. use redhat as password [sudo user] Configure the container with systemd services as the shangrila user using the service name, "container-logserver" so that it can be persistent across reboot.
Use admin as the username and admin123 as the credentials for the image registry.
Task 15 [Running Containers]
Create a container named logserver with the image rhel8/rsyslog found from the registry registry.domain15.example.com:5000 The container should run as the root less user shangril a. use redhat as password [sudo user] Configure the container with systemd services as the shangrila user using the service name, "container-logserver" so that it can be persistent across reboot.
Use admin as the username and admin123 as the credentials for the image registry.
正解：
* [root@workstation ~]# ssh shangrila@node1
[shangrila@node1 ~]$ podman login registry.domain15.example.com:5000
Username: admin
Password:
Login Succeeded!
[shangrila@node1 ~]$ podman pull registry.domain15.example.com:5000/rhel8/rsyslog
[shangrila@node1 ~]$ podman run -d --name logserver registry.domain15.example.com:5000/rhel8/rsyslog
021b26669f39cc42b8e94eab886ba8293d6247bf68e4b0d76db2874aef284d6d
[shangrila@node1 ~]$ mkdir -p ~/.config/systemd/user
[shangrila@node1 ~]$ cd ~/.config/systemd/user
* [shangrila@node1 user]$ podman generate systemd --name logserver --files --new
/home/shangrila/.config/systemd/user/container-logserver.service
[shangrila@node1 ~]$ systemctl --user daemon-reload
[shangrila@node1 user]$ systemctl --user enable --now container-logserver.service
[shangrila@node1 ~]$ podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7d9f7a8a4d63 registry.domain15.example.com:5000/rhel8/rsyslog:latest /bin/rsyslog.sh 2 seconds ago logserver
[shangrila@node1 ~]$ sudo reboot
[shangrila@node1 ~]$ cd .config/systemd/user
[shangrila@node1 user]$ systemctl --user status
[shangrila@node1 ~]$ podman login registry.domain15.example.com:5000
Username: admin
Password:
Login Succeeded!
[shangrila@node1 ~]$ podman pull registry.domain15.example.com:5000/rhel8/rsyslog
[shangrila@node1 ~]$ podman run -d --name logserver registry.domain15.example.com:5000/rhel8/rsyslog
021b26669f39cc42b8e94eab886ba8293d6247bf68e4b0d76db2874aef284d6d
[shangrila@node1 ~]$ mkdir -p ~/.config/systemd/user
[shangrila@node1 ~]$ cd ~/.config/systemd/user
* [shangrila@node1 user]$ podman generate systemd --name logserver --files --new
/home/shangrila/.config/systemd/user/container-logserver.service
[shangrila@node1 ~]$ systemctl --user daemon-reload
[shangrila@node1 user]$ systemctl --user enable --now container-logserver.service
[shangrila@node1 ~]$ podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7d9f7a8a4d63 registry.domain15.example.com:5000/rhel8/rsyslog:latest /bin/rsyslog.sh 2 seconds ago logserver
[shangrila@node1 ~]$ sudo reboot
[shangrila@node1 ~]$ cd .config/systemd/user
[shangrila@node1 user]$ systemctl --user status
Update the kernel from ftp://instructor.example.com/pub/updates.
According the following requirements:
The updated kernel must exist as default kernel after rebooting the system.
The original kernel still exists and is available in the system.
According the following requirements:
The updated kernel must exist as default kernel after rebooting the system.
The original kernel still exists and is available in the system.
正解：
rpm -ivh kernel-firm...
rpm -ivh kernel...
rpm -ivh kernel...
In the system, mounted the iso image /root/examine.iso to/mnt/iso directory. And enable automatically mount (permanent mount) after restart system.
正解：
mkdir -p /mnt/iso
/etc/fstab:
/root/examine.iso /mnt/iso iso9660 loop 0 0 mount -a
mount | grep examine
/etc/fstab:
/root/examine.iso /mnt/iso iso9660 loop 0 0 mount -a
mount | grep examine