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 34

Question 330

The lab examiner asks for evidence after this assignment: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. What is the decisive verification step?

  1. The output contains one result per unit and no unrequested service is started.
  2. A fixture with no matches reports zero while actual unreadable-file errors remain flagged.
  3. The resulting filename contains the current date digits and `tar -tzf` lists expected members.
  4. The script runs under a restricted environment and resolves required binaries.

Explanation

Correct Answer

D:

The script runs under a restricted environment and resolves required binaries. This check confirms the expected effect of: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script. It distinguishes the intended result from the original failure mechanism: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

Incorrect Answers

A:

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 a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.

B:

A fixture with no matches reports zero while actual unreadable-file errors remain flagged. That verifies a separate lab task: 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 does not validate the implementation required here: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.

C:

The resulting filename contains the current date digits and `tar -tzf` lists expected members. That verifies a separate lab task: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. It does not validate the implementation required here: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.

Question 331

A training host has this situation: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. Which system behavior best explains the original failure or risk?

  1. Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.
  2. A nonzero command status must be checked when later actions depend on it.
  3. `read` without `-r` can treat backslashes as escapes.
  4. A shell condition requires an explicit test and controlled success/failure branches.

Explanation

Correct Answer

A:

Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization. This explains the task's initial state: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. The supported lab action is: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.

Incorrect Answers

B:

A nonzero command status must be checked when later actions depend on it. This mechanism applies to another scenario: A backup script runs even when its destination directory cannot be created, silently losing its output. The given lab state instead requires the more specific cause in the correct choice.

C:

`read` without `-r` can treat backslashes as escapes. This mechanism applies to another scenario: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 332

A student has implemented the following configuration: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. What repeatable control best reduces regressions or unsafe changes?

  1. Quote substituted variables and test outputs when constructing paths or configuration.
  2. Declare runtime prerequisites, command paths and required environment variables in scheduled scripts.
  3. Use literal input mode for untrusted or structured strings.
  4. Choose exact process selectors and check for ambiguous multiple matches.

Explanation

Correct Answer

B:

Declare runtime prerequisites, command paths and required environment variables in scheduled scripts. This guards against recurrence of: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization. Confirm the lab's final state by: The script runs under a restricted environment and resolves required binaries.

Incorrect Answers

A:

Quote substituted variables and test outputs when constructing paths or configuration. That control is best suited to a separate scenario: A shell script writes raw command output but needs its first line to include the current hostname from the target host. It is not the best safeguard for the current mechanism: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

C:

Use literal input mode for untrusted or structured strings. That control is best suited to a separate scenario: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. It is not the best safeguard for the current mechanism: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

D:

Choose exact process selectors and check for ambiguous multiple matches. That control is best suited to a separate scenario: A maintenance script must report whether a given process name exists without exiting with a misleading success status. It is not the best safeguard for the current mechanism: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

Question 333

You are responsible for a test RHEL10 instance. The required hands-on outcome is: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. Select the most appropriate implementation step.

  1. Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.
  2. Launch it in the lab using `nice -n 10 /usr/local/bin/lab-indexer` rather than renicing afterward.
  3. Validate the new configuration and execute `sudo systemctl restart lab-daemon.service` where a restart is the supported reload mechanism.
  4. Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`.

Explanation

Correct Answer

D:

Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`. This directly addresses the lab target: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. The underlying behavior is: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated. Verification: The highest CPU-consuming fixture process appears with its PID and percentage data.

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: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

B:

Launch it in the lab using `nice -n 10 /usr/local/bin/lab-indexer` rather than renicing afterward. This is an appropriate step for a DIFFERENT exercise, specifically: A background indexing job should start with a lower CPU scheduling priority from its first instruction. It does not address the required lab state, whose mechanism is: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

C:

Validate the new configuration and execute `sudo systemctl restart lab-daemon.service` where a restart is the supported reload mechanism. This is an appropriate step for a DIFFERENT exercise, specifically: An application configuration was changed on disk, but the running daemon still uses the previous settings. It does not address the required lab state, whose mechanism is: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

Question 334

After a lab configuration change, verify: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. Which result most directly proves the desired system state?

  1. The highest CPU-consuming fixture process appears with its PID and percentage data.
  2. `ps -o ni,comm -p <pid>` shows the intended nice value for the launched job.
  3. `systemctl cat labworker.service` shows the updated directive and a controlled start honors it.
  4. The destination file exists with expected checksum and SSH encrypted transport.

Explanation

Correct Answer

A:

The highest CPU-consuming fixture process appears with its PID and percentage data. This check confirms the expected effect of: Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`. It distinguishes the intended result from the original failure mechanism: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

Incorrect Answers

B:

`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: Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`.

C:

`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: Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`.

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: Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`.

Question 335

In an EX200-style practice lab, this condition exists: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. Which explanation correctly identifies the underlying issue?

  1. Boot interruption changes early startup context and password recovery may require filesystem relabeling.
  2. Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.
  3. `isolate` changes current target state rather than the saved default target.
  4. Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

Explanation

Correct Answer

B:

Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated. This explains the task's initial state: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. The supported lab action is: Run `ps -eo pid,comm,%cpu,%mem --sort=-%cpu | head` and corroborate with `top`.

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.

C:

`isolate` changes current target state rather than the saved default target. This mechanism applies to another scenario: A technician needs to switch the currently running lab host from its GUI session to a non-graphical target without changing future boots. The given lab state instead requires the more specific cause in the correct choice.

D:

Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not. This mechanism applies to another scenario: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. The given lab state instead requires the more specific cause in the correct choice.

Question 336

After completing this practical task on a test RHEL10 instance: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. Which operational safeguard helps keep the result correct and safe?

  1. Include explicit action and target hostname in approved shutdown runbooks.
  2. Keep tested console recovery access and backup before rescue-target maintenance.
  3. Collect evidence and identify process ownership before choosing a corrective signal.
  4. Schedule batch tasks with appropriate priority and monitor the impact rather than stopping critical processes.

Explanation

Correct Answer

C:

Collect evidence and identify process ownership before choosing a corrective signal. This guards against recurrence of: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated. Confirm the lab's final state by: The highest CPU-consuming fixture process appears with its PID and percentage data.

Incorrect Answers

A:

Include explicit action and target hostname in approved shutdown runbooks. That control is best suited to a separate scenario: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. It is not the best safeguard for the current mechanism: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

B:

Keep tested console recovery access and backup before rescue-target maintenance. That control is best suited to a separate scenario: A VM has a misconfigured service and requires recovery operations in an isolated rescue target. It is not the best safeguard for the current mechanism: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

D:

Schedule batch tasks with appropriate priority and monitor the impact rather than stopping critical processes. That control is best suited to a separate scenario: A batch reporting program interferes with interactive tasks, and the goal is to reduce its scheduling priority while it remains active. It is not the best safeguard for the current mechanism: Process metrics identify resource consumers; a performance problem is not proof that the process should be terminated.

Question 337

Lab exercise on an isolated enterprise lab VM: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`.
  2. 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.
  3. On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures.
  4. Run `pvs -o pv_name,vg_name,pv_free` and `vgs` to distinguish per-PV free extents from VG aggregate free extents.

Explanation

Correct Answer

A:

Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`. This directly addresses the lab target: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. The underlying behavior is: A volume group does not gain capacity just because a new disk is visible to Linux. Verification: `vgs vg_training` reports increased free space and `pvs` shows the new member assigned.

Incorrect Answers

B:

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: A volume group does not gain capacity just because a new disk is visible to Linux.

C:

On the verified disposable device, run `pvcreate /dev/vdb1` after checking `wipefs -n /dev/vdb1` for unexpected signatures. This is an appropriate step for a DIFFERENT exercise, specifically: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. It does not address the required lab state, whose mechanism is: A volume group does not gain capacity just because a new disk is visible to Linux.

D:

Run `pvs -o pv_name,vg_name,pv_free` and `vgs` to distinguish per-PV free extents from VG aggregate free extents. This is an appropriate step for a DIFFERENT exercise, specifically: A training PV reports little free space while its VG appears to have ample total capacity across a second PV. It does not address the required lab state, whose mechanism is: A volume group does not gain capacity just because a new disk is visible to Linux.

Question 338

In a hands-on RHCSA practice VM, the assigned outcome was: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. What specific verification would demonstrate the target state?

  1. `lvs vg_training` no longer lists the retired LV and unrelated LVs remain.
  2. `vgs vg_training` reports increased free space and `pvs` shows the new member assigned.
  3. The observed signatures are documented without erasing data and a different populated disk remains untouched.
  4. `lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents.

Explanation

Correct Answer

B:

`vgs vg_training` reports increased free space and `pvs` shows the new member assigned. This check confirms the expected effect of: Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`. It distinguishes the intended result from the original failure mechanism: A volume group does not gain capacity just because a new disk is visible to Linux.

Incorrect Answers

A:

`lvs vg_training` no longer lists the retired LV and unrelated LVs remain. That verifies a separate lab task: A test operator removed a block LV without first unmounting it, risking a busy-device error or data loss. It does not validate the implementation required here: Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`.

C:

The observed signatures are documented without erasing data and a different populated disk remains untouched. That verifies a separate lab task: A lab disk appears to contain an old filesystem signature after a supposedly blank virtual disk is attached. It does not validate the implementation required here: Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`.

D:

`lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents. That verifies a separate lab task: An LV should consume precisely 20% of remaining free extents for a training scratch workload. It does not validate the implementation required here: Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`.

Question 339

A trainee is diagnosing: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. Which root cause should they recognize before changing the system?

  1. A logical volume is not active swap until formatted with swap metadata and enabled.
  2. LVM `-r` invokes filesystem resize handling, unlike block-only extension.
  3. A volume group does not gain capacity just because a new disk is visible to Linux.
  4. Swap can reside on a partition or LV but still needs swap metadata and activation.

Explanation

Correct Answer

C:

A volume group does not gain capacity just because a new disk is visible to Linux. This explains the task's initial state: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. The supported lab action is: Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`.

Incorrect Answers

A:

A logical volume is not active swap until formatted with swap metadata and enabled. This mechanism applies to another scenario: A small swap logical volume on a training host is inactive after it has been created. The given lab state instead requires the more specific cause in the correct choice.

B:

LVM `-r` invokes filesystem resize handling, unlike block-only extension. This mechanism applies to another scenario: An administrator wants to grow a logical volume and its XFS filesystem together for a disposable data directory. The given lab state instead requires the more specific cause in the correct choice.

D:

Swap can reside on a partition or LV but still needs swap metadata and activation. This mechanism applies to another scenario: A VM needs a dedicated 1 GiB swap partition on an explicitly empty GPT training disk instead of an LVM swap LV. The given lab state instead requires the more specific cause in the correct choice.

Question 340

For this Linux administration lab: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. Which safety and lifecycle check best prevents the same problem returning?

  1. Confirm exact partition number, holders and backups before partition deletion.
  2. Plan LV resizing and compatible filesystem growth as separate verified steps.
  3. Make disk identification a mandatory gate; never run `mklabel` on a disk with live data.
  4. Track approved PV additions in capacity records and test before growing filesystems.

Explanation

Correct Answer

D:

Track approved PV additions in capacity records and test before growing filesystems. This guards against recurrence of: A volume group does not gain capacity just because a new disk is visible to Linux. Confirm the lab's final state by: `vgs vg_training` reports increased free space and `pvs` shows the new member assigned.

Incorrect Answers

A:

Confirm exact partition number, holders and backups before partition deletion. That control is best suited to a separate scenario: A trainee needs to delete one unused partition on a disposable GPT disk but proposes erasing the whole disk. It is not the best safeguard for the current mechanism: A volume group does not gain capacity just because a new disk is visible to Linux.

B:

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 does not gain capacity just because a new disk is visible to Linux.

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: A volume group does not gain capacity just because a new disk is visible to Linux.