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 18

Question 170

The lab examiner asks for evidence after this assignment: A shell script writes raw command output but needs its first line to include the current hostname from the target host. What is the decisive verification step?

  1. The known present and missing fixture processes produce different status messages.
  2. The output contains one result per unit and no unrequested service is started.
  3. In a fixture where the first command exits 1, the second command does not run.
  4. The printed host label matches `hostname -s` without treating it as an executable.

Explanation

Correct Answer

D:

The printed host label matches `hostname -s` without treating it as an executable. This check confirms the expected effect of: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script. It distinguishes the intended result from the original failure mechanism: Command substitution captures a command's standard output as data.

Incorrect Answers

A:

The known present and missing fixture processes produce different status messages. That verifies a separate lab task: A maintenance script must report whether a given process name exists without exiting with a misleading success status. It does not validate the implementation required here: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

B:

The output contains one result per unit and no unrequested service is started. That verifies a separate lab task: A service check is intended to poll five named systemd units, but the script uses only the first literal unit. It does not validate the implementation required here: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

C:

In a fixture where the first command exits 1, the second command does not run. That verifies a separate lab task: A script invokes two commands on one line with a semicolon and prints success even if the first fails. It does not validate the implementation required here: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

Question 171

A training host has this situation: A shell script writes raw command output but needs its first line to include the current hostname from the target host. Which system behavior best explains the original failure or risk?

  1. Command substitution captures a command's standard output as data.
  2. A shell condition requires an explicit test and controlled success/failure branches.
  3. A `for` loop explicitly processes each named input rather than repeating one static check.
  4. A wildcard expands all matching entries; the `-d` test discriminates directories.

Explanation

Correct Answer

A:

Command substitution captures a command's standard output as data. This explains the task's initial state: A shell script writes raw command output but needs its first line to include the current hostname from the target host. The supported lab action is: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

Incorrect Answers

B:

A shell condition requires an explicit test and controlled success/failure branches. This mechanism applies to another scenario: A lab script must exit successfully only when `/etc/hosts` exists, but an unguarded command reports success in both cases. The given lab state instead requires the more specific cause in the correct choice.

C:

A `for` loop explicitly processes each named input rather than repeating one static check. This mechanism applies to another scenario: A service check is intended to poll five named systemd units, but the script uses only the first literal unit. The given lab state instead requires the more specific cause in the correct choice.

D:

A wildcard expands all matching entries; the `-d` test discriminates directories. This mechanism applies to another scenario: A daily job must print only directories under a sample tree but currently loops through both files and directories. The given lab state instead requires the more specific cause in the correct choice.

Question 172

A student has implemented the following configuration: A shell script writes raw command output but needs its first line to include the current hostname from the target host. What repeatable control best reduces regressions or unsafe changes?

  1. Quote variables unless deliberate splitting is required and tested.
  2. Quote substituted variables and test outputs when constructing paths or configuration.
  3. Fail fast on prerequisite failures and propagate meaningful exit codes.
  4. Declare runtime prerequisites, command paths and required environment variables in scheduled scripts.

Explanation

Correct Answer

B:

Quote substituted variables and test outputs when constructing paths or configuration. This guards against recurrence of: Command substitution captures a command's standard output as data. Confirm the lab's final state by: The printed host label matches `hostname -s` without treating it as an executable.

Incorrect Answers

A:

Quote variables unless deliberate splitting is required and tested. That control is best suited to a separate scenario: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. It is not the best safeguard for the current mechanism: Command substitution captures a command's standard output as data.

C:

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: Command substitution captures a command's standard output as data.

D:

Declare runtime prerequisites, command paths and required environment variables in scheduled scripts. That control is best suited to a separate scenario: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. It is not the best safeguard for the current mechanism: Command substitution captures a command's standard output as data.

Question 173

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. Select the most appropriate implementation step.

  1. Use `scp -p /tmp/diagnostics.tgz student@labhost:/home/student/` with an authenticated host key.
  2. Run `journalctl -k -b -p warning --no-pager` on the sample host.
  3. At the local hypervisor console, follow the supported Red Hat boot-interruption password recovery procedure for the RHEL 10 installation; do not change unrelated production hosts.
  4. Use `sudo systemctl set-default multi-user.target` on the disposable training VM.

Explanation

Correct Answer

D:

Use `sudo systemctl set-default multi-user.target` on the disposable training VM. This directly addresses the lab target: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. The underlying behavior is: The default systemd target controls the system's boot state and persists independently of the current target. Verification: `systemctl get-default` reports `multi-user.target`, including after reboot.

Incorrect Answers

A:

Use `scp -p /tmp/diagnostics.tgz student@labhost:/home/student/` with an authenticated host key. This is an appropriate step for a DIFFERENT exercise, specifically: 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 address the required lab state, whose mechanism is: The default systemd target controls the system's boot state and persists independently of the current target.

B:

Run `journalctl -k -b -p warning --no-pager` on the sample host. This is an appropriate step for a DIFFERENT exercise, specifically: A system journal contains many warnings and the student must isolate kernel-related messages for the current boot. It does not address the required lab state, whose mechanism is: The default systemd target controls the system's boot state and persists independently of the current target.

C:

At the local hypervisor console, follow the supported Red Hat boot-interruption password recovery procedure for the RHEL 10 installation; do not change unrelated production hosts. This is an appropriate step for a DIFFERENT exercise, specifically: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. It does not address the required lab state, whose mechanism is: The default systemd target controls the system's boot state and persists independently of the current target.

Question 174

After a lab configuration change, verify: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. Which result most directly proves the desired system state?

  1. `systemctl get-default` reports `multi-user.target`, including after reboot.
  2. `systemctl cat labworker.service` shows the updated directive and a controlled start honors it.
  3. `systemctl show -p ActiveState lab-daemon.service` is healthy and an end-to-end test reflects the updated setting.
  4. `ps -o ni,comm -p <pid>` shows the intended nice value for the launched job.

Explanation

Correct Answer

A:

`systemctl get-default` reports `multi-user.target`, including after reboot. This check confirms the expected effect of: Use `sudo systemctl set-default multi-user.target` on the disposable training VM. It distinguishes the intended result from the original failure mechanism: The default systemd target controls the system's boot state and persists independently of the current target.

Incorrect Answers

B:

`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: Use `sudo systemctl set-default multi-user.target` on the disposable training VM.

C:

`systemctl show -p ActiveState lab-daemon.service` is healthy and an end-to-end test reflects the updated setting. That verifies a separate lab task: An application configuration was changed on disk, but the running daemon still uses the previous settings. It does not validate the implementation required here: Use `sudo systemctl set-default multi-user.target` on the disposable training VM.

D:

`ps -o ni,comm -p <pid>` shows the intended nice value for the launched job. That verifies a separate lab task: A background indexing job should start with a lower CPU scheduling priority from its first instruction. It does not validate the implementation required here: Use `sudo systemctl set-default multi-user.target` on the disposable training VM.

Question 175

In an EX200-style practice lab, this condition exists: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. Which explanation correctly identifies the underlying issue?

  1. Systemd caches unit definitions until its manager configuration is reloaded.
  2. The default systemd target controls the system's boot state and persists independently of the current target.
  3. A masked unit points to `/dev/null`, intentionally preventing activation.
  4. Poweroff and reboot invoke different system state transitions.

Explanation

Correct Answer

B:

The default systemd target controls the system's boot state and persists independently of the current target. This explains the task's initial state: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. The supported lab action is: Use `sudo systemctl set-default multi-user.target` on the disposable training VM.

Incorrect Answers

A:

Systemd caches unit definitions until its manager configuration is reloaded. This mechanism applies to another scenario: A unit file for a custom service is edited directly under `/etc/systemd/system`, but systemd continues using the old unit definition. The given lab state instead requires the more specific cause in the correct choice.

C:

A masked unit points to `/dev/null`, intentionally preventing activation. This mechanism applies to another scenario: A critical lab service was accidentally masked, so a regular `systemctl start` command fails despite correct unit configuration. The given lab state instead requires the more specific cause in the correct choice.

D:

Poweroff and reboot invoke different system state transitions. This mechanism applies to another scenario: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. The given lab state instead requires the more specific cause in the correct choice.

Question 176

After completing this practical task on a disposable RHEL10 training node: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. Which operational safeguard helps keep the result correct and safe?

  1. Record the original profile and restore it after the controlled benchmark.
  2. Trend memory and paging activity together under representative workload.
  3. Record target changes and verify a console login path before reboot.
  4. Protect physical/virtual console access and document emergency recovery approvals.

Explanation

Correct Answer

C:

Record target changes and verify a console login path before reboot. This guards against recurrence of: The default systemd target controls the system's boot state and persists independently of the current target. Confirm the lab's final state by: `systemctl get-default` reports `multi-user.target`, including after reboot.

Incorrect Answers

A:

Record the original profile and restore it after the controlled benchmark. That control is best suited to a separate scenario: The team wants a consistent throughput-oriented system tuning profile during a disposable performance experiment. It is not the best safeguard for the current mechanism: The default systemd target controls the system's boot state and persists independently of the current target.

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: The default systemd target controls the system's boot state and persists independently of the current target.

D:

Protect physical/virtual console access and document emergency recovery approvals. That control is best suited to a separate scenario: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. It is not the best safeguard for the current mechanism: The default systemd target controls the system's boot state and persists independently of the current target.

Question 177

Lab exercise on an offline training clone: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures.
  2. Run `mkswap /dev/vg_training/lv_swap` on the dedicated empty swap LV followed by `swapon /dev/vg_training/lv_swap`.
  3. Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`.
  4. Use `lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS`, `blkid`, and the lab inventory to identify the designated empty `/dev/vdb`.

Explanation

Correct Answer

A:

On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures. This directly addresses the lab target: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. The underlying behavior is: LVM physical volumes carry metadata that lets volume groups manage underlying extents. Verification: `pvs /dev/vdb1` shows a physical volume and no other disk was initialized.

Incorrect Answers

B:

Run `mkswap /dev/vg_training/lv_swap` on the dedicated empty swap LV followed by `swapon /dev/vg_training/lv_swap`. This is an appropriate step for a DIFFERENT exercise, specifically: A small swap logical volume on a training host is inactive after it has been created. It does not address the required lab state, whose mechanism is: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

C:

Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`. This is an appropriate step for a DIFFERENT exercise, specifically: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. It does not address the required lab state, whose mechanism is: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

D:

Use `lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS`, `blkid`, and the lab inventory to identify the designated empty `/dev/vdb`. This is an appropriate step for a DIFFERENT exercise, specifically: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. It does not address the required lab state, whose mechanism is: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

Question 178

In a hands-on RHCSA practice VM, the assigned outcome was: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. What specific verification would demonstrate the target state?

  1. The report accurately explains why a constrained allocation on the first PV differs from total VG capacity.
  2. `pvs /dev/vdb1` shows a physical volume and no other disk was initialized.
  3. `swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error.
  4. `vgs` no longer lists the retired group while `vg_training` remains unaffected.

Explanation

Correct Answer

B:

`pvs /dev/vdb1` shows a physical volume and no other disk was initialized. This check confirms the expected effect of: On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures. It distinguishes the intended result from the original failure mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.

Incorrect Answers

A:

The report accurately explains why a constrained allocation on the first PV differs from total VG capacity. That verifies a separate lab task: A training PV reports little free space while its VG appears to have ample total capacity across a second PV. It does not validate the implementation required here: On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures.

C:

`swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error. That verifies a separate lab task: A previously working swap LV disappears after restart because no persistent swap entry was configured. It does not validate the implementation required here: On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures.

D:

`vgs` no longer lists the retired group while `vg_training` remains unaffected. That verifies a separate lab task: A volume group is to be retired in a disposable lab, but it still contains active LVs and the student tries `vgremove` immediately. It does not validate the implementation required here: On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures.

Question 179

A trainee is diagnosing: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. Which root cause should they recognize before changing the system?

  1. `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.
  2. Stale signatures can affect device recognition even when partitions seem empty.
  3. LVM physical volumes carry metadata that lets volume groups manage underlying extents.
  4. Device discovery and actual filesystem or LVM creation are separate operations.

Explanation

Correct Answer

C:

LVM physical volumes carry metadata that lets volume groups manage underlying extents. This explains the task's initial state: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. The supported lab action is: On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures.

Incorrect Answers

A:

`-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.

B:

Stale signatures can affect device recognition even when partitions seem empty. This mechanism applies to another scenario: A lab disk appears to contain an old filesystem signature after a supposedly blank virtual disk is attached. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 180

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

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

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

B:

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

C:

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