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 30

Question 290

In a hands-on RHCSA practice VM, the assigned outcome was: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. What specific verification would demonstrate the target state?

  1. The script runs under a restricted environment and resolves required binaries.
  2. The file `/tmp/lab reports/status.txt` receives the line and no extra files are created.
  3. A simulated directory creation failure stops the script before any misleading success message.
  4. The resulting filename contains the current date digits and `tar -tzf` lists expected members.

Explanation

Correct Answer

B:

The file `/tmp/lab reports/status.txt` receives the line and no extra files are created. This check confirms the expected effect of: Use `printf '%s\n' "$message" >> "$log_path"` with a quoted destination variable. It distinguishes the intended result from the original failure mechanism: Unquoted shell variable expansion performs splitting and pathname expansion.

Incorrect Answers

A:

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 `printf '%s\n' "$message" >> "$log_path"` with a quoted destination variable.

C:

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 `printf '%s\n' "$message" >> "$log_path"` with a quoted destination variable.

D:

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 `printf '%s\n' "$message" >> "$log_path"` with a quoted destination variable.

Question 291

A trainee is diagnosing: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. Which root cause should they recognize before changing the system?

  1. A semicolon runs subsequent commands irrespective of previous exit status; `&&` is conditional.
  2. A `for` loop explicitly processes each named input rather than repeating one static check.
  3. Unquoted shell variable expansion performs splitting and pathname expansion.
  4. Positional parameters may be absent or contain spaces, requiring validation and quoting.

Explanation

Correct Answer

C:

Unquoted shell variable expansion performs splitting and pathname expansion. This explains the task's initial state: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. The supported lab action is: Use `printf '%s\n' "$message" >> "$log_path"` with a quoted destination variable.

Incorrect Answers

A:

A semicolon runs subsequent commands irrespective of previous exit status; `&&` is conditional. This mechanism applies to another scenario: A script invokes two commands on one line with a semicolon and prints success even if the first fails. The given lab state instead requires the more specific cause in the correct choice.

B:

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:

Positional parameters may be absent or contain spaces, requiring validation and quoting. This mechanism applies to another scenario: A shell script receives `source` and `destination` as positional parameters and currently copies an empty path when arguments are missing. The given lab state instead requires the more specific cause in the correct choice.

Question 292

For this Linux administration lab: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. Which safety and lifecycle check best prevents the same problem returning?

  1. Test mixed file-and-directory fixtures before relying on loops.
  2. Choose exact process selectors and check for ambiguous multiple matches.
  3. Check input count and quote expanded paths in every filesystem loop.
  4. Quote variables unless deliberate splitting is required and tested.

Explanation

Correct Answer

D:

Quote variables unless deliberate splitting is required and tested. This guards against recurrence of: Unquoted shell variable expansion performs splitting and pathname expansion. Confirm the lab's final state by: The file `/tmp/lab reports/status.txt` receives the line and no extra files are created.

Incorrect Answers

A:

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: Unquoted shell variable expansion performs splitting and pathname expansion.

B:

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: Unquoted shell variable expansion performs splitting and pathname expansion.

C:

Check input count and quote expanded paths in every filesystem loop. That control is best suited to a separate scenario: A housekeeping script must print each user-provided directory rather than always print one hard-coded value. It is not the best safeguard for the current mechanism: Unquoted shell variable expansion performs splitting and pathname expansion.

Question 293

A student working on a disposable RHEL10 training node receives this assignment: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. 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. 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.
  3. Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented.
  4. Send `kill -TERM <verified-pid>`, check graceful exit, and only escalate to `kill -KILL` for that confirmed PID if necessary.

Explanation

Correct Answer

B:

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 directly addresses the lab target: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. The underlying behavior is: Boot interruption changes early startup context and password recovery may require filesystem relabeling. Verification: After recovery, an authorized local login succeeds and SELinux file labels are corrected if the procedure required it.

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: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

C:

Enable supported persistent systemd journal storage, such as creating `/var/log/journal` with correct ownership and restarting `systemd-journald` as documented. This is an appropriate step for a DIFFERENT exercise, specifically: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. It does not address the required lab state, whose mechanism is: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

D:

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: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

Question 294

You have attempted this task on a disposable RHEL10 training node: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. Which command output or observation best confirms its success?

  1. `systemctl list-units --type=target --state=active` shows multi-user operation, while `get-default` remains unchanged.
  2. The host presents the expected rescue environment where the affected service can be repaired.
  3. After recovery, an authorized local login succeeds and SELinux file labels are corrected if the procedure required it.
  4. The recorded swap-in/out rates and memory pressure indicate whether active thrashing is occurring.

Explanation

Correct Answer

C:

After recovery, an authorized local login succeeds and SELinux file labels are corrected if the procedure required it. This check confirms the expected effect of: 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. It distinguishes the intended result from the original failure mechanism: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

Incorrect Answers

A:

`systemctl list-units --type=target --state=active` shows multi-user operation, while `get-default` remains unchanged. That verifies a separate lab task: A technician needs to switch the currently running lab host from its GUI session to a non-graphical target without changing future boots. It does not validate the implementation required here: 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.

B:

The host presents the expected rescue environment where the affected service can be repaired. That verifies a separate lab task: A VM has a misconfigured service and requires recovery operations in an isolated rescue target. It does not validate the implementation required here: 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.

D:

The recorded swap-in/out rates and memory pressure indicate whether active thrashing is occurring. That verifies a separate lab task: A running VM has adequate memory by `free -h` but swap usage spikes and the team assumes the application is leaking. It does not validate the implementation required here: 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.

Question 295

Troubleshoot the following RHEL 10 lab situation: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. Identify the key Linux mechanism behind the issue.

  1. Poweroff and reboot invoke different system state transitions.
  2. Service enablement controls boot dependencies; it does not establish successful execution.
  3. A masked unit points to `/dev/null`, intentionally preventing activation.
  4. Boot interruption changes early startup context and password recovery may require filesystem relabeling.

Explanation

Correct Answer

D:

Boot interruption changes early startup context and password recovery may require filesystem relabeling. This explains the task's initial state: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. The supported lab action is: 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.

Incorrect Answers

A:

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.

B:

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.

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.

Question 296

Following lab verification, document the preventive or persistence-oriented procedure for: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. Which practice is most suitable?

  1. Protect physical/virtual console access and document emergency recovery approvals.
  2. Collect evidence and identify process ownership before choosing a corrective signal.
  3. Record target changes and verify a console login path before reboot.
  4. Schedule batch tasks with appropriate priority and monitor the impact rather than stopping critical processes.

Explanation

Correct Answer

A:

Protect physical/virtual console access and document emergency recovery approvals. This guards against recurrence of: Boot interruption changes early startup context and password recovery may require filesystem relabeling. Confirm the lab's final state by: After recovery, an authorized local login succeeds and SELinux file labels are corrected if the procedure required it.

Incorrect Answers

B:

Collect evidence and identify process ownership before choosing a corrective signal. That control is best suited to a separate scenario: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. It is not the best safeguard for the current mechanism: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

C:

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: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

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: Boot interruption changes early startup context and password recovery may require filesystem relabeling.

Question 297

On an offline training clone, perform the following practical task: An LV should consume precisely 20% of remaining free extents for a training scratch workload. Which action should be carried out after confirming the lab prerequisites?

  1. Run `mkswap /dev/vg_training/lv_swap` on the dedicated empty swap LV followed by `swapon /dev/vg_training/lv_swap`.
  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. Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG.
  4. Use `vgcreate vg_training /dev/vdb1 /dev/vdc1` after confirming both are dedicated PVs.

Explanation

Correct Answer

C:

Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG. This directly addresses the lab target: An LV should consume precisely 20% of remaining free extents for a training scratch workload. The underlying behavior is: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. Verification: `lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents.

Incorrect Answers

A:

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: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

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: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

D:

Use `vgcreate vg_training /dev/vdb1 /dev/vdc1` after confirming both are dedicated PVs. This is an appropriate step for a DIFFERENT exercise, specifically: Two fresh disposable LVM partitions must become one storage pool for a new application. It does not address the required lab state, whose mechanism is: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

Question 298

The lab examiner asks for evidence after this assignment: An LV should consume precisely 20% of remaining free extents for a training scratch workload. What is the decisive verification step?

  1. `lsblk -f` reports swap type and `swapon --show` shows the correct partition.
  2. The report lists the actual PV paths and their group membership for the target LV.
  3. `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.
  4. `lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents.

Explanation

Correct Answer

D:

`lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents. This check confirms the expected effect of: Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG. It distinguishes the intended result from the original failure mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

Incorrect Answers

A:

`lsblk -f` reports swap type and `swapon --show` shows the correct partition. That verifies a separate lab task: A VM needs a dedicated 1 GiB swap partition on an explicitly empty GPT training disk instead of an LVM swap LV. It does not validate the implementation required here: Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG.

B:

The report lists the actual PV paths and their group membership for the target LV. That verifies a separate lab task: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. It does not validate the implementation required here: Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG.

C:

`lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth. That verifies a separate lab task: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. It does not validate the implementation required here: Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG.

Question 299

A training host has this situation: An LV should consume precisely 20% of remaining free extents for a training scratch workload. Which system behavior best explains the original failure or risk?

  1. `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.
  2. A logical volume is not active swap until formatted with swap metadata and enabled.
  3. A GPT partition requires explicit start/end boundaries; unsafe offsets can overlap or misalign data.
  4. LVM `-r` invokes filesystem resize handling, unlike block-only extension.

Explanation

Correct Answer

A:

`-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. This explains the task's initial state: An LV should consume precisely 20% of remaining free extents for a training scratch workload. The supported lab action is: Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG.

Incorrect Answers

B:

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.

C:

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.

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 300

A student has implemented the following configuration: An LV should consume precisely 20% of remaining free extents for a training scratch workload. What repeatable control best reduces regressions or unsafe changes?

  1. Check `vgs` free extents before provisioning and keep names consistent with service inventory.
  2. Document whether requests are byte sizes or extents before provisioning LVM.
  3. Verify extent allocation and redundancy before any VG reduction.
  4. Treat unexpected signatures as a stop-and-investigate condition, never automatic wipe permission.

Explanation

Correct Answer

B:

Document whether requests are byte sizes or extents before provisioning LVM. This guards against recurrence of: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. Confirm the lab's final state by: `lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents.

Incorrect Answers

A:

Check `vgs` free extents before provisioning and keep names consistent with service inventory. That control is best suited to a separate scenario: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

C:

Verify extent allocation and redundancy before any VG reduction. That control is best suited to a separate scenario: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

D:

Treat unexpected signatures as a stop-and-investigate condition, never automatic wipe permission. That control is best suited to a separate scenario: A lab disk appears to contain an old filesystem signature after a supposedly blank virtual disk is attached. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.