McAfee-Secured Website

Exam Bundle

Exam Code: EX200

Exam Name Red Hat Certified System Administrator (RHCSA)

Certification Provider: RedHat

Corresponding Certification: RHCSA

RedHat EX200 Bundle $44.99

100% RedHat EX200 Guaranteed Success With Testking Training Materials

Get Real EX200 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    EX200 Questions & Answers

    111 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual EX200 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • EX200 Video Course

    EX200 Video Course

    71 Video Lectures

    EX200 Video Course is developed by RedHat Professionals to help you pass the EX200 exam.

    Description

    This course will improve your knowledge and skills required to pass Red Hat Certified System Administrator (RHCSA) exam.
  • Study Guide

    EX200 Study Guide

    1601 PDF Pages

    Developed by industry experts, this 1601-page guide spells out in painstaking detail all of the information you need to ace EX200 exam.

Red Hat Certified System Administrator (RHCSA) (EX200) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    111 Questions

    $124.99
  • EX200 Video Course

    Video Course

    71 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1601 PDF Pages

    $29.99

RedHat EX200 Practice Test 19

Question 180

For this Linux administration lab: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. Which safety and lifecycle check best prevents the same problem returning?

  1. Include a full storage dependency diagram in change requests.
  2. Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot.
  3. Make disk identification a mandatory gate; never run `mklabel` on a disk with live data.
  4. Inspect device signatures and mount holders before PV creation.

Explanation

Correct Answer

D:

Inspect device signatures and mount holders before PV creation. This guards against recurrence of: LVM physical volumes carry metadata that lets volume groups manage underlying extents. Confirm the lab's final state by: `pvs /dev/vdb1` shows a physical volume and no other disk was initialized.

Incorrect Answers

A:

Include a full storage dependency diagram in change requests. That control is best suited to a separate scenario: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. It is not the best safeguard for the current mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

B:

Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot. That control is best suited to a separate scenario: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It is not the best safeguard for the current mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

C:

Make disk identification a mandatory gate; never run `mklabel` on a disk with live data. That control is best suited to a separate scenario: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. It is not the best safeguard for the current mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

Question 181

A student working on a local virtualization classroom receives this assignment: A student tries to unmount an NFS training mount while another process has its current directory inside it. Which answer gives the correct practical approach?

  1. Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM.
  2. Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.
  3. Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.
  4. Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.

Explanation

Correct Answer

B:

Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`. This directly addresses the lab target: A student tries to unmount an NFS training mount while another process has its current directory inside it. The underlying behavior is: A busy mount cannot be detached normally while processes retain open references. Verification: `findmnt /mnt/labnfs` no longer reports the mount and no nonlab processes were terminated.

Incorrect Answers

A:

Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM. This is an appropriate step for a DIFFERENT exercise, specifically: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It does not address the required lab state, whose mechanism is: A busy mount cannot be detached normally while processes retain open references.

C:

Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted. This is an appropriate step for a DIFFERENT exercise, specifically: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. It does not address the required lab state, whose mechanism is: A busy mount cannot be detached normally while processes retain open references.

D:

Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports. This is an appropriate step for a DIFFERENT exercise, specifically: A large remote home-directory NFS tree should mount on demand rather than all at login. It does not address the required lab state, whose mechanism is: A busy mount cannot be detached normally while processes retain open references.

Question 182

You have attempted this task on a local virtualization classroom: A student tries to unmount an NFS training mount while another process has its current directory inside it. Which command output or observation best confirms its success?

  1. The verification returns no invalid-entry errors before the reboot and the mount becomes active.
  2. The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted.
  3. `findmnt /mnt/labnfs` no longer reports the mount and no nonlab processes were terminated.
  4. A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data.

Explanation

Correct Answer

C:

`findmnt /mnt/labnfs` no longer reports the mount and no nonlab processes were terminated. This check confirms the expected effect of: Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`. It distinguishes the intended result from the original failure mechanism: A busy mount cannot be detached normally while processes retain open references.

Incorrect Answers

A:

The verification returns no invalid-entry errors before the reboot and the mount becomes active. That verifies a separate lab task: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It does not validate the implementation required here: Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.

B:

The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted. That verifies a separate lab task: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. It does not validate the implementation required here: Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.

D:

A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data. That verifies a separate lab task: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. It does not validate the implementation required here: Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.

Question 183

Troubleshoot the following RHEL 10 lab situation: A student tries to unmount an NFS training mount while another process has its current directory inside it. Identify the key Linux mechanism behind the issue.

  1. Interoperable FAT filesystems differ from XFS, ext4 and their Unix permissions.
  2. Incorrect persistent mount definitions can delay boot or prevent expected units from activating.
  3. XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.
  4. A busy mount cannot be detached normally while processes retain open references.

Explanation

Correct Answer

D:

A busy mount cannot be detached normally while processes retain open references. This explains the task's initial state: A student tries to unmount an NFS training mount while another process has its current directory inside it. The supported lab action is: Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.

Incorrect Answers

A:

Interoperable FAT filesystems differ from XFS, ext4 and their Unix permissions. This mechanism applies to another scenario: A USB-compatible training partition must use the VFAT filesystem, but the operator formats it as XFS instead. The given lab state instead requires the more specific cause in the correct choice.

B:

Incorrect persistent mount definitions can delay boot or prevent expected units from activating. This mechanism applies to another scenario: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. The given lab state instead requires the more specific cause in the correct choice.

C:

XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration. This mechanism applies to another scenario: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. The given lab state instead requires the more specific cause in the correct choice.

Question 184

Following lab verification, document the preventive or persistence-oriented procedure for: A student tries to unmount an NFS training mount while another process has its current directory inside it. Which practice is most suitable?

  1. Inspect mount users and coordinate termination before maintenance unmounts.
  2. Perform filesystem-aware resize following every block extension and confirm available bytes.
  3. Verify server export reachability and intended access controls before persistent NFS configuration.
  4. Inspect the entire path before changing only the final file's mode.

Explanation

Correct Answer

A:

Inspect mount users and coordinate termination before maintenance unmounts. This guards against recurrence of: A busy mount cannot be detached normally while processes retain open references. Confirm the lab's final state by: `findmnt /mnt/labnfs` no longer reports the mount and no nonlab processes were terminated.

Incorrect Answers

B:

Perform filesystem-aware resize following every block extension and confirm available bytes. That control is best suited to a separate scenario: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. It is not the best safeguard for the current mechanism: A busy mount cannot be detached normally while processes retain open references.

C:

Verify server export reachability and intended access controls before persistent NFS configuration. That control is best suited to a separate scenario: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. It is not the best safeguard for the current mechanism: A busy mount cannot be detached normally while processes retain open references.

D:

Inspect the entire path before changing only the final file's mode. That control is best suited to a separate scenario: A file under `/srv/team` is readable by its owner but inaccessible to the `analysts` group despite the group being listed in the account database. It is not the best safeguard for the current mechanism: A busy mount cannot be detached normally while processes retain open references.

Question 185

On a nonproduction Linux administration sandbox, perform the following practical task: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. Which action should be carried out after confirming the lab prerequisites?

  1. Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference.
  2. Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.
  3. Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.
  4. Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.

Explanation

Correct Answer

C:

Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system. This directly addresses the lab target: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. The underlying behavior is: Writing unit files alone does not start or enable a new timer. Verification: `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.

Incorrect Answers

A:

Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference. This is an appropriate step for a DIFFERENT exercise, specifically: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. It does not address the required lab state, whose mechanism is: Writing unit files alone does not start or enable a new timer.

B:

Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources. This is an appropriate step for a DIFFERENT exercise, specifically: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. It does not address the required lab state, whose mechanism is: Writing unit files alone does not start or enable a new timer.

D:

Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement. This is an appropriate step for a DIFFERENT exercise, specifically: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It does not address the required lab state, whose mechanism is: Writing unit files alone does not start or enable a new timer.

Question 186

The lab examiner asks for evidence after this assignment: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. What is the decisive verification step?

  1. `crontab -u reporter -l` contains the job and generated files are owned by `reporter` rather than root.
  2. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.
  3. The source list displays the replacement server and offset converges within the intended test tolerance.
  4. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.

Explanation

Correct Answer

D:

`systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit. This check confirms the expected effect of: Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system. It distinguishes the intended result from the original failure mechanism: Writing unit files alone does not start or enable a new timer.

Incorrect Answers

A:

`crontab -u reporter -l` contains the job and generated files are owned by `reporter` rather than root. That verifies a separate lab task: A recurring cron script runs as root because it was inserted into the system crontab, while it should run as a least-privilege reporting account. It does not validate the implementation required here: Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.

B:

`systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot. That verifies a separate lab task: A daemon is started manually after package installation but must be reliably available after reboots. It does not validate the implementation required here: Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.

C:

The source list displays the replacement server and offset converges within the intended test tolerance. That verifies a separate lab task: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It does not validate the implementation required here: Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.

Question 187

A training host has this situation: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. Which system behavior best explains the original failure or risk?

  1. Writing unit files alone does not start or enable a new timer.
  2. A scheduled job executes with the identity of the scheduler's configured user.
  3. A running time daemon without valid reachable sources cannot synchronize clocks.
  4. Runtime activation and boot-time activation are separate systemd states.

Explanation

Correct Answer

A:

Writing unit files alone does not start or enable a new timer. This explains the task's initial state: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. The supported lab action is: Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.

Incorrect Answers

B:

A scheduled job executes with the identity of the scheduler's configured user. This mechanism applies to another scenario: A recurring cron script runs as root because it was inserted into the system crontab, while it should run as a least-privilege reporting account. The given lab state instead requires the more specific cause in the correct choice.

C:

A running time daemon without valid reachable sources cannot synchronize clocks. This mechanism applies to another scenario: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. The given lab state instead requires the more specific cause in the correct choice.

D:

Runtime activation and boot-time activation are separate systemd states. This mechanism applies to another scenario: A daemon is started manually after package installation but must be reliably available after reboots. The given lab state instead requires the more specific cause in the correct choice.

Question 188

A student has implemented the following configuration: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. What repeatable control best reduces regressions or unsafe changes?

  1. Maintain approved time servers and monitor drift/offset after network changes.
  2. Include unit reload, activation and next-fire-time checks in release tasks.
  3. Test full cold-boot readiness, not just whether a unit says active.
  4. Document persistent default target configuration separately from runtime target switching.

Explanation

Correct Answer

B:

Include unit reload, activation and next-fire-time checks in release tasks. This guards against recurrence of: Writing unit files alone does not start or enable a new timer. Confirm the lab's final state by: `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.

Incorrect Answers

A:

Maintain approved time servers and monitor drift/offset after network changes. That control is best suited to a separate scenario: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. It is not the best safeguard for the current mechanism: Writing unit files alone does not start or enable a new timer.

C:

Test full cold-boot readiness, not just whether a unit says active. That control is best suited to a separate scenario: A service is enabled and active, but the actual application fails after boot because a required mount is not available in time. It is not the best safeguard for the current mechanism: Writing unit files alone does not start or enable a new timer.

D:

Document persistent default target configuration separately from runtime target switching. That control is best suited to a separate scenario: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. It is not the best safeguard for the current mechanism: Writing unit files alone does not start or enable a new timer.

Question 189

You are responsible for a test RHEL10 instance. The required hands-on outcome is: The lab interface is assigned the right IP but the host cannot reach an off-subnet gateway due to an incorrect default route. Select the most appropriate implementation step.

  1. After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.
  2. Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.
  3. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.
  4. Review `ip route`, then set the approved NetworkManager `ipv4.gateway` and route fields on the active profile.

Explanation

Correct Answer

D:

Review `ip route`, then set the approved NetworkManager `ipv4.gateway` and route fields on the active profile. This directly addresses the lab target: The lab interface is assigned the right IP but the host cannot reach an off-subnet gateway due to an incorrect default route. The underlying behavior is: A valid local interface address does not automatically provide off-subnet routing. Verification: `ip route get 203.0.113.10` selects the correct gateway and the intended test connection succeeds.

Incorrect Answers

A:

After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule. This is an appropriate step for a DIFFERENT exercise, specifically: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. It does not address the required lab state, whose mechanism is: A valid local interface address does not automatically provide off-subnet routing.

B:

Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured. This is an appropriate step for a DIFFERENT exercise, specifically: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It does not address the required lab state, whose mechanism is: A valid local interface address does not automatically provide off-subnet routing.

C:

Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. It does not address the required lab state, whose mechanism is: A valid local interface address does not automatically provide off-subnet routing.

Question 190

After a lab configuration change, verify: The lab interface is assigned the right IP but the host cannot reach an off-subnet gateway due to an incorrect default route. Which result most directly proves the desired system state?

  1. `ip route get 203.0.113.10` selects the correct gateway and the intended test connection succeeds.
  2. The profile reflects changed settings and existing remote management remains recoverable.
  3. An authorized client connects and the correct zone reports the service or port.
  4. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.

Explanation

Correct Answer

A:

`ip route get 203.0.113.10` selects the correct gateway and the intended test connection succeeds. This check confirms the expected effect of: Review `ip route`, then set the approved NetworkManager `ipv4.gateway` and route fields on the active profile. It distinguishes the intended result from the original failure mechanism: A valid local interface address does not automatically provide off-subnet routing.

Incorrect Answers

B:

The profile reflects changed settings and existing remote management remains recoverable. That verifies a separate lab task: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not validate the implementation required here: Review `ip route`, then set the approved NetworkManager `ipv4.gateway` and route fields on the active profile.

C:

An authorized client connects and the correct zone reports the service or port. That verifies a separate lab task: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. It does not validate the implementation required here: Review `ip route`, then set the approved NetworkManager `ipv4.gateway` and route fields on the active profile.

D:

After reconnect or reboot `nmcli con show` and `ip addr` still report the address. That verifies a separate lab task: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not validate the implementation required here: Review `ip route`, then set the approved NetworkManager `ipv4.gateway` and route fields on the active profile.