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 54

Question 530

In a hands-on RHCSA practice VM, the assigned outcome was: A maintenance script must report whether a given process name exists without exiting with a misleading success status. What specific verification would demonstrate the target state?

  1. A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs.
  2. The known present and missing fixture processes produce different status messages.
  3. The script runs under a restricted environment and resolves required binaries.
  4. Arguments containing spaces are printed as single intended entries and the loop count matches input count.

Explanation

Correct Answer

B:

The known present and missing fixture processes produce different status messages. This check confirms the expected effect of: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation. It distinguishes the intended result from the original failure mechanism: An exact process-name match requires `-x` instead of a broad substring search.

Incorrect Answers

A:

A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs. That verifies a separate lab task: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. It does not validate the implementation required here: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.

C:

The script runs under a restricted environment and resolves required binaries. That verifies a separate lab task: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. It does not validate the implementation required here: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.

D:

Arguments containing spaces are printed as single intended entries and the loop count matches input count. That verifies a separate lab task: A housekeeping script must print each user-provided directory rather than always print one hard-coded value. It does not validate the implementation required here: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.

Question 531

A trainee is diagnosing: A maintenance script must report whether a given process name exists without exiting with a misleading success status. Which root cause should they recognize before changing the system?

  1. The shebang selects an interpreter; shell-specific syntax is not universal across implementations.
  2. Unquoted shell variable expansion performs splitting and pathname expansion.
  3. An exact process-name match requires `-x` instead of a broad substring search.
  4. Quoting `"$@"` preserves positional argument boundaries for safe shell iteration.

Explanation

Correct Answer

C:

An exact process-name match requires `-x` instead of a broad substring search. This explains the task's initial state: A maintenance script must report whether a given process name exists without exiting with a misleading success status. The supported lab action is: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.

Incorrect Answers

A:

The shebang selects an interpreter; shell-specific syntax is not universal across implementations. This mechanism applies to another scenario: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. The given lab state instead requires the more specific cause in the correct choice.

B:

Unquoted shell variable expansion performs splitting and pathname expansion. This mechanism applies to another scenario: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. The given lab state instead requires the more specific cause in the correct choice.

D:

Quoting `"$@"` preserves positional argument boundaries for safe shell iteration. This mechanism applies to another scenario: A housekeeping script must print each user-provided directory rather than always print one hard-coded value. The given lab state instead requires the more specific cause in the correct choice.

Question 532

For this Linux administration lab: A maintenance script must report whether a given process name exists without exiting with a misleading success status. Which safety and lifecycle check best prevents the same problem returning?

  1. Distinguish expected empty results from real failures in pipeline error handling.
  2. Fail fast on prerequisite failures and propagate meaningful exit codes.
  3. Declare interpreter requirements and run shell syntax checks before deployment.
  4. Choose exact process selectors and check for ambiguous multiple matches.

Explanation

Correct Answer

D:

Choose exact process selectors and check for ambiguous multiple matches. This guards against recurrence of: An exact process-name match requires `-x` instead of a broad substring search. Confirm the lab's final state by: The known present and missing fixture processes produce different status messages.

Incorrect Answers

A:

Distinguish expected empty results from real failures in pipeline error handling. That control is best suited to a separate scenario: A reporting script pipes `grep` through `wc` and treats a zero-match grep exit as a catastrophic error even though zero results are valid. It is not the best safeguard for the current mechanism: An exact process-name match requires `-x` instead of a broad substring search.

B:

Fail fast on prerequisite failures and propagate meaningful exit codes. That control is best suited to a separate scenario: A backup script runs even when its destination directory cannot be created, silently losing its output. It is not the best safeguard for the current mechanism: An exact process-name match requires `-x` instead of a broad substring search.

C:

Declare interpreter requirements and run shell syntax checks before deployment. That control is best suited to a separate scenario: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. It is not the best safeguard for the current mechanism: An exact process-name match requires `-x` instead of a broad substring search.

Question 533

A student working on a disposable RHEL10 training node receives this assignment: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. Which answer gives the correct practical approach?

  1. Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.
  2. Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented.
  3. Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.
  4. Use `renice +10 -p <verified-pid>` with appropriate privileges and permissions.

Explanation

Correct Answer

B:

Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented. This directly addresses the lab target: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. The underlying behavior is: Volatile journaling stored only in runtime memory may disappear on restart. Verification: After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries.

Incorrect Answers

A:

Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary. This is an appropriate step for a DIFFERENT exercise, specifically: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. It does not address the required lab state, whose mechanism is: Volatile journaling stored only in runtime memory may disappear on restart.

C:

Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes. This is an appropriate step for a DIFFERENT exercise, specifically: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. It does not address the required lab state, whose mechanism is: Volatile journaling stored only in runtime memory may disappear on restart.

D:

Use `renice +10 -p <verified-pid>` with appropriate privileges and permissions. This is an appropriate step for a DIFFERENT exercise, specifically: A batch reporting program interferes with interactive tasks, and the goal is to reduce its scheduling priority while it remains active. It does not address the required lab state, whose mechanism is: Volatile journaling stored only in runtime memory may disappear on restart.

Question 534

You have attempted this task on a disposable RHEL10 training node: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. Which command output or observation best confirms its success?

  1. `systemctl cat labworker.service` shows the updated directive and a controlled start honors it.
  2. The relevant exit status and journal error identify the cause, not merely whether the unit is enabled.
  3. After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries.
  4. The destination file exists with expected checksum and SSH encrypted transport.

Explanation

Correct Answer

C:

After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries. This check confirms the expected effect of: Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented. It distinguishes the intended result from the original failure mechanism: Volatile journaling stored only in runtime memory may disappear on restart.

Incorrect Answers

A:

`systemctl cat labworker.service` shows the updated directive and a controlled start honors it. That verifies a separate lab task: A unit file for a custom service is edited directly under `/etc/systemd/system`, but systemd continues using the old unit definition. It does not validate the implementation required here: Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented.

B:

The relevant exit status and journal error identify the cause, not merely whether the unit is enabled. That verifies a separate lab task: An application service fails to start but an administrator looks only at its unit's enabled state. It does not validate the implementation required here: Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented.

D:

The destination file exists with expected checksum and SSH encrypted transport. That verifies a separate lab task: A lab workstation must copy a sensitive diagnostic bundle to a remote node without exposing it to an insecure plain-text transfer. It does not validate the implementation required here: Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented.

Question 535

Troubleshoot the following RHEL 10 lab situation: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. Identify the key Linux mechanism behind the issue.

  1. Boot interruption changes early startup context and password recovery may require filesystem relabeling.
  2. Tuned applies a named set of system tuning policies rather than one ad hoc kernel setting.
  3. Journal filters separate source, boot and priority, whereas unfiltered logs mix unrelated events.
  4. Volatile journaling stored only in runtime memory may disappear on restart.

Explanation

Correct Answer

D:

Volatile journaling stored only in runtime memory may disappear on restart. This explains the task's initial state: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. The supported lab action is: Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented.

Incorrect Answers

A:

Boot interruption changes early startup context and password recovery may require filesystem relabeling. This mechanism applies to another scenario: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. The given lab state instead requires the more specific cause in the correct choice.

B:

Tuned applies a named set of system tuning policies rather than one ad hoc kernel setting. This mechanism applies to another scenario: The team wants a consistent throughput-oriented system tuning profile during a disposable performance experiment. The given lab state instead requires the more specific cause in the correct choice.

C:

Journal filters separate source, boot and priority, whereas unfiltered logs mix unrelated events. This mechanism applies to another scenario: A system journal contains many warnings and the student must isolate kernel-related messages for the current boot. The given lab state instead requires the more specific cause in the correct choice.

Question 536

Following lab verification, document the preventive or persistence-oriented procedure for: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. Which practice is most suitable?

  1. Maintain documented persistent journal storage and retention limits for troubleshooting.
  2. Trend memory and paging activity together under representative workload.
  3. Use verified PIDs and graceful termination before forced process removal.
  4. Check runtime unit health and recent journal errors after configuration changes.

Explanation

Correct Answer

A:

Maintain documented persistent journal storage and retention limits for troubleshooting. This guards against recurrence of: Volatile journaling stored only in runtime memory may disappear on restart. Confirm the lab's final state by: After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries.

Incorrect Answers

B:

Trend memory and paging activity together under representative workload. That control is best suited to a separate scenario: A running VM has adequate memory by `free -h` but swap usage spikes and the team assumes the application is leaking. It is not the best safeguard for the current mechanism: Volatile journaling stored only in runtime memory may disappear on restart.

C:

Use verified PIDs and graceful termination before forced process removal. That control is best suited to a separate scenario: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. It is not the best safeguard for the current mechanism: Volatile journaling stored only in runtime memory may disappear on restart.

D:

Check runtime unit health and recent journal errors after configuration changes. That control is best suited to a separate scenario: An application service fails to start but an administrator looks only at its unit's enabled state. It is not the best safeguard for the current mechanism: Volatile journaling stored only in runtime memory may disappear on restart.

Question 537

On an offline training clone, perform the following practical task: A previously working swap LV disappears after restart because no persistent swap entry was configured. Which action should be carried out after confirming the lab prerequisites?

  1. After confirming the mounted XFS LV and free VG capacity, use `lvextend -r -L +2G /dev/vg_training/lv_data` if the supported tools are available.
  2. Use `parted -s /dev/vdb mkpart primary 1MiB 1025MiB` and then `partprobe /dev/vdb` on the disposable disk.
  3. Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`.
  4. Use `blkid` to identify the filesystem UUID and update the relevant fstab line to `UUID=<value>` with an unchanged mountpoint.

Explanation

Correct Answer

C:

Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`. This directly addresses the lab target: A previously working swap LV disappears after restart because no persistent swap entry was configured. The underlying behavior is: `swapon` applies at runtime but does not automatically create persistent boot activation. Verification: `swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error.

Incorrect Answers

A:

After confirming the mounted XFS LV and free VG capacity, use `lvextend -r -L +2G /dev/vg_training/lv_data` if the supported tools are available. This is an appropriate step for a DIFFERENT exercise, specifically: An administrator wants to grow a logical volume and its XFS filesystem together for a disposable data directory. It does not address the required lab state, whose mechanism is: `swapon` applies at runtime but does not automatically create persistent boot activation.

B:

Use `parted -s /dev/vdb mkpart primary 1MiB 1025MiB` and then `partprobe /dev/vdb` on the disposable disk. This is an appropriate step for a DIFFERENT exercise, specifically: A verified blank GPT training disk needs one new 1 GiB partition with appropriate alignment. It does not address the required lab state, whose mechanism is: `swapon` applies at runtime but does not automatically create persistent boot activation.

D:

Use `blkid` to identify the filesystem UUID and update the relevant fstab line to `UUID=<value>` with an unchanged mountpoint. This is an appropriate step for a DIFFERENT exercise, specifically: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It does not address the required lab state, whose mechanism is: `swapon` applies at runtime but does not automatically create persistent boot activation.

Question 538

The lab examiner asks for evidence after this assignment: A previously working swap LV disappears after restart because no persistent swap entry was configured. What is the decisive verification step?

  1. `vgs vg_training` displays the total size and `pvs` maps both PVs to the group.
  2. The resulting mapping identifies filesystem to LV to VG to PV without changing data.
  3. `lvs` and `df -h /srv/data` both show the expanded LV and filesystem.
  4. `swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error.

Explanation

Correct Answer

D:

`swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error. This check confirms the expected effect of: Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`. It distinguishes the intended result from the original failure mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.

Incorrect Answers

A:

`vgs vg_training` displays the total size and `pvs` maps both PVs to the group. That verifies a separate lab task: Two fresh disposable LVM partitions must become one storage pool for a new application. It does not validate the implementation required here: Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`.

B:

The resulting mapping identifies filesystem to LV to VG to PV without changing data. That verifies a separate lab task: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. It does not validate the implementation required here: Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`.

C:

`lvs` and `df -h /srv/data` both show the expanded LV and filesystem. That verifies a separate lab task: An administrator wants to grow a logical volume and its XFS filesystem together for a disposable data directory. It does not validate the implementation required here: Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`.

Question 539

A training host has this situation: A previously working swap LV disappears after restart because no persistent swap entry was configured. Which system behavior best explains the original failure or risk?

  1. `swapon` applies at runtime but does not automatically create persistent boot activation.
  2. Device discovery and actual filesystem or LVM creation are separate operations.
  3. `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.
  4. GPT initialization replaces the chosen disk's partition metadata.

Explanation

Correct Answer

A:

`swapon` applies at runtime but does not automatically create persistent boot activation. This explains the task's initial state: A previously working swap LV disappears after restart because no persistent swap entry was configured. The supported lab action is: Find its UUID with `blkid`, then add a reviewed `UUID=<uuid> none swap defaults 0 0` entry to `/etc/fstab`.

Incorrect Answers

B:

Device discovery and actual filesystem or LVM creation are separate operations. This mechanism applies to another scenario: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. The given lab state instead requires the more specific cause in the correct choice.

C:

`-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. This mechanism applies to another scenario: An LV should consume precisely 20% of remaining free extents for a training scratch workload. The given lab state instead requires the more specific cause in the correct choice.

D:

GPT initialization replaces the chosen disk's partition metadata. This mechanism applies to another scenario: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. The given lab state instead requires the more specific cause in the correct choice.

Question 540

A student has implemented the following configuration: A previously working swap LV disappears after restart because no persistent swap entry was configured. What repeatable control best reduces regressions or unsafe changes?

  1. Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot.
  2. Audit swap entries and device UUIDs after storage migrations.
  3. Record PV mapping before hardware maintenance and always verify device identification.
  4. Track approved PV additions in capacity records and test before growing filesystems.

Explanation

Correct Answer

B:

Audit swap entries and device UUIDs after storage migrations. This guards against recurrence of: `swapon` applies at runtime but does not automatically create persistent boot activation. Confirm the lab's final state by: `swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error.

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: `swapon` applies at runtime but does not automatically create persistent boot activation.

C:

Record PV mapping before hardware maintenance and always verify device identification. That control is best suited to a separate scenario: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.

D:

Track approved PV additions in capacity records and test before growing filesystems. That control is best suited to a separate scenario: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.