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 57

Question 560

After completing this practical task on a disposable RHEL10 training node: A shell session creates files with default modes exposing group-readable secrets to unrelated users. Which operational safeguard helps keep the result correct and safe?

  1. Use narrowly timed diagnostics and restore enforcing mode after analyzing denial logs.
  2. Check runtime and configured SELinux modes after policy changes.
  3. Set a restrictive umask in service startup or trusted shell policy for secret handling.
  4. Provision and rotate private keys under managed mode and ownership controls.

Explanation

Correct Answer

C:

Set a restrictive umask in service startup or trusted shell policy for secret handling. This guards against recurrence of: A umask subtracts permission bits from default requested modes at object creation. Confirm the lab's final state by: A normal new file is mode `600` or more restrictive and a new directory is mode `700` or more restrictive.

Incorrect Answers

A:

Use narrowly timed diagnostics and restore enforcing mode after analyzing denial logs. That control is best suited to a separate scenario: An administrator temporarily changes SELinux to permissive mode for diagnostics and believes it will remain so after reboot. It is not the best safeguard for the current mechanism: A umask subtracts permission bits from default requested modes at object creation.

B:

Check runtime and configured SELinux modes after policy changes. That control is best suited to a separate scenario: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. It is not the best safeguard for the current mechanism: A umask subtracts permission bits from default requested modes at object creation.

D:

Provision and rotate private keys under managed mode and ownership controls. That control is best suited to a separate scenario: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. It is not the best safeguard for the current mechanism: A umask subtracts permission bits from default requested modes at object creation.

Question 561

Lab exercise on an offline training clone: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.
  2. Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.
  3. Inspect `rpm -ql packagename` and relevant package files under `/usr/share/doc` in the offline lab.
  4. Verify the server host-key fingerprint using an out-of-band lab inventory before accepting the key.

Explanation

Correct Answer

A:

Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory. This directly addresses the lab target: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. The underlying behavior is: Broad globs and unchecked paths can expand beyond the intended temporary file scope. Verification: The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion.

Incorrect Answers

B:

Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator. This is an appropriate step for a DIFFERENT exercise, specifically: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. It does not address the required lab state, whose mechanism is: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

C:

Inspect `rpm -ql packagename` and relevant package files under `/usr/share/doc` in the offline lab. This is an appropriate step for a DIFFERENT exercise, specifically: A junior administrator wants usage examples for a locally installed system package but searches an unrelated online version. It does not address the required lab state, whose mechanism is: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

D:

Verify the server host-key fingerprint using an out-of-band lab inventory before accepting the key. This is an appropriate step for a DIFFERENT exercise, specifically: A first SSH connection warns that the server identity is unknown, and a student proposes disabling host key checks globally. It does not address the required lab state, whose mechanism is: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

Question 562

In a hands-on RHCSA practice VM, the assigned outcome was: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. What specific verification would demonstrate the target state?

  1. Output includes both capitalizations and line numbers, enabling source inspection.
  2. The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion.
  3. `ssh -o BatchMode=yes student@hostB true` succeeds using an authorized key on the isolated lab.
  4. The numeric result matches a manual sample from `/etc/passwd` and excludes strings in other fields.

Explanation

Correct Answer

B:

The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion. This check confirms the expected effect of: Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory. It distinguishes the intended result from the original failure mechanism: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

Incorrect Answers

A:

Output includes both capitalizations and line numbers, enabling source inspection. That verifies a separate lab task: An incident report contains both `ERROR` and `error`, but the investigation intentionally needs case-insensitive matching. It does not validate the implementation required here: Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.

C:

`ssh -o BatchMode=yes student@hostB true` succeeds using an authorized key on the isolated lab. That verifies a separate lab task: Two lab hosts need noninteractive operator access and password prompts interrupt file-copy automation. It does not validate the implementation required here: Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.

D:

The numeric result matches a manual sample from `/etc/passwd` and excludes strings in other fields. That verifies a separate lab task: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. It does not validate the implementation required here: Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.

Question 563

A trainee is diagnosing: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. Which root cause should they recognize before changing the system?

  1. SSH host-key validation helps prevent connecting to an impersonated endpoint.
  2. Renaming a local path with `mv` is different from duplicating it with `cp`.
  3. Broad globs and unchecked paths can expand beyond the intended temporary file scope.
  4. Hard links name the same inode and cannot ordinarily link across separate file systems.

Explanation

Correct Answer

C:

Broad globs and unchecked paths can expand beyond the intended temporary file scope. This explains the task's initial state: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. The supported lab action is: Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.

Incorrect Answers

A:

SSH host-key validation helps prevent connecting to an impersonated endpoint. This mechanism applies to another scenario: A first SSH connection warns that the server identity is unknown, and a student proposes disabling host key checks globally. The given lab state instead requires the more specific cause in the correct choice.

B:

Renaming a local path with `mv` is different from duplicating it with `cp`. This mechanism applies to another scenario: A team must rename a log file atomically inside one local file system before starting a new capture. The given lab state instead requires the more specific cause in the correct choice.

D:

Hard links name the same inode and cannot ordinarily link across separate file systems. This mechanism applies to another scenario: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. The given lab state instead requires the more specific cause in the correct choice.

Question 564

For this Linux administration lab: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. Which safety and lifecycle check best prevents the same problem returning?

  1. Select metadata-preserving copy flags only when ownership and permissions are intentionally retained.
  2. Start scripted changes with an explicit `cd` guarded by failure checking and record the resolved target path.
  3. Constrain glob paths and check match existence before iterating over files.
  4. Require a dry-run match review before removing files in scripted maintenance jobs.

Explanation

Correct Answer

D:

Require a dry-run match review before removing files in scripted maintenance jobs. This guards against recurrence of: Broad globs and unchecked paths can expand beyond the intended temporary file scope. Confirm the lab's final state by: The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion.

Incorrect Answers

A:

Select metadata-preserving copy flags only when ownership and permissions are intentionally retained. That control is best suited to a separate scenario: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. It is not the best safeguard for the current mechanism: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

B:

Start scripted changes with an explicit `cd` guarded by failure checking and record the resolved target path. That control is best suited to a separate scenario: On a disposable RHEL 10 training host, an operator enters a nested work directory but later edits the wrong file because the current path was assumed. It is not the best safeguard for the current mechanism: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

C:

Constrain glob paths and check match existence before iterating over files. That control is best suited to a separate scenario: A shell script is supposed to process every `.conf` file, but its wildcard is quoted as a single literal. It is not the best safeguard for the current mechanism: Broad globs and unchecked paths can expand beyond the intended temporary file scope.

Question 565

A student working on a local virtualization classroom receives this assignment: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. Which answer gives the correct practical approach?

  1. Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`.
  2. Use the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax.
  3. Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.
  4. Use `if test -f /etc/hosts; then echo present; else exit 1; fi` in a shell script.

Explanation

Correct Answer

B:

Use the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax. This directly addresses the lab target: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. The underlying behavior is: The shebang selects an interpreter; shell-specific syntax is not universal across implementations. Verification: `head -n 1 script` shows the interpreter and direct execution uses the expected Bash features.

Incorrect Answers

A:

Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`. This is an appropriate step for a DIFFERENT exercise, specifically: A daily job must print only directories under a sample tree but currently loops through both files and directories. It does not address the required lab state, whose mechanism is: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

C:

Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation. This is an appropriate step for a DIFFERENT exercise, specifically: A maintenance script must report whether a given process name exists without exiting with a misleading success status. It does not address the required lab state, whose mechanism is: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

D:

Use `if test -f /etc/hosts; then echo present; else exit 1; fi` in a shell script. This is an appropriate step for a DIFFERENT exercise, specifically: A lab script must exit successfully only when `/etc/hosts` exists, but an unguarded command reports success in both cases. It does not address the required lab state, whose mechanism is: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

Question 566

You have attempted this task on a local virtualization classroom: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. Which command output or observation best confirms its success?

  1. A simulated directory creation failure stops the script before any misleading success message.
  2. The printed host label matches `hostname -s` without treating it as an executable.
  3. `head -n 1 script` shows the interpreter and direct execution uses the expected Bash features.
  4. Arguments containing spaces are printed as single intended entries and the loop count matches input count.

Explanation

Correct Answer

C:

`head -n 1 script` shows the interpreter and direct execution uses the expected Bash features. This check confirms the expected effect of: Use the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax. It distinguishes the intended result from the original failure mechanism: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

Incorrect Answers

A:

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 the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax.

B:

The printed host label matches `hostname -s` without treating it as an executable. That verifies a separate lab task: A shell script writes raw command output but needs its first line to include the current hostname from the target host. It does not validate the implementation required here: Use the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax.

D:

Arguments containing spaces are printed as single intended entries and the loop count matches input count. That verifies a separate lab task: A housekeeping script must print each user-provided directory rather than always print one hard-coded value. It does not validate the implementation required here: Use the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax.

Question 567

Troubleshoot the following RHEL 10 lab situation: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. Identify the key Linux mechanism behind the issue.

  1. `read` without `-r` can treat backslashes as escapes.
  2. Single quotes suppress shell substitutions; double-quoted variable expansion preserves values.
  3. Shell test numeric operators compare integers, while lexical string operations do not model number magnitude.
  4. The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

Explanation

Correct Answer

D:

The shebang selects an interpreter; shell-specific syntax is not universal across implementations. This explains the task's initial state: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. The supported lab action is: Use the intended `#!/usr/bin/bash` shebang and invoke the script directly after `chmod +x`, or rewrite it in portable POSIX syntax.

Incorrect Answers

A:

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

B:

Single quotes suppress shell substitutions; double-quoted variable expansion preserves values. This mechanism applies to another scenario: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. The given lab state instead requires the more specific cause in the correct choice.

C:

Shell test numeric operators compare integers, while lexical string operations do not model number magnitude. This mechanism applies to another scenario: A script's `if` statement tests a numeric threshold using string comparison and misorders the values 9 and 10. The given lab state instead requires the more specific cause in the correct choice.

Question 568

Following lab verification, document the preventive or persistence-oriented procedure for: A shell helper is executed with `/bin/sh` but contains Bash-only syntax and fails on an alternate POSIX shell. Which practice is most suitable?

  1. Declare interpreter requirements and run shell syntax checks before deployment.
  2. Define script usage and test invalid argument counts.
  3. Quote variables unless deliberate splitting is required and tested.
  4. Use predictable timestamp formats and validate generated filenames.

Explanation

Correct Answer

A:

Declare interpreter requirements and run shell syntax checks before deployment. This guards against recurrence of: The shebang selects an interpreter; shell-specific syntax is not universal across implementations. Confirm the lab's final state by: `head -n 1 script` shows the interpreter and direct execution uses the expected Bash features.

Incorrect Answers

B:

Define script usage and test invalid argument counts. That control is best suited to a separate scenario: A shell script receives `source` and `destination` as positional parameters and currently copies an empty path when arguments are missing. It is not the best safeguard for the current mechanism: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

C:

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: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

D:

Use predictable timestamp formats and validate generated filenames. That control is best suited to a separate scenario: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. It is not the best safeguard for the current mechanism: The shebang selects an interpreter; shell-specific syntax is not universal across implementations.

Question 569

On a nonproduction Linux administration sandbox, perform the following practical task: An application service fails to start but an administrator looks only at its unit's enabled state. Which action should be carried out after confirming the lab prerequisites?

  1. Use `sudo systemctl set-default multi-user.target` on the disposable training VM.
  2. Use the systemd boot or supported recovery procedure to reach `rescue.target` from an authorized local VM console.
  3. Use `journalctl -u labworker.service -b --no-pager` and inspect `systemctl status labworker.service` for the actual failure.
  4. Use `scp -p /tmp/diagnostics.tgz student@labhost:/home/student/` with an authenticated host key.

Explanation

Correct Answer

C:

Use `journalctl -u labworker.service -b --no-pager` and inspect `systemctl status labworker.service` for the actual failure. This directly addresses the lab target: An application service fails to start but an administrator looks only at its unit's enabled state. The underlying behavior is: Service enablement controls boot dependencies; it does not establish successful execution. Verification: The relevant exit status and journal error identify the cause, not merely whether the unit is enabled.

Incorrect Answers

A:

Use `sudo systemctl set-default multi-user.target` on the disposable training VM. This is an appropriate step for a DIFFERENT exercise, specifically: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. It does not address the required lab state, whose mechanism is: Service enablement controls boot dependencies; it does not establish successful execution.

B:

Use the systemd boot or supported recovery procedure to reach `rescue.target` from an authorized local VM console. This is an appropriate step for a DIFFERENT exercise, specifically: A VM has a misconfigured service and requires recovery operations in an isolated rescue target. It does not address the required lab state, whose mechanism is: Service enablement controls boot dependencies; it does not establish successful execution.

D:

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: Service enablement controls boot dependencies; it does not establish successful execution.

Question 570

The lab examiner asks for evidence after this assignment: An application service fails to start but an administrator looks only at its unit's enabled state. What is the decisive verification step?

  1. The host restarts cleanly, and journal boot IDs show the new boot.
  2. The host presents the expected rescue environment where the affected service can be repaired.
  3. The intended service listens on the expected IP/port before any firewall modification is made.
  4. The relevant exit status and journal error identify the cause, not merely whether the unit is enabled.

Explanation

Correct Answer

D:

The relevant exit status and journal error identify the cause, not merely whether the unit is enabled. This check confirms the expected effect of: Use `journalctl -u labworker.service -b --no-pager` and inspect `systemctl status labworker.service` for the actual failure. It distinguishes the intended result from the original failure mechanism: Service enablement controls boot dependencies; it does not establish successful execution.

Incorrect Answers

A:

The host restarts cleanly, and journal boot IDs show the new boot. That verifies a separate lab task: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. It does not validate the implementation required here: Use `journalctl -u labworker.service -b --no-pager` and inspect `systemctl status labworker.service` for the actual failure.

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: Use `journalctl -u labworker.service -b --no-pager` and inspect `systemctl status labworker.service` for the actual failure.

C:

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: Use `journalctl -u labworker.service -b --no-pager` and inspect `systemctl status labworker.service` for the actual failure.