26 August, 2023
Renewal EX200 Red Hat Certified System Administrator (RHCSA) Exam EX200 Free Question
Want to know Actualtests EX200 Exam practice test features? Want to lear more about Red-Hat EX200 Red Hat Certified System Administrator (RHCSA) Exam certification experience? Study Approved Red-Hat EX200 answers to Abreast of the times EX200 questions at Actualtests. Gat a success with an absolute guarantee to pass Red-Hat EX200 (EX200 Red Hat Certified System Administrator (RHCSA) Exam) test on your first attempt.
Red-Hat EX200 Free Dumps Questions Online, Read and Test Now.
Question 1
You are new System Administrator and from now you are going to handle the system and your main task is Network monitoring, Backup and Restore. But you don't know the root password. Change the root password to redhat and login in default Runlevel.
Solution:
When you Boot the System, it starts on default Runlevel specified in /etc/inittab:
Id:?:initdefault:
When System Successfully boot, it will ask for username and password. But you don't know the root's password. To change the root password you need to boot the system into single user mode. You can pass the kernel arguments from the boot loader.
1. Restart the System.
2. You will get the boot loader GRUB screen.
3. Press a and type 1 or s for single mode ro root=LABEL=/ rhgb queit s
4. System will boot on Single User mode.
5. Use passwd command to change.
6. Press ctrl+d
Does this meet the goal?
Solution:
When you Boot the System, it starts on default Runlevel specified in /etc/inittab:
Id:?:initdefault:
When System Successfully boot, it will ask for username and password. But you don't know the root's password. To change the root password you need to boot the system into single user mode. You can pass the kernel arguments from the boot loader.
1. Restart the System.
2. You will get the boot loader GRUB screen.
3. Press a and type 1 or s for single mode ro root=LABEL=/ rhgb queit s
4. System will boot on Single User mode.
5. Use passwd command to change.
6. Press ctrl+d
Does this meet the goal?
Question 2
According the following requirements to create user, user group and the group members:
- A group named admin.
- A user named mary, and belong to admin as the secondary group.
- A user named alice, and belong to admin as the secondary group.
- A user named bobby, bobby’s login shell should be non-interactive. Bobby not belong to admin as the secondary group.
Mary, Alice, bobby users must be set "password" as the user's password.
Solution:
see explanation below.
groupadd admin
useradd -G admin mary
useradd -G admin alice
useradd -s /sbin/nologin bobby
echo "password" | passwd --stdin mary
echo "password" | passwd --stdin alice
echo "password" | passwd --stdin bobby
Does this meet the goal?
- A group named admin.
- A user named mary, and belong to admin as the secondary group.
- A user named alice, and belong to admin as the secondary group.
- A user named bobby, bobby’s login shell should be non-interactive. Bobby not belong to admin as the secondary group.
Mary, Alice, bobby users must be set "password" as the user's password.
Solution:
see explanation below.
groupadd admin
useradd -G admin mary
useradd -G admin alice
useradd -s /sbin/nologin bobby
echo "password" | passwd --stdin mary
echo "password" | passwd --stdin alice
echo "password" | passwd --stdin bobby
Does this meet the goal?
Question 3
Add a new logical partition having size 100MB and create the data which will be the mount point for the new partition.
Solution:
1. Use fdisk /dev/hda-> To create new partition.
2. Type n ->For New partitions
3. It will ask for Logical or Primary Partitions. Press l for logical.
4. It will ask for the Starting Cylinder: Use the Default by pressing Enter
Keys
5. Type the size: +100M you can specify either Last cylinder of size here.
6. Press P to verify the partitions lists and remember the partitions name.
7. Press w to write on partitions table.
8. Either Reboot or use partprobe command.
9. Use mkfs -t ext3 /dev/hda?
OR
1. mke2fs -j /dev/hda? ->To create ext3 filesystem.
2. vi /etc/fstab
3. Write:
/dev/hda? /data ext3 defaults 0 0
4. Verify by mounting on current sessions also: mount /dev/hda? /data
Does this meet the goal?
Solution:
1. Use fdisk /dev/hda-> To create new partition.
2. Type n ->For New partitions
3. It will ask for Logical or Primary Partitions. Press l for logical.
4. It will ask for the Starting Cylinder: Use the Default by pressing Enter
Keys
5. Type the size: +100M you can specify either Last cylinder of size here.
6. Press P to verify the partitions lists and remember the partitions name.
7. Press w to write on partitions table.
8. Either Reboot or use partprobe command.
9. Use mkfs -t ext3 /dev/hda?
OR
1. mke2fs -j /dev/hda? ->To create ext3 filesystem.
2. vi /etc/fstab
3. Write:
/dev/hda? /data ext3 defaults 0 0
4. Verify by mounting on current sessions also: mount /dev/hda? /data
Does this meet the goal?
Question 4
Upgrading the kernel as 2.6.36.7.1, and configure the system to Start the default kernel, keep the old kernel available.
Solution:
# cat /etc/grub.conf
# cd /boot
# lftp it
# get dr/dom/kernel-xxxx.rpm
# rpm -ivh kernel-xxxx.rpm
# vim /etc/grub.conf default=0
Does this meet the goal?
Solution:
# cat /etc/grub.conf
# cd /boot
# lftp it
# get dr/dom/kernel-xxxx.rpm
# rpm -ivh kernel-xxxx.rpm
# vim /etc/grub.conf default=0
Does this meet the goal?
Question 5
Create a logical volume
Create a new logical volume as required:
Name the logical volume as database, belongs to datastore of the volume group, size is 50 PE. Expansion size of each volume in volume group datastore is 16MB.
Use ext3 to format this new logical volume, this logical volume should automatically mount to /mnt/database
Solution:
fdisk -cu /dev/vda// Create a 1G partition, modified when needed
partx –a /dev/vda
pvcreate /dev/vdax
vgcreate datastore /dev/vdax –s 16M
lvcreate– l 50 –n database datastore
mkfs.ext3 /dev/datastore/database
mkdir /mnt/database
mount /dev/datastore/database /mnt/database/ df –Th
vi /etc/fstab
/dev/datastore /database /mnt/database/ ext3 defaults 0 0 mount –a
Restart and check all the questions requirements.
Does this meet the goal?
Create a new logical volume as required:
Name the logical volume as database, belongs to datastore of the volume group, size is 50 PE. Expansion size of each volume in volume group datastore is 16MB.
Use ext3 to format this new logical volume, this logical volume should automatically mount to /mnt/database
Solution:
fdisk -cu /dev/vda// Create a 1G partition, modified when needed
partx –a /dev/vda
pvcreate /dev/vdax
vgcreate datastore /dev/vdax –s 16M
lvcreate– l 50 –n database datastore
mkfs.ext3 /dev/datastore/database
mkdir /mnt/database
mount /dev/datastore/database /mnt/database/ df –Th
vi /etc/fstab
/dev/datastore /database /mnt/database/ ext3 defaults 0 0 mount –a
Restart and check all the questions requirements.
Does this meet the goal?
Question 6
Configure autofs to make sure after login successfully, it has the home directory autofs, which is shared as /rhome/ldapuser40 at the ip: 172.24.40.10. and it also requires that, other ldap users can use the home directory normally.
Solution:
# chkconfig autofs on
# cd /etc/
# vim /etc/auto.master
/rhome /etc/auto.ldap
# cp auto.misc auto.ldap
# vim auto.ladp
ldapuser40 -rw,soft,intr 172.24.40.10:/rhome/ldapuser40
* -rw,soft,intr 172.16.40.10:/rhome/&
# service autofs stop
# server autofs start
# showmount -e 172.24.40.10
# su - ladpuser40
Does this meet the goal?
Solution:
# chkconfig autofs on
# cd /etc/
# vim /etc/auto.master
/rhome /etc/auto.ldap
# cp auto.misc auto.ldap
# vim auto.ladp
ldapuser40 -rw,soft,intr 172.24.40.10:/rhome/ldapuser40
* -rw,soft,intr 172.16.40.10:/rhome/&
# service autofs stop
# server autofs start
# showmount -e 172.24.40.10
# su - ladpuser40
Does this meet the goal?
Question 7
Who ever creates the files/directories on archive group owner should be automatically should be the same group owner of archive.
Solution:
chmod g+s /archive
Verify using: ls -ld /archive Permission should be like:
drwxrws--- 2 root sysuser 4096 Mar 16 18:08 /archive
If SGID bit is set on directory then who every users creates the files on directory group owner automatically
the owner of parent directory.
To set the SGID bit: chmod g+s directory
To Remove the SGID bit: chmod g-s directory
Does this meet the goal?
Solution:
chmod g+s /archive
Verify using: ls -ld /archive Permission should be like:
drwxrws--- 2 root sysuser 4096 Mar 16 18:08 /archive
If SGID bit is set on directory then who every users creates the files on directory group owner automatically
the owner of parent directory.
To set the SGID bit: chmod g+s directory
To Remove the SGID bit: chmod g-s directory
Does this meet the goal?
Question 8
Configure a task: plan to run echo hello command at 14:23 every day.
Solution:
# which echo
# crontab -e
23 14 * * * /bin/echo hello
# crontab -l (Verify)
Does this meet the goal?
Solution:
# which echo
# crontab -e
23 14 * * * /bin/echo hello
# crontab -l (Verify)
Does this meet the goal?
Question 9
Configure your Host Name, IP Address, Gateway and DNS.
Host name: station.domain40.example.com
/etc/sysconfig/network
hostname=abc.com
hostname abc.com
IP Address:172.24.40.40/24
Gateway172.24.40.1
DNS:172.24.40.1
Solution:
# cd /etc/syscofig/network-scripts/
# ls
# vim ifcfg-eth0 (Configure IP Address, Gateway and DNS) IPADDR=172.24.40.40 GATEWAY=172.24.40.1
DNS1=172.24.40.1
# vim /etc/sysconfig/network
(Configure Host Name)
HOSTNAME= station.domain40.example.com
OR
Graphical Interfaces:
System->Preference->Network Connections (Configure IP Address, Gateway and DNS) Vim
/etc/sysconfig/network
(Configure Host Name)
Does this meet the goal?
Host name: station.domain40.example.com
/etc/sysconfig/network
hostname=abc.com
hostname abc.com
IP Address:172.24.40.40/24
Gateway172.24.40.1
DNS:172.24.40.1
Solution:
# cd /etc/syscofig/network-scripts/
# ls
# vim ifcfg-eth0 (Configure IP Address, Gateway and DNS) IPADDR=172.24.40.40 GATEWAY=172.24.40.1
DNS1=172.24.40.1
# vim /etc/sysconfig/network
(Configure Host Name)
HOSTNAME= station.domain40.example.com
OR
Graphical Interfaces:
System->Preference->Network Connections (Configure IP Address, Gateway and DNS) Vim
/etc/sysconfig/network
(Configure Host Name)
Does this meet the goal?
Question 10
Your System is configured in 192.168.0.0/24 Network and your nameserver is 192.168.0.254. Make successfully resolve to server1.example.com.
Solution:
nameserver is specified in question,
1. Vi /etc/resolv.conf
nameserver 192.168.0.254
2. host server1.example.com
Does this meet the goal?
Solution:
nameserver is specified in question,
1. Vi /etc/resolv.conf
nameserver 192.168.0.254
2. host server1.example.com
Does this meet the goal?
Question 11
Create a backup file named /root/backup.tar.bz2, which contains the contents of /usr/local, bar must use the bzip2 compression.
Solution:
cd /usr/local
tar -jcvf /root/backup.tar.bz2*
mkdir /test
tar -jxvf /root/backup.tar.bz2 -C /test/
Does this meet the goal?
Solution:
cd /usr/local
tar -jcvf /root/backup.tar.bz2*
mkdir /test
tar -jxvf /root/backup.tar.bz2 -C /test/
Does this meet the goal?
Question 12
/data Directory is shared from the server1.example.com server. Mount the shared directory that:
Solution:
1. vi /etc/auto.master
/mnt /etc /auto.misc --timeout=50
vi /etc/auto.misc
data -rw,soft,intr server1.example.com:/data
service autofs restart
chkconfig autofs on
When you mount the other filesystem, you should unmount the mounted filesystem, Automount feature of linux helps to mount at access time and after certain seconds, when user unaccess the mounted directory, automatically unmount the filesystem.
/etc/auto.master is the master configuration file for autofs service. When you start the service, it reads the mount point as defined in /etc/auto.master.
Does this meet the goal?
Solution:
1. vi /etc/auto.master
/mnt /etc /auto.misc --timeout=50
vi /etc/auto.misc
data -rw,soft,intr server1.example.com:/data
service autofs restart
chkconfig autofs on
When you mount the other filesystem, you should unmount the mounted filesystem, Automount feature of linux helps to mount at access time and after certain seconds, when user unaccess the mounted directory, automatically unmount the filesystem.
/etc/auto.master is the master configuration file for autofs service. When you start the service, it reads the mount point as defined in /etc/auto.master.
Does this meet the goal?
Question 13
Make a swap partition having 100MB. Make Automatically Usable at System Boot Time.
Solution:
see explanation below.
Use fdisk /dev/hda ->To create new partition.
Type n-> For New partition
It will ask for Logical or Primary Partitions. Press l for logical.
It will ask for the Starting Cylinder: Use the Default by pressing Enter Key.
Type the Size: +100M ->You can Specify either Last cylinder of Size here.
Press P to verify the partitions lists and remember the partitions name. Default System ID is 83 that means Linux Native.
Type t to change the System ID of partition.
Type Partition Number
Type 82 that means Linux Swap.
Press w to write on partitions table.
Either Reboot or use partprobe command.
mkswap /dev/hda? ->To create Swap File system on partition.
swapon /dev/hda? ->To enable the Swap space from partition.
free -m ->Verify Either Swap is enabled or not.
vi /etc/fstab/dev/hda? swap swap defaults 0 0
Reboot the System and verify that swap is automatically enabled or not.
Does this meet the goal?
Solution:
see explanation below.
Use fdisk /dev/hda ->To create new partition.
Type n-> For New partition
It will ask for Logical or Primary Partitions. Press l for logical.
It will ask for the Starting Cylinder: Use the Default by pressing Enter Key.
Type the Size: +100M ->You can Specify either Last cylinder of Size here.
Press P to verify the partitions lists and remember the partitions name. Default System ID is 83 that means Linux Native.
Type t to change the System ID of partition.
Type Partition Number
Type 82 that means Linux Swap.
Press w to write on partitions table.
Either Reboot or use partprobe command.
mkswap /dev/hda? ->To create Swap File system on partition.
swapon /dev/hda? ->To enable the Swap space from partition.
free -m ->Verify Either Swap is enabled or not.
vi /etc/fstab/dev/hda? swap swap defaults 0 0
Reboot the System and verify that swap is automatically enabled or not.
Does this meet the goal?
Question 14
Search a String
Find out all the columns that contains the string seismic within /usr/share/dict/words, then copy all these columns to /root/lines.tx in original order, there is no blank line, all columns must be the accurate copy of the original columns.
Solution:
grep seismic /usr/share/dict/words> /root/lines.txt
Does this meet the goal?
Find out all the columns that contains the string seismic within /usr/share/dict/words, then copy all these columns to /root/lines.tx in original order, there is no blank line, all columns must be the accurate copy of the original columns.
Solution:
grep seismic /usr/share/dict/words> /root/lines.txt
Does this meet the goal?
Question 15
Find the files owned by harry, and copy it to catalog: /opt/dir
Solution:
# cd /opt/
# mkdir dir
# find / -user harry -exec cp -rfp {} /opt/dir/ ;
Does this meet the goal?
Solution:
# cd /opt/
# mkdir dir
# find / -user harry -exec cp -rfp {} /opt/dir/ ;
Does this meet the goal?
Question 16
Find all lines in the file /usr/share/dict/words that contain the string seismic. Put a copy of all these lines in their original order in the file /root/wordlist. /root/wordlist should contain no empty lines and all lines must be exact copies of the original lines in /usr/share/dict/words.
Solution:
grep seismic /usr/share/dict/words> /root/wordlist
Does this meet the goal?
Solution:
grep seismic /usr/share/dict/words> /root/wordlist
Does this meet the goal?
Question 17
You are a System administrator. Using Log files very easy to monitor the system. Now there are 50 servers running as Mail, Web, Proxy, DNS services etc. You want to centralize the logs from all servers into on LOG Server. How will you configure the LOG Server to accept logs from remote host?
Solution:
By default, system accept the logs only generated from local host. To accept the Log from other host configure:
vi /etc/sysconfig/syslog SYSLOGD_OPTIONS="-m 0 -r"
Where
-m 0 disables 'MARK' messages.
-r enables logging from remote machines
-x disables DNS lookups on messages received with -r
service syslog restart
Does this meet the goal?
Solution:
By default, system accept the logs only generated from local host. To accept the Log from other host configure:
vi /etc/sysconfig/syslog SYSLOGD_OPTIONS="-m 0 -r"
Where
-m 0 disables 'MARK' messages.
-r enables logging from remote machines
-x disables DNS lookups on messages received with -r
service syslog restart
Does this meet the goal?
Question 18
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.
Solution:
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/&
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.
Does this meet the goal?
Solution:
use the authconfig --nisserver=
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/&
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.
Does this meet the goal?
Question 19
One Logical Volume named lv1 is created under vg0. The Initial Size of that Logical Volume is 100MB. Now you required the size 500MB. Make successfully the size of that Logical Volume 500M without losing any data. As well as size should be increased online.
Solution:
The LVM system organizes hard disks into Logical Volume (LV) groups. Essentially, physical hard disk partitions (or possibly RAID arrays) are set up in a bunch of equal sized chunks known as Physical Extents (PE). As there are several other concepts associated with the LVM system, let's start with some basic definitions:
Physical Volume (PV) is the standard partition that you add to the LVM mix. Normally, a physical volume is a standard primary or logical partition. It can also be a RAID array.
Physical Extent (PE) is a chunk of disk space. Every PV is divided into a number of equal sized PEs. Every PE in a LV group is the same size. Different LV groups can have different sized PEs.
Logical Extent (LE) is also a chunk of disk space. Every LE is mapped to a specific PE.
Logical Volume (LV) is composed of a group of LEs. You can mount a file system such as /home and /var on an LV.
Volume Group (VG) is composed of a group of LVs. It is the organizational group for LVM. Most of the commands that you'll use apply to a specific VG.
Verify the size of Logical Volume: lvdisplay /dev/vg0/lv1
Verify the Size on mounted directory: df -h or df -h mounted directory name
Use: lvextend -L+400M /dev/vg0/lv1
ext2online -d /dev/vg0/lv1 to bring extended size online.
Again Verify using lvdisplay and df -h command.
Does this meet the goal?
Solution:
The LVM system organizes hard disks into Logical Volume (LV) groups. Essentially, physical hard disk partitions (or possibly RAID arrays) are set up in a bunch of equal sized chunks known as Physical Extents (PE). As there are several other concepts associated with the LVM system, let's start with some basic definitions:
Physical Volume (PV) is the standard partition that you add to the LVM mix. Normally, a physical volume is a standard primary or logical partition. It can also be a RAID array.
Physical Extent (PE) is a chunk of disk space. Every PV is divided into a number of equal sized PEs. Every PE in a LV group is the same size. Different LV groups can have different sized PEs.
Logical Extent (LE) is also a chunk of disk space. Every LE is mapped to a specific PE.
Logical Volume (LV) is composed of a group of LEs. You can mount a file system such as /home and /var on an LV.
Volume Group (VG) is composed of a group of LVs. It is the organizational group for LVM. Most of the commands that you'll use apply to a specific VG.
Verify the size of Logical Volume: lvdisplay /dev/vg0/lv1
Verify the Size on mounted directory: df -h or df -h mounted directory name
Use: lvextend -L+400M /dev/vg0/lv1
ext2online -d /dev/vg0/lv1 to bring extended size online.
Again Verify using lvdisplay and df -h command.
Does this meet the goal?
Question 20
Create User Account.
Create the following user, group and group membership:
Adminuser group
User natasha, using adminuser as a sub group
User Harry, also using adminuser as a sub group
User sarah, can not access the SHELL which is interactive in the system, and is not a member of adminuser, natashaharrysarah password is redhat.
Solution:
groupadd adminuser
useradd natasha -G adminuser
useradd haryy -G adminuser
useradd sarah -s /sbin/nologin
Passwd user name // to modify password or echo redhat | passwd --stdin user name id natasha // to view user group.
Does this meet the goal?
Create the following user, group and group membership:
Adminuser group
User natasha, using adminuser as a sub group
User Harry, also using adminuser as a sub group
User sarah, can not access the SHELL which is interactive in the system, and is not a member of adminuser, natashaharrysarah password is redhat.
Solution:
groupadd adminuser
useradd natasha -G adminuser
useradd haryy -G adminuser
useradd sarah -s /sbin/nologin
Passwd user name // to modify password or echo redhat | passwd --stdin user name id natasha // to view user group.
Does this meet the goal?