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 15

Question 140

A student has implemented the following configuration: A trainee needs to delete one unused partition on a disposable GPT disk but proposes erasing the whole disk. What repeatable control best reduces regressions or unsafe changes?

  1. Include a full storage dependency diagram in change requests.
  2. Confirm exact partition number, holders and backups before partition deletion.
  3. Plan allocations with PV placement requirements as well as aggregate capacity.
  4. Document whether requests are byte sizes or extents before provisioning LVM.

Explanation

Correct Answer

B:

Confirm exact partition number, holders and backups before partition deletion. This guards against recurrence of: Removing one GPT partition differs from overwriting the entire partition table. Confirm the lab's final state by: `parted -s /dev/vdb print` no longer lists partition 2 and remaining partition metadata is intact.

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: Removing one GPT partition differs from overwriting the entire partition table.

C:

Plan allocations with PV placement requirements as well as aggregate capacity. That control is best suited to a separate scenario: A training PV reports little free space while its VG appears to have ample total capacity across a second PV. It is not the best safeguard for the current mechanism: Removing one GPT partition differs from overwriting the entire partition table.

D:

Document whether requests are byte sizes or extents before provisioning LVM. That control is best suited to a separate scenario: An LV should consume precisely 20% of remaining free extents for a training scratch workload. It is not the best safeguard for the current mechanism: Removing one GPT partition differs from overwriting the entire partition table.

Question 141

You are responsible for a test RHEL10 instance. The required hands-on outcome is: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. Select the most appropriate implementation step.

  1. Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.
  2. Check the server export permissions, UID/GID mapping and client ownership, then correct authorized permissions on the exporting server.
  3. Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.
  4. Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM.

Explanation

Correct Answer

D:

Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM. This directly addresses the lab target: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. The underlying behavior is: Filesystem presence alone does not attach it into the directory namespace. Verification: `findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works.

Incorrect Answers

A:

Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements. This is an appropriate step for a DIFFERENT exercise, specifically: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It does not address the required lab state, whose mechanism is: Filesystem presence alone does not attach it into the directory namespace.

B:

Check the server export permissions, UID/GID mapping and client ownership, then correct authorized permissions on the exporting server. This is an appropriate step for a DIFFERENT exercise, specifically: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. It does not address the required lab state, whose mechanism is: Filesystem presence alone does not attach it into the directory namespace.

C:

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: Filesystem presence alone does not attach it into the directory namespace.

Question 142

After a lab configuration change, verify: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. Which result most directly proves the desired system state?

  1. `findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works.
  2. A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data.
  3. `blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata.
  4. A simulated server outage does not block the expected system boot and access after recovery mounts normally.

Explanation

Correct Answer

A:

`findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works. This check confirms the expected effect of: Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM. It distinguishes the intended result from the original failure mechanism: Filesystem presence alone does not attach it into the directory namespace.

Incorrect Answers

B:

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: Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM.

C:

`blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata. That verifies a separate lab task: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. It does not validate the implementation required here: Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM.

D:

A simulated server outage does not block the expected system boot and access after recovery mounts normally. That verifies a separate lab task: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It does not validate the implementation required here: Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM.

Question 143

In an EX200-style practice lab, this condition exists: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. Which explanation correctly identifies the underlying issue?

  1. Increasing block-device capacity does not automatically grow the filesystem metadata.
  2. Filesystem presence alone does not attach it into the directory namespace.
  3. NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.
  4. ext4 filesystem capacity has a separate resize operation from LVM block capacity.

Explanation

Correct Answer

B:

Filesystem presence alone does not attach it into the directory namespace. This explains the task's initial state: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. The supported lab action is: Create `/srv/archive` and run `mount /dev/vg_training/lv_archive /srv/archive` on the disposable VM.

Incorrect Answers

A:

Increasing block-device capacity does not automatically grow the filesystem metadata. This mechanism applies to another scenario: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. The given lab state instead requires the more specific cause in the correct choice.

C:

NFS access depends on remote export policy and identity mapping in addition to client-side mode bits. This mechanism applies to another scenario: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. The given lab state instead requires the more specific cause in the correct choice.

D:

ext4 filesystem capacity has a separate resize operation from LVM block capacity. This mechanism applies to another scenario: An ext4 training LV was expanded but file capacity remains unchanged. The given lab state instead requires the more specific cause in the correct choice.

Question 144

After completing this practical task on a test RHEL10 instance: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. Which operational safeguard helps keep the result correct and safe?

  1. Inspect mount users and coordinate termination before maintenance unmounts.
  2. Validate map syntax and restart/enable autofs after controlled changes.
  3. Configure an appropriate persistent mount separately after runtime testing.
  4. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.

Explanation

Correct Answer

C:

Configure an appropriate persistent mount separately after runtime testing. This guards against recurrence of: Filesystem presence alone does not attach it into the directory namespace. Confirm the lab's final state by: `findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works.

Incorrect Answers

A:

Inspect mount users and coordinate termination before maintenance unmounts. That control is best suited to a separate scenario: A student tries to unmount an NFS training mount while another process has its current directory inside it. It is not the best safeguard for the current mechanism: Filesystem presence alone does not attach it into the directory namespace.

B:

Validate map syntax and restart/enable autofs after controlled changes. That control is best suited to a separate scenario: A large remote home-directory NFS tree should mount on demand rather than all at login. It is not the best safeguard for the current mechanism: Filesystem presence alone does not attach it into the directory namespace.

D:

Treat fstab modifications as high-impact and test mount behavior while a recovery console is available. That control is best suited to a separate scenario: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It is not the best safeguard for the current mechanism: Filesystem presence alone does not attach it into the directory namespace.

Question 145

Lab exercise on an isolated enterprise lab VM: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.
  2. Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance.
  3. Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.
  4. Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.

Explanation

Correct Answer

A:

Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate. This directly addresses the lab target: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. The underlying behavior is: The Persistent option handles missed calendar timer events differently from regular cron execution. Verification: After a simulated missed schedule, the service runs on next startup and `systemctl list-timers` shows a new next trigger.

Incorrect Answers

B:

Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance. This is an appropriate step for a DIFFERENT exercise, specifically: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. It does not address the required lab state, whose mechanism is: The Persistent option handles missed calendar timer events differently from regular cron execution.

C:

Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`. This is an appropriate step for a DIFFERENT exercise, specifically: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. It does not address the required lab state, whose mechanism is: The Persistent option handles missed calendar timer events differently from regular cron execution.

D:

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: The Persistent option handles missed calendar timer events differently from regular cron execution.

Question 146

In a hands-on RHCSA practice VM, the assigned outcome was: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. What specific verification would demonstrate the target state?

  1. `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.
  2. After a simulated missed schedule, the service runs on next startup and `systemctl list-timers` shows a new next trigger.
  3. `grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`.
  4. After a lab reboot, the boot menu uses the approved timeout and the system still starts normally.

Explanation

Correct Answer

B:

After a simulated missed schedule, the service runs on next startup and `systemctl list-timers` shows a new next trigger. This check confirms the expected effect of: Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate. It distinguishes the intended result from the original failure mechanism: The Persistent option handles missed calendar timer events differently from regular cron execution.

Incorrect Answers

A:

`systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged. That verifies a separate lab task: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. It does not validate the implementation required here: Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.

C:

`grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`. That verifies a separate lab task: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. It does not validate the implementation required here: Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.

D:

After a lab reboot, the boot menu uses the approved timeout and the system still starts normally. That verifies a separate lab task: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It does not validate the implementation required here: Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.

Question 147

A trainee is diagnosing: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. Which root cause should they recognize before changing the system?

  1. A timer schedules activation of a corresponding service unit rather than executing arbitrary shell code by itself.
  2. Runtime activation and boot-time activation are separate systemd states.
  3. The Persistent option handles missed calendar timer events differently from regular cron execution.
  4. A scheduled job executes with the identity of the scheduler's configured user.

Explanation

Correct Answer

C:

The Persistent option handles missed calendar timer events differently from regular cron execution. This explains the task's initial state: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. The supported lab action is: Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.

Incorrect Answers

A:

A timer schedules activation of a corresponding service unit rather than executing arbitrary shell code by itself. This mechanism applies to another scenario: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. The given lab state instead requires the more specific cause in the correct choice.

B:

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.

D:

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.

Question 148

For this Linux administration lab: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. Which safety and lifecycle check best prevents the same problem returning?

  1. Review executable paths and file ownership as part of service deployment testing.
  2. Use managed package installations and maintain a rollbackable version record.
  3. Include unit reload, activation and next-fire-time checks in release tasks.
  4. Document catch-up side effects before enabling persistent timers for state-changing tasks.

Explanation

Correct Answer

D:

Document catch-up side effects before enabling persistent timers for state-changing tasks. This guards against recurrence of: The Persistent option handles missed calendar timer events differently from regular cron execution. Confirm the lab's final state by: After a simulated missed schedule, the service runs on next startup and `systemctl list-timers` shows a new next trigger.

Incorrect Answers

A:

Review executable paths and file ownership as part of service deployment testing. That control is best suited to a separate scenario: A new custom service has an `ExecStart` path that no longer exists after the application was moved. It is not the best safeguard for the current mechanism: The Persistent option handles missed calendar timer events differently from regular cron execution.

B:

Use managed package installations and maintain a rollbackable version record. That control is best suited to a separate scenario: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. It is not the best safeguard for the current mechanism: The Persistent option handles missed calendar timer events differently from regular cron execution.

C:

Include unit reload, activation and next-fire-time checks in release tasks. That control is best suited to a separate scenario: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. It is not the best safeguard for the current mechanism: The Persistent option handles missed calendar timer events differently from regular cron execution.

Question 149

A student working on a disposable RHEL10 training node receives this assignment: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. Which answer gives the correct practical approach?

  1. Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required.
  2. Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`.
  3. Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.
  4. Compare `getent hosts app.lab`, `ip route get <resolved-ip>`, and `ss -tln` or a permitted client connection.

Explanation

Correct Answer

B:

Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`. This directly addresses the lab target: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. The underlying behavior is: IP address assignment and resolver configuration are independent network settings. Verification: `nmcli dev show` and `getent hosts server.lab` show the approved DNS servers and expected name resolution.

Incorrect Answers

A:

Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required. This is an appropriate step for a DIFFERENT exercise, specifically: An IPv6-only lab application cannot listen because the host connection has no configured static IPv6 address. It does not address the required lab state, whose mechanism is: IP address assignment and resolver configuration are independent network settings.

C:

Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally. This is an appropriate step for a DIFFERENT exercise, specifically: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It does not address the required lab state, whose mechanism is: IP address assignment and resolver configuration are independent network settings.

D:

Compare `getent hosts app.lab`, `ip route get <resolved-ip>`, and `ss -tln` or a permitted client connection. This is an appropriate step for a DIFFERENT exercise, specifically: The host can ping its gateway but an HTTPS connection fails; the operator wants to blame DNS without checking name resolution. It does not address the required lab state, whose mechanism is: IP address assignment and resolver configuration are independent network settings.

Question 150

You have attempted this task on a disposable RHEL10 training node: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. Which command output or observation best confirms its success?

  1. `ip -6 addr show` lists the address and a local IPv6 connectivity test succeeds.
  2. The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled.
  3. `nmcli dev show` and `getent hosts server.lab` show the approved DNS servers and expected name resolution.
  4. `nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot.

Explanation

Correct Answer

C:

`nmcli dev show` and `getent hosts server.lab` show the approved DNS servers and expected name resolution. This check confirms the expected effect of: Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`. It distinguishes the intended result from the original failure mechanism: IP address assignment and resolver configuration are independent network settings.

Incorrect Answers

A:

`ip -6 addr show` lists the address and a local IPv6 connectivity test succeeds. That verifies a separate lab task: An IPv6-only lab application cannot listen because the host connection has no configured static IPv6 address. It does not validate the implementation required here: Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`.

B:

The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled. That verifies a separate lab task: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It does not validate the implementation required here: Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`.

D:

`nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot. That verifies a separate lab task: A NetworkManager profile is stored on disk but is not automatically activated after reboot. It does not validate the implementation required here: Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`.