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 13

Question 120

Following lab verification, document the preventive or persistence-oriented procedure for: A web service moved to `/srv/custom-web` encounters SELinux denials because content copied from a home directory carries the wrong label. Which practice is most suitable?

  1. Persist custom path mapping in SELinux fcontext policy, not one-off `chcon` changes.
  2. Set a restrictive umask in service startup or trusted shell policy for secret handling.
  3. Audit filesystem permissions on configuration files after each deployment.
  4. Test positive and negative access after SSH authorization changes.

Explanation

Correct Answer

A:

Persist custom path mapping in SELinux fcontext policy, not one-off `chcon` changes. This guards against recurrence of: DAC permissions can be correct while SELinux type enforcement still denies access. Confirm the lab's final state by: `ls -Z /srv/custom-web/index.html` reports the expected content type and the service reads the file.

Incorrect Answers

B:

Set a restrictive umask in service startup or trusted shell policy for secret handling. That control is best suited to a separate scenario: A shell session creates files with default modes exposing group-readable secrets to unrelated users. It is not the best safeguard for the current mechanism: DAC permissions can be correct while SELinux type enforcement still denies access.

C:

Audit filesystem permissions on configuration files after each deployment. That control is best suited to a separate scenario: A user accidentally gives write permission to everyone on an application's configuration file. It is not the best safeguard for the current mechanism: DAC permissions can be correct while SELinux type enforcement still denies access.

D:

Test positive and negative access after SSH authorization changes. That control is best suited to a separate scenario: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. It is not the best safeguard for the current mechanism: DAC permissions can be correct while SELinux type enforcement still denies access.

Question 121

On an isolated enterprise lab VM, perform the following practical task: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. Which action should be carried out after confirming the lab prerequisites?

  1. Run `pwd`, then `cd /srv/labs/projectA` after checking it exists; use absolute paths for the target edit.
  2. Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.
  3. Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.
  4. Use `ssh -p 2222 student@lab-gateway` with the approved nonstandard port.

Explanation

Correct Answer

C:

Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator. This directly addresses the lab target: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. The underlying behavior is: The `>` operator truncates an existing output file, whereas `>>` appends. Verification: The prior entries remain and the newly written line appears at the end of the log.

Incorrect Answers

A:

Run `pwd`, then `cd /srv/labs/projectA` after checking it exists; use absolute paths for the target edit. This is an appropriate step for a DIFFERENT exercise, specifically: 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 does not address the required lab state, whose mechanism is: The `>` operator truncates an existing output file, whereas `>>` appends.

B:

Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory. This is an appropriate step for a DIFFERENT exercise, specifically: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. It does not address the required lab state, whose mechanism is: The `>` operator truncates an existing output file, whereas `>>` appends.

D:

Use `ssh -p 2222 student@lab-gateway` with the approved nonstandard port. This is an appropriate step for a DIFFERENT exercise, specifically: An SSH lab service listens on a deliberately nonstandard port 2222, but a tester keeps connecting to the default port. It does not address the required lab state, whose mechanism is: The `>` operator truncates an existing output file, whereas `>>` appends.

Question 122

The lab examiner asks for evidence after this assignment: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. What is the decisive verification step?

  1. `stat -c '%U:%G %a' /srv/labs/summary.txt` shows the target owner and group, and the analyst can edit under allowed group bits.
  2. `tar -tzf /tmp/projectA.tgz` lists the expected tree relative to `projectA/` without absolute paths.
  3. `id -un`, `pwd`, and `printf '%s\n' "$HOME"` reflect the privileged login context.
  4. The prior entries remain and the newly written line appears at the end of the log.

Explanation

Correct Answer

D:

The prior entries remain and the newly written line appears at the end of the log. This check confirms the expected effect of: Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator. It distinguishes the intended result from the original failure mechanism: The `>` operator truncates an existing output file, whereas `>>` appends.

Incorrect Answers

A:

`stat -c '%U:%G %a' /srv/labs/summary.txt` shows the target owner and group, and the analyst can edit under allowed group bits. That verifies a separate lab task: A text report was created by root, preventing the intended nonprivileged analyst from editing it. It does not validate the implementation required here: Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.

B:

`tar -tzf /tmp/projectA.tgz` lists the expected tree relative to `projectA/` without absolute paths. That verifies a separate lab task: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. It does not validate the implementation required here: Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.

C:

`id -un`, `pwd`, and `printf '%s\n' "$HOME"` reflect the privileged login context. That verifies a separate lab task: A student becomes root with `su` but finds the previous user's PATH and working directory still active during an administrative test. It does not validate the implementation required here: Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.

Question 123

A training host has this situation: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. Which system behavior best explains the original failure or risk?

  1. The `>` operator truncates an existing output file, whereas `>>` appends.
  2. Colon-separated account records require field-aware matching rather than substring searches.
  3. System manuals are installed sources of command syntax rather than requiring external web search.
  4. Archive extraction can create paths and overwrite files relative to the extraction root.

Explanation

Correct Answer

A:

The `>` operator truncates an existing output file, whereas `>>` appends. This explains the task's initial state: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. The supported lab action is: Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.

Incorrect Answers

B:

Colon-separated account records require field-aware matching rather than substring searches. This mechanism applies to another scenario: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. The given lab state instead requires the more specific cause in the correct choice.

C:

System manuals are installed sources of command syntax rather than requiring external web search. This mechanism applies to another scenario: The team needs the documented purpose and arguments of `systemctl` without accessing the Internet during training. The given lab state instead requires the more specific cause in the correct choice.

D:

Archive extraction can create paths and overwrite files relative to the extraction root. This mechanism applies to another scenario: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. The given lab state instead requires the more specific cause in the correct choice.

Question 124

A student has implemented the following configuration: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. What repeatable control best reduces regressions or unsafe changes?

  1. Maintain per-operator SSH keys and revoke retired keys instead of sharing passwords.
  2. Use append mode for accumulation and rotate retained logs when they exceed capacity limits.
  3. Specify desired age semantics and verify test timestamps before automating maintenance.
  4. Use hard links only for same-filesystem files and document how unlinking each name affects retention.

Explanation

Correct Answer

B:

Use append mode for accumulation and rotate retained logs when they exceed capacity limits. This guards against recurrence of: The `>` operator truncates an existing output file, whereas `>>` appends. Confirm the lab's final state by: The prior entries remain and the newly written line appears at the end of the log.

Incorrect Answers

A:

Maintain per-operator SSH keys and revoke retired keys instead of sharing passwords. That control is best suited to a separate scenario: Two lab hosts need noninteractive operator access and password prompts interrupt file-copy automation. It is not the best safeguard for the current mechanism: The `>` operator truncates an existing output file, whereas `>>` appends.

C:

Specify desired age semantics and verify test timestamps before automating maintenance. That control is best suited to a separate scenario: A large fixture tree has many similarly named files; an operator must find only files updated during the last day. It is not the best safeguard for the current mechanism: The `>` operator truncates an existing output file, whereas `>>` appends.

D:

Use hard links only for same-filesystem files and document how unlinking each name affects retention. That control is best suited to a separate scenario: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. It is not the best safeguard for the current mechanism: The `>` operator truncates an existing output file, whereas `>>` appends.

Question 125

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. Select the most appropriate implementation step.

  1. Use `flatpak install labapps org.example.Editor` after configuring the approved Flatpak remote.
  2. Repair the trusted repository signing key or certificate chain supplied by the lab rather than disabling validation.
  3. Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.
  4. Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM.

Explanation

Correct Answer

D:

Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM. This directly addresses the lab target: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. The underlying behavior is: DNF removal resolves dependencies and may remove related packages, which requires plan review. Verification: `rpm -q packagename` reports not installed and required unrelated packages remain present.

Incorrect Answers

A:

Use `flatpak install labapps org.example.Editor` after configuring the approved Flatpak remote. This is an appropriate step for a DIFFERENT exercise, specifically: A desktop lab task requires installing a named Flatpak application, but the administrator runs `dnf install` for its Flatpak ID. It does not address the required lab state, whose mechanism is: DNF removal resolves dependencies and may remove related packages, which requires plan review.

B:

Repair the trusted repository signing key or certificate chain supplied by the lab rather than disabling validation. This is an appropriate step for a DIFFERENT exercise, specifically: A repository download fails because a private package mirror certificate is not trusted, and a student proposes turning off `gpgcheck` globally. It does not address the required lab state, whose mechanism is: DNF removal resolves dependencies and may remove related packages, which requires plan review.

C:

Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes. This is an appropriate step for a DIFFERENT exercise, specifically: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. It does not address the required lab state, whose mechanism is: DNF removal resolves dependencies and may remove related packages, which requires plan review.

Question 126

After a lab configuration change, verify: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. Which result most directly proves the desired system state?

  1. `rpm -q packagename` reports not installed and required unrelated packages remain present.
  2. The target package and action appear under the expected transaction ID without guessing which manual file changed.
  3. `rpm -q httpd` reports an installed package and `dnf info httpd` shows package metadata.
  4. `flatpak remotes` lists the approved remote and its actual configured URL.

Explanation

Correct Answer

A:

`rpm -q packagename` reports not installed and required unrelated packages remain present. This check confirms the expected effect of: Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM. It distinguishes the intended result from the original failure mechanism: DNF removal resolves dependencies and may remove related packages, which requires plan review.

Incorrect Answers

B:

The target package and action appear under the expected transaction ID without guessing which manual file changed. That verifies a separate lab task: A student must audit a recently updated package and identify whether a DNF transaction caused a regression. It does not validate the implementation required here: Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM.

C:

`rpm -q httpd` reports an installed package and `dnf info httpd` shows package metadata. That verifies a separate lab task: A test server needs the packaged `httpd` service but an administrator tries to install files by manual copying. It does not validate the implementation required here: Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM.

D:

`flatpak remotes` lists the approved remote and its actual configured URL. That verifies a separate lab task: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. It does not validate the implementation required here: Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM.

Question 127

In an EX200-style practice lab, this condition exists: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. Which explanation correctly identifies the underlying issue?

  1. DNF can resolve local-RPM dependencies using available repository metadata whereas raw copying cannot.
  2. DNF removal resolves dependencies and may remove related packages, which requires plan review.
  3. RPM package management installs files, dependencies and lifecycle metadata that ad hoc copying lacks.
  4. Unsigned or untrusted repository sources should not be implicitly accepted just to satisfy an install.

Explanation

Correct Answer

B:

DNF removal resolves dependencies and may remove related packages, which requires plan review. This explains the task's initial state: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. The supported lab action is: Run `sudo dnf remove packagename` after inspecting the dependency removal plan on the disposable VM.

Incorrect Answers

A:

DNF can resolve local-RPM dependencies using available repository metadata whereas raw copying cannot. This mechanism applies to another scenario: A lab host cannot install a local signed RPM because an engineer assumes a bare filename will automatically resolve dependency packages. The given lab state instead requires the more specific cause in the correct choice.

C:

RPM package management installs files, dependencies and lifecycle metadata that ad hoc copying lacks. This mechanism applies to another scenario: A test server needs the packaged `httpd` service but an administrator tries to install files by manual copying. The given lab state instead requires the more specific cause in the correct choice.

D:

Unsigned or untrusted repository sources should not be implicitly accepted just to satisfy an install. This mechanism applies to another scenario: A repository download fails because a private package mirror certificate is not trusted, and a student proposes turning off `gpgcheck` globally. The given lab state instead requires the more specific cause in the correct choice.

Question 128

After completing this practical task on a disposable RHEL10 training node: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. Which operational safeguard helps keep the result correct and safe?

  1. Document both package manager and approved source when installing GUI applications.
  2. Review unused runtime cleanup separately and record approved desktop application removals.
  3. Review transaction proposals and preserve business data before package retirement.
  4. Confirm target host identity and deployment scope before every package change.

Explanation

Correct Answer

C:

Review transaction proposals and preserve business data before package retirement. This guards against recurrence of: DNF removal resolves dependencies and may remove related packages, which requires plan review. Confirm the lab's final state by: `rpm -q packagename` reports not installed and required unrelated packages remain present.

Incorrect Answers

A:

Document both package manager and approved source when installing GUI applications. That control is best suited to a separate scenario: A desktop lab task requires installing a named Flatpak application, but the administrator runs `dnf install` for its Flatpak ID. It is not the best safeguard for the current mechanism: DNF removal resolves dependencies and may remove related packages, which requires plan review.

B:

Review unused runtime cleanup separately and record approved desktop application removals. That control is best suited to a separate scenario: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. It is not the best safeguard for the current mechanism: DNF removal resolves dependencies and may remove related packages, which requires plan review.

D:

Confirm target host identity and deployment scope before every package change. That control is best suited to a separate scenario: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. It is not the best safeguard for the current mechanism: DNF removal resolves dependencies and may remove related packages, which requires plan review.

Question 129

Lab exercise on an offline training clone: A shell script receives `source` and `destination` as positional parameters and currently copies an empty path when arguments are missing. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command.
  2. Use `first_command && second_command` when the second action must depend on the first succeeding.
  3. Use `for unit in sshd crond chronyd firewalld NetworkManager; do systemctl is-active "$unit"; done`.
  4. Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`.

Explanation

Correct Answer

A:

Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command. This directly addresses the lab target: A shell script receives `source` and `destination` as positional parameters and currently copies an empty path when arguments are missing. The underlying behavior is: Positional parameters may be absent or contain spaces, requiring validation and quoting. Verification: Two valid paths work and calling with only one argument returns exit code 2 without copying.

Incorrect Answers

B:

Use `first_command && second_command` when the second action must depend on the first succeeding. This is an appropriate step for a DIFFERENT exercise, specifically: A script invokes two commands on one line with a semicolon and prints success even if the first fails. It does not address the required lab state, whose mechanism is: Positional parameters may be absent or contain spaces, requiring validation and quoting.

C:

Use `for unit in sshd crond chronyd firewalld NetworkManager; do systemctl is-active "$unit"; done`. This is an appropriate step for a DIFFERENT exercise, specifically: A service check is intended to poll five named systemd units, but the script uses only the first literal unit. It does not address the required lab state, whose mechanism is: Positional parameters may be absent or contain spaces, requiring validation and quoting.

D:

Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`. This is an appropriate step for a DIFFERENT exercise, specifically: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. It does not address the required lab state, whose mechanism is: Positional parameters may be absent or contain spaces, requiring validation and quoting.

Question 130

In a hands-on RHCSA practice VM, the assigned outcome was: A shell script receives `source` and `destination` as positional parameters and currently copies an empty path when arguments are missing. What specific verification would demonstrate the target state?

  1. A simulated directory creation failure stops the script before any misleading success message.
  2. Two valid paths work and calling with only one argument returns exit code 2 without copying.
  3. Known values 9 and 10 route to different expected branches.
  4. The printed host label matches `hostname -s` without treating it as an executable.

Explanation

Correct Answer

B:

Two valid paths work and calling with only one argument returns exit code 2 without copying. This check confirms the expected effect of: Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command. It distinguishes the intended result from the original failure mechanism: Positional parameters may be absent or contain spaces, requiring validation and quoting.

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: Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command.

C:

Known values 9 and 10 route to different expected branches. That verifies a separate lab task: A script's `if` statement tests a numeric threshold using string comparison and misorders the values 9 and 10. It does not validate the implementation required here: Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command.

D:

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: Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command.