Free Red Hat Certified System Administrator (RHCSA) Exam EX200 Exam Practice Test

The user authentication has been provided by ldap domain in 192.168.0.254. According the following requirements to get ldapuser.-LdapuserX must be able to login your system, X is your hostname number. But the ldapuser's home directory cannot be mounted, until you realize automatically mount by autofs server.- All ldap user's password is 'password'.

• Explanation:
  system-config-authentication &
  

  

Create the following users, groups, and group memberships:A group named adminuser.A user natasha who belongs to adminuser as a secondary group A user harry who also belongs to adminuser as a secondary group.A user sarah who does not have access to an interactive shell on the system, and who is not a member of adminuser, natasha, harry, and sarah should all have the password of redhat.

• Explanation:
  groupadd sysmgrs
  useradd -G sysmgrs Natasha
  We can verify the newly created user by cat /etc/passwd)
  # useradd -G sysmgrs harry
  # useradd -s /sbin/nologin sarrh
  # passwd Natasha
  # passwd harry
  # passwd sarrah
  

Binding to an external validation server.System server.domain11.example.com provides a LDAP validation service, your system should bind to this service as required:Base DN of validation service is dc=example,dc=comAfter the correct configuration, ldapuser1 can log into your system, it does not have HOME directory until you finish autofs questions, ldapuser1 password is password.

• Explanation:
  yum -y install sssd authconfig-gtk krb5-workstation authconfig-gtk // open the graphical interface
  Modify user account database to ldap, fill up DN and LDAP SERVER as questions required, use TLS to encrypt connections making tick, write http://server.domain11.example.com/pub/EXAMPLE-CA-CERT to download ca, authentication method choose ldap password.
  You can test if the ldapuser is added by the following command:
  Id ldapuser1
  Note: user password doesn't not need to set
  

There is a local logical volumes in your system, named with common and belong to VGSRV volume group, mount to the /common directory. The definition of size is 128 MB.Requirement:Extend the logical volume to 190 MB without any loss of data. The size is allowed between 160-160 MB after extending.

• Explanation:
  lvextend -L 190M /dev/mapper/vgsrv-common resize2fs /dev/mapper/vgsrv-common
  

Resize the logical volume vo and its filesystem to 290 MB. Make sure that the filesystem contents remain intact.Note: Partitions are seldom exactly the same size requested, so a size within the range of 260 MB to 320 MiB is acceptable.

• Explanation:
  df -hT
  lvextend -L +100M /dev/vg0/vo
  lvscan
  xfs_growfs /home/ // home is LVM mounted directory
  Note: This step is only need to do in our practice environment, you do not need to do in the real exam
  resize2fs /dev/vg0/vo // Use this comand to update in the real exam df -hT
  OR
  e2fsck -f/dev/vg0/vo
  umount /home
  resize2fs /dev/vg0/vo required partition capacity such as 100M lvreduce -l 100M /dev/vg0/vo mount /dev/vg0/vo /home
  df --Ht
  

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:5000The container should run as the root less user shangrila. 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.

• Explanation:
  *
  [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
  

Part 1 (on Node1 Server)Task 13 [Archiving and Transferring Files & 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.

• 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
  

One Logical Volume is created named as myvol under vo volume group and is mounted. The Initial Size of that Logical Volume is 400MB. Make successfully that the size of Logical Volume 200MB without losing any data. The size of logical volume 200MB to 210MB will be acceptable.

• Explanation:
  First check the size of Logical Volume: lvdisplay /dev/vo/myvol
  Make sure that the filesystem is in a consistent state before reducing:
  # fsck -f /dev/vo/myvol
  Now reduce the filesystem by 200MB.
  # resize2fs /dev/vo/myvol 200M
  It is now possible to reduce the logical volume. #lvreduce /dev/vo/myvol -L 200M
  Verify the Size of Logical Volume: lvdisplay /dev/vo/myvol
  Verify that the size comes in online or not: df -h
  

Create a volume group, and set 16M as a extends. And divided a volume group containing 50 extends on volume group lv, make it as ext4 file system, and mounted automatically under /mnt/data.

• Explanation:
  # pvcreate /dev/sda7 /dev/sda8
  # vgcreate -s 16M vg1 /dev/sda7 /dev/sda8
  # lvcreate -l 50 -n lvm02
  # mkfs.ext4 /dev/vg1/lvm02
  # blkid /dev/vg1/lv1
  # vim /etc/fstab
  # mkdir -p /mnt/data
  UUID=xxxxxxxx /mnt/data ext4 defaults 0 0
  # vim /etc/fstab
  # mount -a
  # mount
  (Verify)
  

Create the user named eric and deny to interactive login.

• Explanation:
  useradd eric
  passwd eric
  vi /etc/passwd
  eric:x:505:505::/home/eric:/sbin/nologin
  Which shell or program should start at login time is specified in /etc/passwd file? By default, Redhat Enterprise Linux assigns the /bin/bash shell to the users. To deny the interactive login, you should write /sbin/nologin or /bin/ false instead of login shell.