Scribd
Upload
45 views6 pages

Red Hat RHCSA EX200 Exam Tasks Guide

The document outlines tasks for the Red Hat RHCSA Certification Exam EX200, detailing various system administration tasks to be performed on Node1 and Node2 servers. Tasks include configuring cron jobs, managing file permissions, setting up NTP synchronization, creating logical volumes, and configuring user accounts and groups. The document serves as a guide for candidates to prepare for the certification exam by practicing these essential Linux administration skills.

Uploaded by

79241015
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
45 views6 pages

Red Hat RHCSA EX200 Exam Tasks Guide

The document outlines tasks for the Red Hat RHCSA Certification Exam EX200, detailing various system administration tasks to be performed on Node1 and Node2 servers. Tasks include configuring cron jobs, managing file permissions, setting up NTP synchronization, creating logical volumes, and configuring user accounts and groups. The document serves as a guide for candidates to prepare for the certification exam by practicing these essential Linux administration skills.

Uploaded by

79241015
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

Red Hat RHCSA Certification Exam EX200 Free Dumps Are Below For Checking

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

24. 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.

29. Part 1 (on Node1 Server)

Task 10 [Configuring NTP/Time Synchronization]

Configure your system so that it is an NTP client of [Link]

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

35. 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

1.

Notes:

NFS NFS [Link]:/var/ftp/pub/rhel6/dvd


YUM [Link]
ldap http//[Link]/pub/EXAMPLE-CA-CERT
Install dialog package.

[Link] a FTP server, and request to anonymous download from /var/ftp/pub


catalog. (it needs you to configure yum direct to the already existing file
server.)

3. Configure /var/tmp/fstab Permission.


Copy the file /etc/fstab to /var/tmp/fstab. Configure var/tmp/fstab permissions as
the following:
Owner of the file /var/tmp/fstab is Root, belongs to group root File /var/tmp/fstab
cannot be executed by any user
User natasha can read and write /var/tmp/fstab User harry cannot read and write
/var/tmp/fstab
All other users (present and future) can read var/tmp/fstab.

4. According the following requirements to create a local directory /common/admin.


✑ This directory has admin group.
✑ This directory has read, write and execute permissions for all admin group
members.
✑ Other groups and users don’t have any permissions.
✑ All the documents or directories created in the/common/admin are automatically
inherit the admin group.

5. 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.

6. Add users: user2, user3.


The Additional group of the two users: user2, user3 is the admin group Password:
redhat

7. A YUM repository has been provided at


[Link]
Configure your system to use this location as a default repository.

8. Create a new logical volume according to the following requirements:


The logical volume is named database and belongs to the datastore volume group and
has a size of 50 extents.
Logical volumes in the datastore volume group should have an extent size of 16 MB.
Format the new logical volume with a ext3 filesystem.
The logical volume should be automatically mounted under /mnt/database at system
boot time.

9. Find all the files or directories with Lucy as the owner, and copy to
/tmp/findfiles directory.

10. Upgrading the kernel as [Link].1, and configure the system to Start the
default kernel, keep the old kernel available.

11. Locate all the files owned by ira and copy them to the / root/findresults
directory.

12. Configure your web services, download from

[Link] And the services must be still


running after
system rebooting.

13. SELinux must be running in the Enforcing mode.

14. Create a volume group, and set the size is 500M, the size of single PE is 16M.
Create logical volume named lv0 in this volume group, set size is 20 PE, make it as
ext3 file system, and mounted automatically under data.

15. Create a backup file named /root/[Link].bz2, which contains the contents of
/usr/local, bar must use the bzip2 compression.

16. vi /etc/[Link] net.ipv4.ip_forward=1

17. Install the appropriate kernel update from

[Link]
The following criteria must also be met:
The updated kernel is the default kernel when the system is rebooted
The original kernel remains available and bootable on the system

18. Make on /archive directory that only the user owner and group owner member can
fully access.

19. Create a 2G swap partition which take effect automatically at boot-start, and
it should not affect the original swap partition.

gdisk -l /dev/sdb
n
enter
enter
+2G
p
w

20. Configure the system synchronous as [Link].

Part 2 (on Node2 Server)

Task 7 [Implementing Advanced Storage Features]

21. 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

22. SELinux must run in force mode.

23. Create a 2G swap partition which take effect automatically at boot-start, and
it should not affect the original swap partition.
25. 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.

26. Open kmcrl value of 5, and can verify in /proc/ cmdline

27. 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.

28. User mary must configure a task.

Requirement: The local time at 14:23 every day echo "Hello World.".

30. In the system, mounted the iso image /root/[Link] to/mnt/iso directory.
And enable automatically mount (permanent mount) after restart system.

31. Configure a task: plan to run echo "file" command at 14:23 every day.

32. Configure the verification mode of your host account and the password as LDAP.
And it can login successfully through ldapuser40. The password is set as
"password". And the certificate can be downloaded from [Link]
After the user logs on the user has no host directory unless you configure the
autofs in the following questions.

33. Configure iptables, there are two domains in the network, the address of local
domain is [Link]/16 other domain is [Link]/16, now refuse domain
[Link]/16 to access the server.

34. 168.1.0/24 Network's Host.


36. 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.

37. Configure autofs.

Configure the autofs automatically mount to the home directory of LDAP, as


required:
[Link] use NFS to share the home to your system. This file
system contains a preconfigured home directory of user ldapuserX.
Home directory of ldapuserX is:
[Link] /home/guests/ldapuser
Home directory of ldapuserX should automatically mount to the ldapuserX of the
local /home/guests Home directory’s write permissions must be available for users
ldapuser1’s password is password

38. Add a new logical partition having size 100MB and create the data which will be
the mount point for the new partition.

39. Create one partitions having size 100MB and mount it on data.

40. 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)

41. Add admin group and set gid=600

43. Who ever creates the files/directories on archive group owner should be
automatically should be the same group owner of archive.

44. Configure autofs to automount the home directories of LDAP users as follows:

[Link] NFS-exports /home to your system.

This filesystem contains a pre-configured home directory for the user ldapuser11
ldapuser11's home directory is [Link] /rhome/ldapuser11
ldapuser11's home directory should be automounted locally beneath /rhome as
/rhome/ldapuser11
Home directories must be writable by their users

ldapuser11's password is 'password'.

45. Find the files owned by harry, and copy it to catalog: /opt/dir

# find / -user harry -exec cp -rfp {} /opt/dir

46. The firewall must be open.

47. Create a backup file named /root/[Link].bz2, contains the content of


/usr/local, tar must use bzip2 to compress.

49. One Logical Volume named /dev/test0/testvolume1 is created. The initial Size of
that disk is 100MB now you required more 200MB. Increase the size of Logical
Volume, size should be increase on online.

42. 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

50. 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

Common questions

Powered by AI

First, create a physical volume using `pvcreate`, a volume group with `vgcreate datastore`, and then a logical volume with `lvcreate -L 800M -n database datastore`. Create a filesystem with `mkfs.ext3 /dev/datastore/database`. To auto-mount, add an entry in `/etc/fstab`: `/dev/datastore/database /mnt/database ext3 defaults 0 0`. Use `mount -a` to verify and ensure it mounts on boot .

Configure autofs by editing `/etc/auto.master`, adding `/rhome /etc/auto.ldap` where `/etc/auto.ldap` specifies `ldapuser11 -rw,soft,rsize=8192,wsize=8192,nosuid server.domain11.example.com:/rhome/ldapuser11`. Reload the autofs service with `systemctl restart autofs`. This setup allows LDAP home directories to mount on-demand, maintaining scalability and reducing resource usage on storage management .

Thin-provisioning allocates storage on-demand instead of upfront, optimizing space usage, especially in environments where full capacity isn't used immediately. To implement, create a thin pool with `lvcreate -L size -T volgroup/thinpool` and then provision volumes like `lvcreate -V size -T volgroup/thinpool -n thinvolume`. Risks include over-provisioning, where sum of volumes exceeds physical space, leading to potential write failures. Monitoring is critical to prevent data loss .

In enforcing mode, SELinux enforces its security policy, restricting access based on the rules defined in its policy. This means unauthorized processes cannot access files, sockets, or other resources unless explicitly allowed. This adds a robust layer of security by preventing privilege escalations and lateral attacks, ensuring that even if a service is compromised, it cannot easily spread or perform unauthorized actions .

When creating a backup with bzip2, ensure you select files that do not need to be in-use or locked, such as `/usr/local`. Use `tar -cjf /root/backup.tar.bz2 /usr/local` to create the compressed backup. Consider system resource availability as bzip2 is CPU intensive; avoid peak usage times. Test by extracting the backup to verify integrity with `tar -xjf`. Scripting and scheduling this process regularly will maintain up-to-date recoverable backups .

During boot, interrupt the boot sequence by pressing 'e' on the GRUB menu. Add `rd.break` to the kernel parameters. Continue booting by pressing `Ctrl+x`. Remount the filesystem in read/write mode with `mount -o remount,rw /sysroot`. Change root with `chroot /sysroot` and reset the password using `passwd`. Finally, ensure SELinux relabeling by creating `.autorelabel` file before rebooting with `touch /.autorelabel; exit; reboot` .

To configure a cron job for user 'natasha' to run daily at 14:23 and every two minutes, you need to edit the user's crontab file by executing `crontab -e` as 'natasha'. Add two entries: `23 14 * * * /bin/echo hello 24` for the daily run at local time 14:23, and `*/2 * * * * /bin/echo hello 24` for the task every two minutes. To validate the configuration, check the crontab by using `crontab -l` to ensure entries exist and monitor system logs or create a log entry in the job to verify execution .

To configure NTP, install the NTP package and edit the `/etc/ntp.conf` file, adding `server utility.domain15.example.com`. Start the `ntpd` service with `systemctl start ntpd` and enable it to start at boot with `systemctl enable ntpd`. Use `timedatectl set-timezone <Your/Timezone>` to set the correct timezone. Correct timezone ensures the local system time aligns with NTP server time, critical for time-based operations like cron jobs, log timestamps, and compliance adherence .

Iptables rules can be configured to manage network access; for example, denying 172.25.0.0/16 with `iptables -A INPUT -s 172.25.0.0/16 -j DROP`. This restricts access from the domain, safeguarding the server from potential network threats. Configuring iptables allows administrators to enforce security policies at the network level, fine-tuning who can access resources .

To configure /var/tmp/fstab securely, first ensure the file's owner is set to root using `chown root:root /var/tmp/fstab`. Remove execute permissions for all with `chmod a-x /var/tmp/fstab`. Grant 'natasha' read and write permissions with `setfacl -m u:natasha:rw /var/tmp/fstab` and restrict 'harry' by setting `setfacl -m u:harry:--- /var/tmp/fstab`. This setup ensures only authorized access as per the requirements .

You might also like