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 41

Question 400

After completing this practical task on a local virtualization classroom: A protected lab directory was copied from `/home` and now has inappropriate user-home SELinux contexts under `/var/www/html`. Which operational safeguard helps keep the result correct and safe?

  1. Test positive and negative access after SSH authorization changes.
  2. Check existing assignments before modifying SELinux port labels.
  3. Reapply default file contexts after moving service data into standard labeled directories.
  4. Use persistent Boolean changes only when justified and test their effects after restart.

Explanation

Correct Answer

C:

Reapply default file contexts after moving service data into standard labeled directories. This guards against recurrence of: Copy operations may preserve source SELinux labels that are incorrect for the destination path. Confirm the lab's final state by: `ls -Z` shows suitable web content labels and Apache accesses the files under the approved mode.

Incorrect Answers

A:

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: Copy operations may preserve source SELinux labels that are incorrect for the destination path.

B:

Check existing assignments before modifying SELinux port labels. That control is best suited to a separate scenario: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. It is not the best safeguard for the current mechanism: Copy operations may preserve source SELinux labels that are incorrect for the destination path.

D:

Use persistent Boolean changes only when justified and test their effects after restart. That control is best suited to a separate scenario: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. It is not the best safeguard for the current mechanism: Copy operations may preserve source SELinux labels that are incorrect for the destination path.

Question 401

Lab exercise on a nonproduction Linux administration sandbox: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.
  2. Use `mkdir -p /tmp/restore && tar -xjf /tmp/training.tar.bz2 -C /tmp/restore` for the trusted fixture.
  3. Run `find /srv/labs -type f -mtime -1 -print` and examine the returned paths.
  4. Run `pwd`, then `cd /srv/labs/projectA` after checking it exists; use absolute paths for the target edit.

Explanation

Correct Answer

A:

Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory. This directly addresses the lab target: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. The underlying behavior is: Archive extraction can create paths and overwrite files relative to the extraction root. Verification: `find /tmp/staged-delivery -maxdepth 2` shows expected content and no unrelated system paths changed.

Incorrect Answers

B:

Use `mkdir -p /tmp/restore && tar -xjf /tmp/training.tar.bz2 -C /tmp/restore` for the trusted fixture. This is an appropriate step for a DIFFERENT exercise, specifically: A restore workflow is given a `.tar.bz2` training archive and a previous attempt used gzip extraction flags. It does not address the required lab state, whose mechanism is: Archive extraction can create paths and overwrite files relative to the extraction root.

C:

Run `find /srv/labs -type f -mtime -1 -print` and examine the returned paths. This is an appropriate step for a DIFFERENT exercise, specifically: A large fixture tree has many similarly named files; an operator must find only files updated during the last day. It does not address the required lab state, whose mechanism is: Archive extraction can create paths and overwrite files relative to the extraction root.

D:

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: Archive extraction can create paths and overwrite files relative to the extraction root.

Question 402

In a hands-on RHCSA practice VM, the assigned outcome was: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. What specific verification would demonstrate the target state?

  1. A successful SSH session connects to the expected lab host and `ss -tln` shows the listener on 2222.
  2. `find /tmp/staged-delivery -maxdepth 2` shows expected content and no unrelated system paths changed.
  3. A fixture with three matching files results in three distinct loop iterations and no literal asterisk filename.
  4. The prior entries remain and the newly written line appears at the end of the log.

Explanation

Correct Answer

B:

`find /tmp/staged-delivery -maxdepth 2` shows expected content and no unrelated system paths changed. This check confirms the expected effect of: Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory. It distinguishes the intended result from the original failure mechanism: Archive extraction can create paths and overwrite files relative to the extraction root.

Incorrect Answers

A:

A successful SSH session connects to the expected lab host and `ss -tln` shows the listener on 2222. That verifies a separate lab task: An SSH lab service listens on a deliberately nonstandard port 2222, but a tester keeps connecting to the default port. It does not validate the implementation required here: Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.

C:

A fixture with three matching files results in three distinct loop iterations and no literal asterisk filename. That verifies a separate lab task: A shell script is supposed to process every `.conf` file, but its wildcard is quoted as a single literal. It does not validate the implementation required here: Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.

D:

The prior entries remain and the newly written line appears at the end of the log. That verifies a separate lab task: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. It does not validate the implementation required here: Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.

Question 403

A trainee is diagnosing: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. Which root cause should they recognize before changing the system?

  1. Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.
  2. An unanchored pattern may count 500-series digits appearing elsewhere in a log line.
  3. Archive extraction can create paths and overwrite files relative to the extraction root.
  4. Quoting the entire wildcard prevents pathname expansion; unmatched globs can also remain literal.

Explanation

Correct Answer

C:

Archive extraction can create paths and overwrite files relative to the extraction root. This explains the task's initial state: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. The supported lab action is: Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.

Incorrect Answers

A:

Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes. This mechanism applies to another scenario: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. The given lab state instead requires the more specific cause in the correct choice.

B:

An unanchored pattern may count 500-series digits appearing elsewhere in a log line. This mechanism applies to another scenario: A lab report contains 5xx server responses mixed with successful lines; a student must count only lines beginning with an HTTP 5xx code. The given lab state instead requires the more specific cause in the correct choice.

D:

Quoting the entire wildcard prevents pathname expansion; unmatched globs can also remain literal. This mechanism applies to another scenario: A shell script is supposed to process every `.conf` file, but its wildcard is quoted as a single literal. The given lab state instead requires the more specific cause in the correct choice.

Question 404

For this Linux administration lab: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. Which safety and lifecycle check best prevents the same problem returning?

  1. Check effective identity and environment before privileged operations, then return to a normal account.
  2. Require a dry-run match review before removing files in scripted maintenance jobs.
  3. Check target collisions and keep a documented rotation/retention naming policy.
  4. Inspect archive member names and use isolated staging for untrusted or unfamiliar archives.

Explanation

Correct Answer

D:

Inspect archive member names and use isolated staging for untrusted or unfamiliar archives. This guards against recurrence of: Archive extraction can create paths and overwrite files relative to the extraction root. Confirm the lab's final state by: `find /tmp/staged-delivery -maxdepth 2` shows expected content and no unrelated system paths changed.

Incorrect Answers

A:

Check effective identity and environment before privileged operations, then return to a normal account. That control is best suited to a separate scenario: A student becomes root with `su` but finds the previous user's PATH and working directory still active during an administrative test. It is not the best safeguard for the current mechanism: Archive extraction can create paths and overwrite files relative to the extraction root.

B:

Require a dry-run match review before removing files in scripted maintenance jobs. That control is best suited to a separate scenario: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. It is not the best safeguard for the current mechanism: Archive extraction can create paths and overwrite files relative to the extraction root.

C:

Check target collisions and keep a documented rotation/retention naming policy. That control is best suited to a separate scenario: A team must rename a log file atomically inside one local file system before starting a new capture. It is not the best safeguard for the current mechanism: Archive extraction can create paths and overwrite files relative to the extraction root.

Question 405

A student working on a test RHEL10 instance receives this assignment: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. Which answer gives the correct practical approach?

  1. Repair the trusted repository signing key or certificate chain supplied by the lab rather than disabling validation.
  2. Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.
  3. Use `rpm -ql package-name` for its installed file manifest and `rpm -qc package-name` for configuration files.
  4. Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.

Explanation

Correct Answer

B:

Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes. This directly addresses the lab target: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. The underlying behavior is: Flatpak application lifecycle is managed separately from RPM transactions. Verification: `flatpak list --app` no longer includes that app, while `rpm -qa` remains unchanged.

Incorrect Answers

A:

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: Flatpak application lifecycle is managed separately from RPM transactions.

C:

Use `rpm -ql package-name` for its installed file manifest and `rpm -qc package-name` for configuration files. This is an appropriate step for a DIFFERENT exercise, specifically: A troubleshooting team wants to know exactly which files an installed RPM delivered before modifying a configuration. It does not address the required lab state, whose mechanism is: Flatpak application lifecycle is managed separately from RPM transactions.

D:

Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable. This is an appropriate step for a DIFFERENT exercise, specifically: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. It does not address the required lab state, whose mechanism is: Flatpak application lifecycle is managed separately from RPM transactions.

Question 406

You have attempted this task on a test RHEL10 instance: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. Which command output or observation best confirms its success?

  1. The configured repository refreshes while `gpgcheck=1` remains enabled and package signatures validate.
  2. `dnf repolist --enabled` includes `labrepo` and a package query returns results.
  3. `flatpak list --app` no longer includes that app, while `rpm -qa` remains unchanged.
  4. `flatpak remotes` lists the approved remote and its actual configured URL.

Explanation

Correct Answer

C:

`flatpak list --app` no longer includes that app, while `rpm -qa` remains unchanged. This check confirms the expected effect of: Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes. It distinguishes the intended result from the original failure mechanism: Flatpak application lifecycle is managed separately from RPM transactions.

Incorrect Answers

A:

The configured repository refreshes while `gpgcheck=1` remains enabled and package signatures validate. That verifies a separate lab task: A repository download fails because a private package mirror certificate is not trusted, and a student proposes turning off `gpgcheck` globally. It does not validate the implementation required here: Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.

B:

`dnf repolist --enabled` includes `labrepo` and a package query returns results. That verifies a separate lab task: A newly configured RPM repository is listed but disabled, so an application package cannot be found. It does not validate the implementation required here: Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.

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 `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.

Question 407

Troubleshoot the following RHEL 10 lab situation: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. Identify the key Linux mechanism behind the issue.

  1. Default DNF resolution may choose a newer version than an explicit compatibility requirement.
  2. Package capability providers and executable filenames do not always equal RPM package names.
  3. DNF cannot resolve packages from an unregistered or disabled repository source.
  4. Flatpak application lifecycle is managed separately from RPM transactions.

Explanation

Correct Answer

D:

Flatpak application lifecycle is managed separately from RPM transactions. This explains the task's initial state: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. The supported lab action is: Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.

Incorrect Answers

A:

Default DNF resolution may choose a newer version than an explicit compatibility requirement. This mechanism applies to another scenario: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. The given lab state instead requires the more specific cause in the correct choice.

B:

Package capability providers and executable filenames do not always equal RPM package names. This mechanism applies to another scenario: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. The given lab state instead requires the more specific cause in the correct choice.

C:

DNF cannot resolve packages from an unregistered or disabled repository source. This mechanism applies to another scenario: A training VM has a reachable approved RPM repository but `dnf` reports no package metadata because the repository is not configured. The given lab state instead requires the more specific cause in the correct choice.

Question 408

Following lab verification, document the preventive or persistence-oriented procedure for: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. Which practice is most suitable?

  1. Review unused runtime cleanup separately and record approved desktop application removals.
  2. Check repository enablement before weakening signature checks or adding unrelated mirrors.
  3. Capture the DNF transaction ID during major package changes for later review.
  4. Document both package manager and approved source when installing GUI applications.

Explanation

Correct Answer

A:

Review unused runtime cleanup separately and record approved desktop application removals. This guards against recurrence of: Flatpak application lifecycle is managed separately from RPM transactions. Confirm the lab's final state by: `flatpak list --app` no longer includes that app, while `rpm -qa` remains unchanged.

Incorrect Answers

B:

Check repository enablement before weakening signature checks or adding unrelated mirrors. That control is best suited to a separate scenario: A newly configured RPM repository is listed but disabled, so an application package cannot be found. It is not the best safeguard for the current mechanism: Flatpak application lifecycle is managed separately from RPM transactions.

C:

Capture the DNF transaction ID during major package changes for later review. That control is best suited to a separate scenario: A student must audit a recently updated package and identify whether a DNF transaction caused a regression. It is not the best safeguard for the current mechanism: Flatpak application lifecycle is managed separately from RPM transactions.

D:

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: Flatpak application lifecycle is managed separately from RPM transactions.

Question 409

On an isolated enterprise lab VM, perform the following practical task: A daily job must print only directories under a sample tree but currently loops through both files and directories. Which action should be carried out after confirming the lab prerequisites?

  1. Use `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input.
  2. Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.
  3. Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`.
  4. Use `if test -f /etc/hosts; then echo present; else exit 1; fi` in a shell script.

Explanation

Correct Answer

C:

Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`. This directly addresses the lab target: A daily job must print only directories under a sample tree but currently loops through both files and directories. The underlying behavior is: A wildcard expands all matching entries; the `-d` test discriminates directories. Verification: Only directory entries appear while ordinary files are skipped.

Incorrect Answers

A:

Use `IFS= read -r name` and `printf '%s\n' "$name"` to preserve literal input. This is an appropriate step for a DIFFERENT exercise, specifically: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. It does not address the required lab state, whose mechanism is: A wildcard expands all matching entries; the `-d` test discriminates directories.

B:

Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script. This is an appropriate step for a DIFFERENT exercise, specifically: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. It does not address the required lab state, whose mechanism is: A wildcard expands all matching entries; the `-d` test discriminates directories.

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: A wildcard expands all matching entries; the `-d` test discriminates directories.

Question 410

The lab examiner asks for evidence after this assignment: A daily job must print only directories under a sample tree but currently loops through both files and directories. What is the decisive verification step?

  1. The script runs under a restricted environment and resolves required binaries.
  2. The printed host label matches `hostname -s` without treating it as an executable.
  3. The output contains one result per unit and no unrequested service is started.
  4. Only directory entries appear while ordinary files are skipped.

Explanation

Correct Answer

D:

Only directory entries appear while ordinary files are skipped. This check confirms the expected effect of: Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`. It distinguishes the intended result from the original failure mechanism: A wildcard expands all matching entries; the `-d` test discriminates directories.

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 `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`.

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 `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`.

C:

The output contains one result per unit and no unrequested service is started. That verifies a separate lab task: A service check is intended to poll five named systemd units, but the script uses only the first literal unit. It does not validate the implementation required here: Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`.