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 23

Question 220

A student has implemented the following configuration: Two fresh disposable LVM partitions must become one storage pool for a new application. What repeatable control best reduces regressions or unsafe changes?

  1. Include a full storage dependency diagram in change requests.
  2. Use descriptive VG names and verify physical member lists before changes.
  3. Check `vgs` free extents before provisioning and keep names consistent with service inventory.
  4. Plan LV resizing and compatible filesystem growth as separate verified steps.

Explanation

Correct Answer

B:

Use descriptive VG names and verify physical member lists before changes. This guards against recurrence of: A volume group aggregates free extents from one or more physical volumes. Confirm the lab's final state by: `vgs vg_training` displays the total size and `pvs` maps both PVs to the group.

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: A volume group aggregates free extents from one or more physical volumes.

C:

Check `vgs` free extents before provisioning and keep names consistent with service inventory. That control is best suited to a separate scenario: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It is not the best safeguard for the current mechanism: A volume group aggregates free extents from one or more physical volumes.

D:

Plan LV resizing and compatible filesystem growth as separate verified steps. That control is best suited to a separate scenario: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. It is not the best safeguard for the current mechanism: A volume group aggregates free extents from one or more physical volumes.

Question 221

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: A static XFS mount works when issued manually but vanishes after every reboot. Select the most appropriate implementation step.

  1. Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.
  2. Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration.
  3. Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported.
  4. Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount.

Explanation

Correct Answer

D:

Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount. This directly addresses the lab target: A static XFS mount works when issued manually but vanishes after every reboot. The underlying behavior is: Runtime mounting does not automatically write persistent boot mount configuration. Verification: After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.

Incorrect Answers

A:

Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`. This is an appropriate step for a DIFFERENT exercise, specifically: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It does not address the required lab state, whose mechanism is: Runtime mounting does not automatically write persistent boot mount configuration.

B:

Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration. This is an appropriate step for a DIFFERENT exercise, specifically: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. It does not address the required lab state, whose mechanism is: Runtime mounting does not automatically write persistent boot mount configuration.

C:

Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported. This is an appropriate step for a DIFFERENT exercise, specifically: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. It does not address the required lab state, whose mechanism is: Runtime mounting does not automatically write persistent boot mount configuration.

Question 222

After a lab configuration change, verify: A static XFS mount works when issued manually but vanishes after every reboot. Which result most directly proves the desired system state?

  1. After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.
  2. The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted.
  3. A simulated server outage does not block the expected system boot and access after recovery mounts normally.
  4. `df -h /mnt/ext4lab` reflects the newly available capacity.

Explanation

Correct Answer

A:

After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type. This check confirms the expected effect of: Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount. It distinguishes the intended result from the original failure mechanism: Runtime mounting does not automatically write persistent boot mount configuration.

Incorrect Answers

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: Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount.

C:

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: Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount.

D:

`df -h /mnt/ext4lab` reflects the newly available capacity. That verifies a separate lab task: An ext4 training LV was expanded but file capacity remains unchanged. It does not validate the implementation required here: Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount.

Question 223

In an EX200-style practice lab, this condition exists: A static XFS mount works when issued manually but vanishes after every reboot. Which explanation correctly identifies the underlying issue?

  1. Interoperable FAT filesystems differ from XFS, ext4 and their Unix permissions.
  2. Runtime mounting does not automatically write persistent boot mount configuration.
  3. Increasing block-device capacity does not automatically grow the filesystem metadata.
  4. Mount option flags can override normal file permission expectations.

Explanation

Correct Answer

B:

Runtime mounting does not automatically write persistent boot mount configuration. This explains the task's initial state: A static XFS mount works when issued manually but vanishes after every reboot. The supported lab action is: Add `UUID=<actual-uuid> /srv/archive xfs defaults 0 0` to `/etc/fstab`, reload systemd, and validate the mount.

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.

C:

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.

D:

Mount option flags can override normal file permission expectations. This mechanism applies to another scenario: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. The given lab state instead requires the more specific cause in the correct choice.

Question 224

After completing this practical task on a disposable RHEL10 training node: A static XFS mount works when issued manually but vanishes after every reboot. Which operational safeguard helps keep the result correct and safe?

  1. Test boot and reconnect behavior with the NFS server intentionally offline in the lab.
  2. Verify server export reachability and intended access controls before persistent NFS configuration.
  3. Use stable identifiers and run `findmnt --verify` before rebooting.
  4. Configure an appropriate persistent mount separately after runtime testing.

Explanation

Correct Answer

C:

Use stable identifiers and run `findmnt --verify` before rebooting. This guards against recurrence of: Runtime mounting does not automatically write persistent boot mount configuration. Confirm the lab's final state by: After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.

Incorrect Answers

A:

Test boot and reconnect behavior with the NFS server intentionally offline in the lab. That control is best suited to a separate scenario: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It is not the best safeguard for the current mechanism: Runtime mounting does not automatically write persistent boot mount configuration.

B:

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: Runtime mounting does not automatically write persistent boot mount configuration.

D:

Configure an appropriate persistent mount separately after runtime testing. That control is best suited to a separate scenario: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It is not the best safeguard for the current mechanism: Runtime mounting does not automatically write persistent boot mount configuration.

Question 225

Lab exercise on an offline training clone: 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. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.
  2. Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.
  3. Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.
  4. Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.

Explanation

Correct Answer

A:

Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions. This directly addresses the lab target: 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 underlying behavior is: A scheduled job executes with the identity of the scheduler's configured user. Verification: `crontab -u reporter -l` contains the job and generated files are owned by `reporter` rather than root.

Incorrect Answers

B:

Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy. This is an appropriate step for a DIFFERENT exercise, specifically: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. It does not address the required lab state, whose mechanism is: A scheduled job executes with the identity of the scheduler's configured user.

C:

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: A scheduled job executes with the identity of the scheduler's configured user.

D:

Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification. This is an appropriate step for a DIFFERENT exercise, specifically: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. It does not address the required lab state, whose mechanism is: A scheduled job executes with the identity of the scheduler's configured user.

Question 226

In a hands-on RHCSA practice VM, the assigned outcome was: 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. What specific verification would demonstrate the target state?

  1. Current time becomes accurate while the configured local timezone remains unchanged.
  2. `crontab -u reporter -l` contains the job and generated files are owned by `reporter` rather than root.
  3. `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.
  4. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.

Explanation

Correct Answer

B:

`crontab -u reporter -l` contains the job and generated files are owned by `reporter` rather than root. This check confirms the expected effect of: Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions. It distinguishes the intended result from the original failure mechanism: A scheduled job executes with the identity of the scheduler's configured user.

Incorrect Answers

A:

Current time becomes accurate while the configured local timezone remains unchanged. That verifies a separate lab task: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. It does not validate the implementation required here: Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.

C:

`chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status. That verifies a separate lab task: 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 validate the implementation required here: Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.

D:

`systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit. That verifies a separate lab task: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. It does not validate the implementation required here: Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.

Question 227

A trainee is diagnosing: 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. Which root cause should they recognize before changing the system?

  1. Subscription entitlement and repository enablement both affect package availability.
  2. Systemd cannot start a unit whose configured executable is absent.
  3. A scheduled job executes with the identity of the scheduler's configured user.
  4. A running time daemon without valid reachable sources cannot synchronize clocks.

Explanation

Correct Answer

C:

A scheduled job executes with the identity of the scheduler's configured user. This explains the task's initial state: 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 supported lab action is: Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.

Incorrect Answers

A:

Subscription entitlement and repository enablement both affect package availability. This mechanism applies to another scenario: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. The given lab state instead requires the more specific cause in the correct choice.

B:

Systemd cannot start a unit whose configured executable is absent. This mechanism applies to another scenario: A new custom service has an `ExecStart` path that no longer exists after the application was moved. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 228

For this Linux administration lab: 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. Which safety and lifecycle check best prevents the same problem returning?

  1. Audit time source and timezone independently in host acceptance tests.
  2. Use managed package installations and maintain a rollbackable version record.
  3. Review package source provenance before modifying repository trust policies.
  4. Choose service accounts and privileges deliberately for each recurring job.

Explanation

Correct Answer

D:

Choose service accounts and privileges deliberately for each recurring job. This guards against recurrence of: A scheduled job executes with the identity of the scheduler's configured user. Confirm the lab's final state by: `crontab -u reporter -l` contains the job and generated files are owned by `reporter` rather than root.

Incorrect Answers

A:

Audit time source and timezone independently in host acceptance tests. That control is best suited to a separate scenario: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. It is not the best safeguard for the current mechanism: A scheduled job executes with the identity of the scheduler's configured user.

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: A scheduled job executes with the identity of the scheduler's configured user.

C:

Review package source provenance before modifying repository trust policies. That control is best suited to a separate scenario: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It is not the best safeguard for the current mechanism: A scheduled job executes with the identity of the scheduler's configured user.

Question 229

A student working on a local virtualization classroom receives this assignment: A NetworkManager profile is stored on disk but is not automatically activated after reboot. Which answer gives the correct practical approach?

  1. After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.
  2. Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.
  3. Use `hostnamectl set-hostname node150.lab` on the disposable host.
  4. Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.

Explanation

Correct Answer

B:

Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe. This directly addresses the lab target: A NetworkManager profile is stored on disk but is not automatically activated after reboot. The underlying behavior is: Persisted connection configuration can remain inactive when autoconnect is disabled. Verification: `nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot.

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: Persisted connection configuration can remain inactive when autoconnect is disabled.

C:

Use `hostnamectl set-hostname node150.lab` on the disposable host. This is an appropriate step for a DIFFERENT exercise, specifically: A hostname change is applied only with the `hostname` runtime command and resets after restart. It does not address the required lab state, whose mechanism is: Persisted connection configuration can remain inactive when autoconnect is disabled.

D:

Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope. This is an appropriate step for a DIFFERENT exercise, specifically: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not address the required lab state, whose mechanism is: Persisted connection configuration can remain inactive when autoconnect is disabled.

Question 230

You have attempted this task on a local virtualization classroom: A NetworkManager profile is stored on disk but is not automatically activated after reboot. Which command output or observation best confirms its success?

  1. The port remains listed in permanent configuration and works after a controlled reboot.
  2. An authorized client connects and the correct zone reports the service or port.
  3. `nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot.
  4. `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.

Explanation

Correct Answer

C:

`nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot. This check confirms the expected effect of: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe. It distinguishes the intended result from the original failure mechanism: Persisted connection configuration can remain inactive when autoconnect is disabled.

Incorrect Answers

A:

The port remains listed in permanent configuration and works after a controlled reboot. That verifies a separate lab task: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. It does not validate the implementation required here: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.

B:

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: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.

D:

`nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway. That verifies a separate lab task: A training host has DHCP IPv4 but requires a fixed address `192.0.2.50/24` and gateway `192.0.2.1` for a private lab subnet. It does not validate the implementation required here: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.