Red Hat Red Hat Certifications EX200 Questions & Answers

• Question 111:

  One Domain RHCE is configured in your lab, your domain server is server1.example.com. nisuser2001, nisuser2002, nisuser2003 user are created on your server 192.168.0.254:/rhome/stationx/nisuser2001. Make sure that when NIS user login in your system automatically mount the home directory. Home directory is separately shared on server /rhome/stationx/ where x is your Station number.

  Correct Answer: Check the anser in explanation.

  use the authconfig --nisserver= --nisdomain= -- update

  Example: authconfig --niserver=192.168.0.254 --nisdomain=RHCE --update or system-config-authentication

  Click on Enable NIS

  Type the NIS Domain: RHCE

  Type Server 192.168.0.254 then click on next and ok

  You will get a ok message.

  Create a Directory /rhome/stationx where x is your station number.

  vi /etc/auto.master and write at the end of file /rhome/stationx /etc/auto.home --timeout=60

  vi /etc/auto.home and write

  * -rw,soft,intr 192.168.0.254:/rhome/stationx/and

  Note: please specify your station number in the place of x.

  Service autofs restart

  Login as the nisuser2001 or nisuser2002 on another terminal will be Success. According to question, RHCE domain is already configured. We have to make a client of RHCE domain and automatically mount the home directory on your

  system. To make a member of domain, we use the authconfig with option or system-config authentication command. There a are lots of authentication server i.e NIS, LDAB, SMB etc. NIS is a RPC related Services, no need to configure

  the DNS, we should specify the NIS server address.

  Here Automount feature is available. When user tried to login, home directory will automatically mount. The automount service used the /etc/auto.master file. On /etc/auto.master file we specified the mount point the configuration file for mount point.

• Question 112:

  Part 2 (on Node2 Server)

  Task 7 [Implementing Advanced Storage Features]

  Create a thin-provisioned filesystem with the name think_fs from a pool think_pool using the devices.

  The filesystem should be mounted on /strav and must be persistent across reboot

  Correct Answer: Check the anser in explanation.

  * [root@node2 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vdd 252:48 0 5G 0 disk vde 252:64 0 10G 0 disk vdo1 253:4 0 50G 0 vdo /vbread [root@node2 ~]# yum install stratis* -y [root@node2 ~]# systemctl enable --now stratisd.service [root@node2 ~]# systemctl start stratisd.service [root@node2 ~]# systemctl status stratisd.service [root@node2 ~]# stratis pool create think_pool /dev/vdd [root@node2 ~]# stratis pool list Name Total Physical Properties think_pool 5 GiB / 37.63 MiB / 4.96 GiB ~Ca,~Cr

  * [root@node2 ~]# stratis filesystem create think_pool think_fs [root@node2 ~]# stratis filesystem list Pool Name Name Used Created Device UUID think_pool think_fs 546 MiB Mar 23 2021 08:21 /stratis/think_pool/think_fs ade6fdaab06449109540c2f3fdb9417d [root@node2 ~]# mkdir /strav [root@node2 ~]# lsblk [root@node2 ~]# blkid /dev/mapper/stratis-1-91ab9faf36a540f49923321ba1c5e40d-thin-fs- ade6fdaab06449109540c2f3fdb9417d: UUID="ade6fdaa-b064-4910-9540-c2f3fdb9417d" BLOCK_SIZE="512" TYPE="xfs"

  * [root@node2 ~]# vim /etc/fstab UUID=ade6fdaa-b064-4910-9540-c2f3fdb9417d /strav xfs defaults,x- systemd.requires=stratisd.service 0 0 [root@node2 ~]# mount /stratis/think_pool/think_fs /strav/ [root@node2 ~]# df -hT /dev/mapper/stratis-1-91ab9faf36a540f49923321ba1c5e40d-thin-fs- ade6fdaab06449109540c2f3fdb9417d xfs 1.0T 7.2G 1017G 1% /strav

• Question 113:

  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.

  Correct Answer: Check the anser in explanation.

  * root@node1 ~]# find / -user alex -type f > /home/alex/files

• Question 114:

  Part 1 (on Node1 Server) Task 10 [Configuring NTP/Time Synchronization]

  Configure your system so that it is an NTP client of utility.domain15.example.com

  The system time should be set to your (or nearest to you) timezone and ensure NTP sync is configured

  Correct Answer: Check the anser in explanation.

  * [root@node1 ~]# yum install chrony [root@node1 ~]# vim /etc/chrony.conf pool utility.domain15.example.com iburst [root@node1 ~]# systemctl enable chronyd [root@node1 ~]# systemctl restart chronyd [root@node1 ~]# systemctl status chronyd [root@node1 ~]# tzselect Please identify a location so that time zone rules can be set correctly. Please select a continent, ocean, "coord", or "TZ". 1) Africa 2) Americas 3) Antarctica 4) Asia 11) TZ - I want to specify the time zone using the Posix TZ format. # 4

  * Please select a country whose clocks agree with yours. 1) Afghanistan 18) Israel 35) Palestine 2) Armenia 19) Japan 36) Philippines 3) Azerbaijan 20) Jordan 37) Qatar 4) Bahrain 21) Kazakhstan 38) Russia 5) Bangladesh 22) Korea (North) 39) Saudi Arabia #? 5 The following information has been given: Bangladesh Therefore TZ='Asia/Dhaka' will be used. Is the above information OK? 1) Yes 2) No

  # 1 Asia/Dhaka [root@node1 ~]# chronyc sources -v ^? utility.domain15.example> 0 7 0 - +0ns[ +0ns] +/- 0ns

• Question 115:

  Part 1 (on Node1 Server)

  Task 16 [Running Containers]

  Configure your host journal to store all journal across reboot

  Copy all journal files from /var/log/journal/ and put them in the /home/shangrila/container- logserver

  Create and mount /home/shangrila/container-logserver as a persistent storage to the container as /var/log/ when container start

  Correct Answer: Check the anser in explanation.

  * [shangrila@node1 ~]$ podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d5ffe018a53c registry.domain15.example.com:5000/rhel8/rsyslog:latest /bin/rsyslog.sh 5 seconds ago Up 4 seconds ago logserver [shangrila@node1 ~]$ podman stats logserver Error: stats is not supported in rootless mode without cgroups v2 [shangrila@node1 ~]$ podman stop logserver d5ffe018a53ca7eb075bf560d1f30822ab6fe51eba58fd1a8f370eda79806496 [shangrila@node1 ~]$ podman rm logserver Error: no container with name or ID logserver found: no such container [shangrila@node1 ~]$ mkdir -p container-journal/

  * [shangrila@node1 ~]$ sudo systemctl restart systemd-journald [sudo] password for shangrila: [shangrila@node1 ~]$ sudo cp -av /var/log/journal/* container-journal/ [shangrila@node1 ~]$ sudo cp -av /var/log/journal/* container-journal/ [shangrila@node1 ~]$ sudo chown -R shangrila container-journal/ [shangrila@node1 ~]$ podman run -d --name logserver -v /home/shangrila/container- journal/:/var/log/journal:Z registry.domain15.example.com:5000/rhel8/rsyslog [shangrila@node1 ~]$ podman ps [shangrila@node1 ~]$ loginctl enable-linger [shangrila@node1 ~]$ loginctl show-user shangrila|grep -i linger Linger=yes

  * [shangrila@node1 ~]$ podman stop logserver [shangrila@node1 ~]$ podman rm logserver [shangrila@node1 ~]$ systemctl --user daemon-reload [shangrila@node1 ~]$ systemctl --user enable --now container-logserver [shangrila@node1 ~]$ podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3903e1d09170 registry.domain15.example.com:5000/rhel8/rsyslog:latest /bin/rsyslog.sh 4 seconds ago Up 4 seconds ago logserver [shangrila@node1 ~]$ systemctl --user stop container-logserver.service

  * [shangrila@node1 ~]$ sudo reboot [shangrila@node1 ~]$ podman ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7e6cd59c506a registry.domain15.example.com:5000/rhel8/rsyslog:latest /bin/rsyslog.sh 10 seconds ago Up 9 seconds ago logserver

• Question 116:

  Part 2 (on Node2 Server)

  Task 4 [Managing Logical Volumes]

  Resize the logical volume, lvrz and reduce filesystem to 4600 MiB. Make sure the the filesystem contents remain intact with mount point /datarz

  (Note: partitions are seldom exactly the size requested, so anything within the range of 4200MiB to 4900MiB is acceptable)

  Correct Answer: Check the anser in explanation.

  * [root@node2 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vdb 252:16 0 5G 0 disk vdb1 252:17 0 4.2G 0 part vgrz-lvrz 253:2 0 4.1G 0 lvm /datarz vdc 252:32 0 5G 0 disk vdc1 252:33 0 4.4G 0 part datavg-datalv 253:3 0 3.9G 0 lvm /data vdd 252:48 0 5G 0 disk vde 252:64 0 10G 0 disk [root@node2 ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvrz vgrz -wi-ao---- 4.10g [root@node2 ~]# vgs VG #PV #LV #SN Attr VSize VFree vgrz 1 1 0 wz--n- <4.15g 48.00m [root@node2 ~]# parted /dev/vdb print Number Start End Size Type File system Flags 1 1049kB 4456MB 4455MB primary lvm

  * [root@node2 ~]# df -hT Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vgrz-lvrz ext4 4.0G 17M 3.8G 1% /datarz [root@node2 ~]# parted /dev/vdb mkpart primary 4456MiB 5100MiB [root@node2 ~]# parted /dev/vdb set 2 lvm on [root@node2 ~]# udevadm settle [root@node2 ~]# pvcreate /dev/vdb2 Physical volume "/dev/vdb2" successfully created.

  * [root@node2 ~]# vgextend vgrz /dev/vdb2 Volume group "vgrz" successfully extended [root@node2 ~]# lvextend -r -L 4600M /dev/vgrz/lvrz Size of logical volume vgrz/lvrz changed from 4.10 GiB (1050 extents) to 4.49 GiB (1150 extents). Logical volume vgrz/lvrz successfully resized. [root@node2 ~]# resize2fs /dev/vgrz/lvrz [root@node2 ~]# df -hT Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vgrz-lvrz ext4 4.4G 17M 4.2G 1% /datarz

• Question 117:

  Part 2 (on Node2 Server)

  Task 1 [Controlling the Boot Process]

  Interrupt the boot process and reset the root password. Change it to kexdrams to gain access to the system

  Correct Answer: Check the anser in explanation.

  *

  1.

  Reboot the server pressing by Ctrl+Alt+Del

  2.

  When the boot-loader menu appears, press the cursor keys to highlight the default boot- loader entry

  3.

  Press e to edit the current entry.

  4.

  Use the cursor keys to navigate to the line that starts with linux.

  5.

  Press End to move the cursor to the end of the line.

  6.

  Append rd.break to the end of the line.

  7.

  Press Ctrl+x to boot using the modified configuration.

  8.

  At the switch_root prompt

  *

  switch_root:/# mount -o remount,rw /sysroot

  switch_root:/# chroot /sysroot

  sh-4.4# echo kexdrams | passwd --stdin root

  Changing password for user root.

  passwd: all authentication tokens updated successfully.

  sh-4.4# touch /.autorelabel

  sh-4.4# exit; exit

  *

  Type exit twice to continue booting your system as usual.

• Question 118:

  Part 1 (on Node1 Server)

  Task 11 [Scheduling Future Tasks]

  The user natasha must configure a cron job that runs daily at 14:23 local time and also the same cron job will run after every 2 minutes and executes:

  /bin/echo hello

  Correct Answer: Check the anser in explanation.

  *

  [root@node1 ~]# crontab -l -u natasha

  no crontab for natasha

  [root@node1 ~]# crontab -e -u natasha

  23 14 * * * /bin/echo hello

  */2 * * * * /bin/echo 2min

  crontab: installing new crontab

  [root@node1 ~]# crontab -l -u natasha

  23 14 * * * /bin/echo hello

  */2 * * * * /bin/echo 2min

  [root@node1 ~]# systemctl status crond.service

  *

  ### For Checking ###

  [root@node1 ~]# tail -f /var/log/cron

  Mar 23 13:23:48 node1 crontab[10636]: (root) REPLACE (natasha) Mar 23 13:23:48 node1 crontab[10636]: (root) END EDIT (natasha) Mar 23 13:23:50 node1 crontab[10638]: (root) LIST (natasha) Mar 23 13:24:01 node1 crond[1349]: (root)

  FAILED (loading cron table) Mar 23 13:24:02 node1 CROND[10673]: (natasha) CMD (/bin/echo 2min)

• Question 119:

  Part 2 (on Node2 Server)

  Task 3 [Managing Logical Volumes]

  Create a new volume group in the name of datavg and physical volume extent is 16 MB

  Create a new logical volume in the name of datalv with the size of 250 extents and file system must xfs

  Then the logical volume should be mounted automatically mounted under /data at system boot time

  Correct Answer: Check the anser in explanation.

  * [root@node2 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vdb 252:16 0 5G 0 disk vdb1 252:17 0 4.2G 0 part vgrz-lvrz 253:2 0 4.1G 0 lvm /datarz vdc 252:32 0 5G 0 disk vdd 252:48 0 5G 0 disk vde 252:64 0 10G 0 disk [root@node2 ~]# parted /dev/vdc mklabel msdos [root@node2 ~]# parted /dev/vdc mkpart primary 1MiB 4200MiB [root@node2 ~]# parted /dev/vdc set 1 lvm on

  * [root@node2 ~]# udevadm settle [root@node2 ~]# pvcreate /dev/vdc1 Physical volume "/dev/vdc1" successfully created. [root@node2 ~]# vgcreate -s 16M datavg /dev/vdc1 Volume group "datavg" successfully created [root@node2 ~]# lvcreate -n datalv -L 4000M datavg Logical volume "datalv" created. [root@node2 ~]# mkfs.xfs /dev/datavg/datalv [root@node2 ~]# mkdir /data [root@node2 ~]# blkid /dev/mapper/datavg-datalv: UUID="7397a292-d67d-4632-941e-382e2bd922ce" BLOCK_SIZE="512" TYPE="xfs"

  * [root@node2 ~]# vim /etc/fstab UUID=7397a292-d67d-4632-941e-382e2bd922ce /data xfs defaults 0 0 [root@node2 ~]# mount UUID=7397a292-d67d-4632-941e-382e2bd922ce /data [root@node2 ~]# reboot [root@node2 ~]# df -hT Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/datavg-datalv xfs 3.9G 61M 3.9G 2% /data

• Question 120:

  Part 1 (on Node1 Server)

  Task 13 [Archiving and Transferring Files and SELinux]

  Create a backup file named /root/backup.tar.bz2. The backup file should contain the content of /usr/local and should be zipped with bzip2 compression format.

  Furthermore, ensure SELinux is in enforcing mode. If it is not, change SELinux to enforcing mode.

  Correct Answer: Check the anser in explanation.

  * [root@node1 ~]# tar cvf /root/backup.tar /usr/local/ tar: Removing leading `/' from member names /usr/local/ /usr/local/bin/ /usr/local/etc/ [root@node1 ~]# ls backup.tar [root@node1 ~]# file backup.tar backup.tar: POSIX tar archive (GNU) [root@node1 ~]# bzip2 backup.tar [root@node1 ~]# ls backup.tar.bz2 [root@node1 ~]# file backup.tar.bz2

  backup.tar.bz2: bzip2 compressed data, block size = 900k

  * [root@node1 ~]# sestatus SELinux status: enabled [root@node1 ~]# cat /etc/selinux/config SELINUX=enforcing SELINUXTYPE=targeted [root@node1 ~]# reboot ### For Checking ### [root@node1 ~]# sestatus SELinux status: enabled