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 27

Question 260

For this Linux administration lab: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. Which safety and lifecycle check best prevents the same problem returning?

  1. Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot.
  2. Verify final filesystem size and document that XFS supports growth but not shrink.
  3. Verify extent allocation and redundancy before any VG reduction.
  4. Check `vgs` free extents before provisioning and keep names consistent with service inventory.

Explanation

Correct Answer

D:

Check `vgs` free extents before provisioning and keep names consistent with service inventory. This guards against recurrence of: An LVM logical volume is a block device until it is formatted and mounted separately. Confirm the lab's final state by: `lvs /dev/vg_training/lv_db` reports the requested LV and does not show a filesystem automatically.

Incorrect Answers

A:

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: An LVM logical volume is a block device until it is formatted and mounted separately.

B:

Verify final filesystem size and document that XFS supports growth but not shrink. That control is best suited to a separate scenario: An administrator wants to grow a logical volume and its XFS filesystem together for a disposable data directory. It is not the best safeguard for the current mechanism: An LVM logical volume is a block device until it is formatted and mounted separately.

C:

Verify extent allocation and redundancy before any VG reduction. That control is best suited to a separate scenario: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. It is not the best safeguard for the current mechanism: An LVM logical volume is a block device until it is formatted and mounted separately.

Question 261

A student working on a test RHEL10 instance receives this assignment: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. Which answer gives the correct practical approach?

  1. Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.
  2. Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.
  3. Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.
  4. Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions.

Explanation

Correct Answer

B:

Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`. This directly addresses the lab target: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. The underlying behavior is: Incorrect persistent mount definitions can delay boot or prevent expected units from activating. Verification: The verification returns no invalid-entry errors before the reboot and the mount becomes active.

Incorrect Answers

A:

Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission. This is an appropriate step for a DIFFERENT exercise, specifically: 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 does not address the required lab state, whose mechanism is: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

C:

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: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

D:

Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions. This is an appropriate step for a DIFFERENT exercise, specifically: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. It does not address the required lab state, whose mechanism is: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

Question 262

You have attempted this task on a test RHEL10 instance: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. Which command output or observation best confirms its success?

  1. A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data.
  2. After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.
  3. The verification returns no invalid-entry errors before the reboot and the mount becomes active.
  4. `findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works.

Explanation

Correct Answer

C:

The verification returns no invalid-entry errors before the reboot and the mount becomes active. This check confirms the expected effect of: Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`. It distinguishes the intended result from the original failure mechanism: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

Incorrect Answers

A:

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: Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.

B:

After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type. That verifies a separate lab task: A static XFS mount works when issued manually but vanishes after every reboot. It does not validate the implementation required here: Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.

D:

`findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works. That verifies a separate lab task: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It does not validate the implementation required here: Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.

Question 263

Troubleshoot the following RHEL 10 lab situation: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. Identify the key Linux mechanism behind the issue.

  1. Filesystem presence alone does not attach it into the directory namespace.
  2. Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.
  3. NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.
  4. Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

Explanation

Correct Answer

D:

Incorrect persistent mount definitions can delay boot or prevent expected units from activating. This explains the task's initial state: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. The supported lab action is: Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.

Incorrect Answers

A:

Filesystem presence alone does not attach it into the directory namespace. This mechanism applies to another scenario: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. The given lab state instead requires the more specific cause in the correct choice.

B:

Remote filesystems depend on network availability and need an appropriate boot-time mount strategy. This mechanism applies to another scenario: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. 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.

Question 264

Following lab verification, document the preventive or persistence-oriented procedure for: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. Which practice is most suitable?

  1. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.
  2. Validate filesystem type and correct resizing utility before growing an LV-backed filesystem.
  3. Keep removable-media formatting separate from system disks and validate compatibility requirements.
  4. Inspect the entire path before changing only the final file's mode.

Explanation

Correct Answer

A:

Treat fstab modifications as high-impact and test mount behavior while a recovery console is available. This guards against recurrence of: Incorrect persistent mount definitions can delay boot or prevent expected units from activating. Confirm the lab's final state by: The verification returns no invalid-entry errors before the reboot and the mount becomes active.

Incorrect Answers

B:

Validate filesystem type and correct resizing utility before growing an LV-backed filesystem. That control is best suited to a separate scenario: An ext4 training LV was expanded but file capacity remains unchanged. It is not the best safeguard for the current mechanism: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

C:

Keep removable-media formatting separate from system disks and validate compatibility requirements. That control is best suited to a separate scenario: A USB-compatible training partition must use the VFAT filesystem, but the operator formats it as XFS instead. It is not the best safeguard for the current mechanism: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

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: Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

Question 265

On an isolated enterprise lab VM, perform the following practical task: A daemon is started manually after package installation but must be reliably available after reboots. 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. Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.
  3. Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.
  4. Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.

Explanation

Correct Answer

C:

Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed. This directly addresses the lab target: A daemon is started manually after package installation but must be reliably available after reboots. The underlying behavior is: Runtime activation and boot-time activation are separate systemd states. Verification: `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.

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: Runtime activation and boot-time activation are separate systemd states.

B:

Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system. This is an appropriate step for a DIFFERENT exercise, specifically: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. It does not address the required lab state, whose mechanism is: Runtime activation and boot-time activation are separate systemd states.

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: Runtime activation and boot-time activation are separate systemd states.

Question 266

The lab examiner asks for evidence after this assignment: A daemon is started manually after package installation but must be reliably available after reboots. What is the decisive verification step?

  1. The target package's metadata resolves from an entitled supported repository.
  2. `atq` lists the pending job and the fixture log records one run at the expected time.
  3. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.
  4. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.

Explanation

Correct Answer

D:

`systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot. This check confirms the expected effect of: Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed. It distinguishes the intended result from the original failure mechanism: Runtime activation and boot-time activation are separate systemd states.

Incorrect Answers

A:

The target package's metadata resolves from an entitled supported repository. That verifies a separate lab task: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It does not validate the implementation required here: Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.

B:

`atq` lists the pending job and the fixture log records one run at the expected time. That verifies a separate lab task: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. It does not validate the implementation required here: Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.

C:

`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: Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.

Question 267

A training host has this situation: A daemon is started manually after package installation but must be reliably available after reboots. Which system behavior best explains the original failure or risk?

  1. Runtime activation and boot-time activation are separate systemd states.
  2. Isolating an active target does not set the default target for future boots.
  3. Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.
  4. Installing a kernel does not guarantee the desired boot entry is selected.

Explanation

Correct Answer

A:

Runtime activation and boot-time activation are separate systemd states. This explains the task's initial state: A daemon is started manually after package installation but must be reliably available after reboots. The supported lab action is: Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.

Incorrect Answers

B:

Isolating an active target does not set the default target for future boots. This mechanism applies to another scenario: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. The given lab state instead requires the more specific cause in the correct choice.

C:

Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS. This mechanism applies to another scenario: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. The given lab state instead requires the more specific cause in the correct choice.

D:

Installing a kernel does not guarantee the desired boot entry is selected. This mechanism applies to another scenario: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. The given lab state instead requires the more specific cause in the correct choice.

Question 268

A student has implemented the following configuration: A daemon is started manually after package installation but must be reliably available after reboots. What repeatable control best reduces regressions or unsafe changes?

  1. Record both the configuration file change and observed runtime source.
  2. Verify both states in application installation acceptance tests.
  3. Maintain approved time servers and monitor drift/offset after network changes.
  4. Include unit reload, activation and next-fire-time checks in release tasks.

Explanation

Correct Answer

B:

Verify both states in application installation acceptance tests. This guards against recurrence of: Runtime activation and boot-time activation are separate systemd states. Confirm the lab's final state by: `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.

Incorrect Answers

A:

Record both the configuration file change and observed runtime source. That control is best suited to a separate scenario: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It is not the best safeguard for the current mechanism: Runtime activation and boot-time activation are separate systemd states.

C:

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: Runtime activation and boot-time activation are separate systemd states.

D:

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: Runtime activation and boot-time activation are separate systemd states.

Question 269

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: A hostname change is applied only with the `hostname` runtime command and resets after restart. Select the most appropriate implementation step.

  1. Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM.
  2. Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.
  3. After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.
  4. Use `hostnamectl set-hostname node150.lab` on the disposable host.

Explanation

Correct Answer

D:

Use `hostnamectl set-hostname node150.lab` on the disposable host. This directly addresses the lab target: A hostname change is applied only with the `hostname` runtime command and resets after restart. The underlying behavior is: Runtime hostname assignment may not update the persistent static hostname. Verification: `hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot.

Incorrect Answers

A:

Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM. This is an appropriate step for a DIFFERENT exercise, specifically: A training host must resolve one intentionally private name without querying DNS while building a disconnected lab. It does not address the required lab state, whose mechanism is: Runtime hostname assignment may not update the persistent static hostname.

B:

Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall. This is an appropriate step for a DIFFERENT exercise, specifically: A service listens on port 8443 but clients are blocked by the active public firewalld zone. It does not address the required lab state, whose mechanism is: Runtime hostname assignment may not update the persistent static hostname.

C:

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: Runtime hostname assignment may not update the persistent static hostname.

Question 270

After a lab configuration change, verify: A hostname change is applied only with the `hostname` runtime command and resets after restart. Which result most directly proves the desired system state?

  1. `hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot.
  2. `ip -6 route` shows only the intended routes and a local subnet test succeeds.
  3. `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.
  4. `nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot.

Explanation

Correct Answer

A:

`hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot. This check confirms the expected effect of: Use `hostnamectl set-hostname node150.lab` on the disposable host. It distinguishes the intended result from the original failure mechanism: Runtime hostname assignment may not update the persistent static hostname.

Incorrect Answers

B:

`ip -6 route` shows only the intended routes and a local subnet test succeeds. That verifies a separate lab task: An IPv6 connection receives a default route from router advertisements when policy requires the test host to use only a specified local IPv6 subnet. It does not validate the implementation required here: Use `hostnamectl set-hostname node150.lab` on the disposable host.

C:

`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: Use `hostnamectl set-hostname node150.lab` on the disposable host.

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: Use `hostnamectl set-hostname node150.lab` on the disposable host.