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 38

Question 370

In a hands-on RHCSA practice VM, the assigned outcome was: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. What specific verification would demonstrate the target state?

  1. Only directory entries appear while ordinary files are skipped.
  2. A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs.
  3. Arguments containing spaces are printed as single intended entries and the loop count matches input count.
  4. A simulated directory creation failure stops the script before any misleading success message.

Explanation

Correct Answer

B:

A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs. This check confirms the expected effect of: Use `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input. It distinguishes the intended result from the original failure mechanism: `read` without `-r` can treat backslashes as escapes.

Incorrect Answers

A:

Only directory entries appear while ordinary files are skipped. That verifies a separate lab task: A daily job must print only directories under a sample tree but currently loops through both files and directories. It does not validate the implementation required here: Use `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input.

C:

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 `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input.

D:

A simulated directory creation failure stops the script before any misleading success message. That verifies a separate lab task: A backup script runs even when its destination directory cannot be created, silently losing its output. It does not validate the implementation required here: Use `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input.

Question 371

A trainee is diagnosing: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. Which root cause should they recognize before changing the system?

  1. An exact process-name match requires `-x` instead of a broad substring search.
  2. Unquoted shell variable expansion performs splitting and pathname expansion.
  3. `read` without `-r` can treat backslashes as escapes.
  4. A `for` loop explicitly processes each named input rather than repeating one static check.

Explanation

Correct Answer

C:

`read` without `-r` can treat backslashes as escapes. This explains the task's initial state: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. The supported lab action is: Use `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input.

Incorrect Answers

A:

An exact process-name match requires `-x` instead of a broad substring search. This mechanism applies to another scenario: A maintenance script must report whether a given process name exists without exiting with a misleading success status. 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:

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.

Question 372

For this Linux administration lab: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. Which safety and lifecycle check best prevents the same problem returning?

  1. Quote substituted variables and test outputs when constructing paths or configuration.
  2. Test mixed file-and-directory fixtures before relying on loops.
  3. Declare runtime prerequisites, command paths and required environment variables in scheduled scripts.
  4. Use literal input mode for untrusted or structured strings.

Explanation

Correct Answer

D:

Use literal input mode for untrusted or structured strings. This guards against recurrence of: `read` without `-r` can treat backslashes as escapes. Confirm the lab's final state by: A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs.

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: `read` without `-r` can treat backslashes as escapes.

B:

Test mixed file-and-directory fixtures before relying on loops. That control is best suited to a separate scenario: A daily job must print only directories under a sample tree but currently loops through both files and directories. It is not the best safeguard for the current mechanism: `read` without `-r` can treat backslashes as escapes.

C:

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: `read` without `-r` can treat backslashes as escapes.

Question 373

A student working on a local virtualization classroom receives this assignment: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. Which answer gives the correct practical approach?

  1. Run `sudo tuned-adm list`, select an installed suitable profile using `sudo tuned-adm profile throughput-performance`.
  2. Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.
  3. Use `scp -p /tmp/diagnostics.tgz student@labhost:/home/student/` with an authenticated host key.
  4. Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.

Explanation

Correct Answer

B:

Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary. This directly addresses the lab target: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. The underlying behavior is: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not. Verification: `ps -p <verified-pid>` no longer returns the task and other matching-name processes survive.

Incorrect Answers

A:

Run `sudo tuned-adm list`, select an installed suitable profile using `sudo tuned-adm profile throughput-performance`. This is an appropriate step for a DIFFERENT exercise, specifically: The team wants a consistent throughput-oriented system tuning profile during a disposable performance experiment. It does not address the required lab state, whose mechanism is: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

C:

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: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

D:

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: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

Question 374

You have attempted this task on a local virtualization classroom: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. Which command output or observation best confirms its success?

  1. The destination file exists with expected checksum and SSH encrypted transport.
  2. The VM reaches its powered-off state rather than returning to login after restart.
  3. `ps -p <verified-pid>` no longer returns the task and other matching-name processes survive.
  4. The intended service listens on the expected IP/port before any firewall modification is made.

Explanation

Correct Answer

C:

`ps -p <verified-pid>` no longer returns the task and other matching-name processes survive. This check confirms the expected effect of: Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary. It distinguishes the intended result from the original failure mechanism: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

Incorrect Answers

A:

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: Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.

B:

The VM reaches its powered-off state rather than returning to login after restart. That verifies a separate lab task: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. It does not validate the implementation required here: Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.

D:

The intended service listens on the expected IP/port before any firewall modification is made. That verifies a separate lab task: A listening service appears healthy but clients cannot connect, and the administrator must distinguish service binding from firewall failures. It does not validate the implementation required here: Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.

Question 375

Troubleshoot the following RHEL 10 lab situation: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. Identify the key Linux mechanism behind the issue.

  1. Systemd caches unit definitions until its manager configuration is reloaded.
  2. Allocated swap usage is not by itself proof of active memory exhaustion or a leak.
  3. Service enablement controls boot dependencies; it does not establish successful execution.
  4. Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

Explanation

Correct Answer

D:

Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not. This explains the task's initial state: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. The supported lab action is: Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.

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.

B:

Allocated swap usage is not by itself proof of active memory exhaustion or a leak. This mechanism applies to another scenario: A running VM has adequate memory by `free -h` but swap usage spikes and the team assumes the application is leaking. The given lab state instead requires the more specific cause in the correct choice.

C:

Service enablement controls boot dependencies; it does not establish successful execution. This mechanism applies to another scenario: An application service fails to start but an administrator looks only at its unit's enabled state. The given lab state instead requires the more specific cause in the correct choice.

Question 376

Following lab verification, document the preventive or persistence-oriented procedure for: A noncritical lab job ignores a termination request, but its process remains and an admin proposes killing all similarly named jobs. Which practice is most suitable?

  1. Use verified PIDs and graceful termination before forced process removal.
  2. Include interface-specific listener verification in network service acceptance tests.
  3. Maintain documented persistent journal storage and retention limits for troubleshooting.
  4. Record target changes and verify a console login path before reboot.

Explanation

Correct Answer

A:

Use verified PIDs and graceful termination before forced process removal. This guards against recurrence of: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not. Confirm the lab's final state by: `ps -p <verified-pid>` no longer returns the task and other matching-name processes survive.

Incorrect Answers

B:

Include interface-specific listener verification in network service acceptance tests. That control is best suited to a separate scenario: A listening service appears healthy but clients cannot connect, and the administrator must distinguish service binding from firewall failures. It is not the best safeguard for the current mechanism: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

C:

Maintain documented persistent journal storage and retention limits for troubleshooting. That control is best suited to a separate scenario: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. It is not the best safeguard for the current mechanism: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

D:

Record target changes and verify a console login path before reboot. That control is best suited to a separate scenario: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. It is not the best safeguard for the current mechanism: Signals target specific PIDs; SIGTERM permits graceful cleanup whereas SIGKILL does not.

Question 377

On a nonproduction Linux administration sandbox, perform the following practical task: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. Which action should be carried out after confirming the lab prerequisites?

  1. After independently confirming `/dev/vdb` is the disposable target, run `parted -s /dev/vdb mklabel gpt`.
  2. Run `pvmove` only if extents need migration, then `vgreduce vg_training /dev/vdd1` after verifying PV free status.
  3. Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV.
  4. Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`.

Explanation

Correct Answer

C:

Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV. This directly addresses the lab target: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. The underlying behavior is: Logical volume capacity and filesystem capacity are distinct layers. Verification: `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.

Incorrect Answers

A:

After independently confirming `/dev/vdb` is the disposable target, run `parted -s /dev/vdb mklabel gpt`. This is an appropriate step for a DIFFERENT exercise, specifically: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. It does not address the required lab state, whose mechanism is: Logical volume capacity and filesystem capacity are distinct layers.

B:

Run `pvmove` only if extents need migration, then `vgreduce vg_training /dev/vdd1` after verifying PV free status. This is an appropriate step for a DIFFERENT exercise, specifically: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. It does not address the required lab state, whose mechanism is: Logical volume capacity and filesystem capacity are distinct layers.

D:

Initialize the verified new PV and run `vgextend vg_training /dev/vdd1`. This is an appropriate step for a DIFFERENT exercise, specifically: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. It does not address the required lab state, whose mechanism is: Logical volume capacity and filesystem capacity are distinct layers.

Question 378

The lab examiner asks for evidence after this assignment: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. What is the decisive verification step?

  1. `vgs vg_training` displays the total size and `pvs` maps both PVs to the group.
  2. After reboot `findmnt` resolves the same filesystem despite the changed volatile device name.
  3. The report accurately explains why a constrained allocation on the first PV differs from total VG capacity.
  4. `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.

Explanation

Correct Answer

D:

`lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth. This check confirms the expected effect of: Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV. It distinguishes the intended result from the original failure mechanism: Logical volume capacity and filesystem capacity are distinct layers.

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: Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV.

B:

After reboot `findmnt` resolves the same filesystem despite the changed volatile device name. That verifies a separate lab task: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It does not validate the implementation required here: Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV.

C:

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: Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV.

Question 379

A training host has this situation: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. Which system behavior best explains the original failure or risk?

  1. Logical volume capacity and filesystem capacity are distinct layers.
  2. A GPT partition requires explicit start/end boundaries; unsafe offsets can overlap or misalign data.
  3. Device names can change and `lsblk` alone does not authorize destructive partition operations.
  4. LVM `-r` invokes filesystem resize handling, unlike block-only extension.

Explanation

Correct Answer

A:

Logical volume capacity and filesystem capacity are distinct layers. This explains the task's initial state: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. The supported lab action is: Run `lvextend -L +1G /dev/vg_training/lv_db` after verifying free extents and the intended LV.

Incorrect Answers

B:

A GPT partition requires explicit start/end boundaries; unsafe offsets can overlap or misalign data. This mechanism applies to another scenario: A verified blank GPT training disk needs one new 1 GiB partition with appropriate alignment. The given lab state instead requires the more specific cause in the correct choice.

C:

Device names can change and `lsblk` alone does not authorize destructive partition operations. This mechanism applies to another scenario: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 380

A student has implemented the following configuration: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. What repeatable control best reduces regressions or unsafe changes?

  1. Require unmount, backup and dependency review before LV retirement.
  2. Plan LV resizing and compatible filesystem growth as separate verified steps.
  3. Perform non-destructive detection before initializing any storage metadata.
  4. Monitor free-extents capacity and set thresholds before service expansion.

Explanation

Correct Answer

B:

Plan LV resizing and compatible filesystem growth as separate verified steps. This guards against recurrence of: Logical volume capacity and filesystem capacity are distinct layers. Confirm the lab's final state by: `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.

Incorrect Answers

A:

Require unmount, backup and dependency review before LV retirement. That control is best suited to a separate scenario: A test operator removed a block LV without first unmounting it, risking a busy-device error or data loss. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.

C:

Perform non-destructive detection before initializing any storage metadata. That control is best suited to a separate scenario: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.

D:

Monitor free-extents capacity and set thresholds before service expansion. That control is best suited to a separate scenario: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.