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 53

Question 520

Following lab verification, document the preventive or persistence-oriented procedure for: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. Which practice is most suitable?

  1. Keep a verified break-glass console path before tightening authentication methods.
  2. Test positive and negative access after SSH authorization changes.
  3. Use policy-backed fcontext mappings for nonstandard service directories.
  4. Verify persistence and remove temporary diagnostic firewall permits.

Explanation

Correct Answer

A:

Keep a verified break-glass console path before tightening authentication methods. This guards against recurrence of: SSH authentication methods are enforced by sshd configuration and authorized key material. Confirm the lab's final state by: Key-based login succeeds while a controlled password-only attempt fails without locking out the authorized admin.

Incorrect Answers

B:

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: SSH authentication methods are enforced by sshd configuration and authorized key material.

C:

Use policy-backed fcontext mappings for nonstandard service directories. That control is best suited to a separate scenario: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. It is not the best safeguard for the current mechanism: SSH authentication methods are enforced by sshd configuration and authorized key material.

D:

Verify persistence and remove temporary diagnostic firewall permits. That control is best suited to a separate scenario: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. It is not the best safeguard for the current mechanism: SSH authentication methods are enforced by sshd configuration and authorized key material.

Question 521

On a nonproduction Linux administration sandbox, perform the following practical task: A team must rename a log file atomically inside one local file system before starting a new capture. Which action should be carried out after confirming the lab prerequisites?

  1. Use `mkdir -p /tmp/restore && tar -xjf /tmp/training.tar.bz2 -C /tmp/restore` for the trusted fixture.
  2. Use a text editor such as `vi /tmp/lab.conf`, change the named setting, and save after checking the file's original contents.
  3. Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.
  4. Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`.

Explanation

Correct Answer

C:

Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record. This directly addresses the lab target: A team must rename a log file atomically inside one local file system before starting a new capture. The underlying behavior is: Renaming a local path with `mv` is different from duplicating it with `cp`. Verification: `test ! -e /tmp/app.log && test -f /tmp/app.log.old` confirms the intended name transition.

Incorrect Answers

A:

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: Renaming a local path with `mv` is different from duplicating it with `cp`.

B:

Use a text editor such as `vi /tmp/lab.conf`, change the named setting, and save after checking the file's original contents. This is an appropriate step for a DIFFERENT exercise, specifically: An operator needs to change a configuration line without deleting other settings in a small text file. It does not address the required lab state, whose mechanism is: Renaming a local path with `mv` is different from duplicating it with `cp`.

D:

Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`. This is an appropriate step for a DIFFERENT exercise, specifically: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. It does not address the required lab state, whose mechanism is: Renaming a local path with `mv` is different from duplicating it with `cp`.

Question 522

The lab examiner asks for evidence after this assignment: A team must rename a log file atomically inside one local file system before starting a new capture. What is the decisive verification step?

  1. `pwd` reports `/srv/labs/projectA` and `realpath ./notes.txt` resolves inside that directory.
  2. A fixture with three matching files results in three distinct loop iterations and no literal asterisk filename.
  3. `stat -c '%a %U'` shows `600` and the intended user, and `test -r` succeeds for that owner.
  4. `test ! -e /tmp/app.log && test -f /tmp/app.log.old` confirms the intended name transition.

Explanation

Correct Answer

D:

`test ! -e /tmp/app.log && test -f /tmp/app.log.old` confirms the intended name transition. This check confirms the expected effect of: Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record. It distinguishes the intended result from the original failure mechanism: Renaming a local path with `mv` is different from duplicating it with `cp`.

Incorrect Answers

A:

`pwd` reports `/srv/labs/projectA` and `realpath ./notes.txt` resolves inside that directory. That verifies a separate lab task: 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 validate the implementation required here: Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.

B:

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: Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.

C:

`stat -c '%a %U'` shows `600` and the intended user, and `test -r` succeeds for that owner. That verifies a separate lab task: A private lab key file is incorrectly world-readable and must be accessible only to its owner. It does not validate the implementation required here: Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.

Question 523

A training host has this situation: A team must rename a log file atomically inside one local file system before starting a new capture. Which system behavior best explains the original failure or risk?

  1. Renaming a local path with `mv` is different from duplicating it with `cp`.
  2. Replacing the whole file for a one-line change risks losing required settings.
  3. An unanchored pattern may count 500-series digits appearing elsewhere in a log line.
  4. Using `-C` sets a stable archive root and gzip is selected using `-z`.

Explanation

Correct Answer

A:

Renaming a local path with `mv` is different from duplicating it with `cp`. This explains the task's initial state: A team must rename a log file atomically inside one local file system before starting a new capture. The supported lab action is: Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.

Incorrect Answers

B:

Replacing the whole file for a one-line change risks losing required settings. This mechanism applies to another scenario: An operator needs to change a configuration line without deleting other settings in a small text file. The given lab state instead requires the more specific cause in the correct choice.

C:

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:

Using `-C` sets a stable archive root and gzip is selected using `-z`. This mechanism applies to another scenario: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. The given lab state instead requires the more specific cause in the correct choice.

Question 524

A student has implemented the following configuration: A team must rename a log file atomically inside one local file system before starting a new capture. What repeatable control best reduces regressions or unsafe changes?

  1. Inspect archive member names and use isolated staging for untrusted or unfamiliar archives.
  2. Check target collisions and keep a documented rotation/retention naming policy.
  3. Select metadata-preserving copy flags only when ownership and permissions are intentionally retained.
  4. Use hard links only for same-filesystem files and document how unlinking each name affects retention.

Explanation

Correct Answer

B:

Check target collisions and keep a documented rotation/retention naming policy. This guards against recurrence of: Renaming a local path with `mv` is different from duplicating it with `cp`. Confirm the lab's final state by: `test ! -e /tmp/app.log && test -f /tmp/app.log.old` confirms the intended name transition.

Incorrect Answers

A:

Inspect archive member names and use isolated staging for untrusted or unfamiliar archives. That control is best suited to a separate scenario: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. It is not the best safeguard for the current mechanism: Renaming a local path with `mv` is different from duplicating it with `cp`.

C:

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: Renaming a local path with `mv` is different from duplicating it with `cp`.

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: Renaming a local path with `mv` is different from duplicating it with `cp`.

Question 525

You are responsible for a test RHEL10 instance. The required hands-on outcome is: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. Select the most appropriate implementation step.

  1. Use `dnf config-manager --set-enabled labrepo` only if the appropriate DNF plugin is present, or set `enabled=1` in the vetted `.repo` entry.
  2. Use `sudo dnf install /tmp/signed-example.rpm` with configured repositories available for dependencies.
  3. Use `flatpak install labapps org.example.Editor` after configuring the approved Flatpak remote.
  4. Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM.

Explanation

Correct Answer

D:

Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM. This directly addresses the lab target: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. The underlying behavior is: Installing inside an ephemeral environment does not alter the host RPM database. Verification: The intended machine's `rpm -q package-name` reports installation after reconnecting to that same host.

Incorrect Answers

A:

Use `dnf config-manager --set-enabled labrepo` only if the appropriate DNF plugin is present, or set `enabled=1` in the vetted `.repo` entry. This is an appropriate step for a DIFFERENT exercise, specifically: A newly configured RPM repository is listed but disabled, so an application package cannot be found. It does not address the required lab state, whose mechanism is: Installing inside an ephemeral environment does not alter the host RPM database.

B:

Use `sudo dnf install /tmp/signed-example.rpm` with configured repositories available for dependencies. This is an appropriate step for a DIFFERENT exercise, specifically: A lab host cannot install a local signed RPM because an engineer assumes a bare filename will automatically resolve dependency packages. It does not address the required lab state, whose mechanism is: Installing inside an ephemeral environment does not alter the host RPM database.

C:

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: Installing inside an ephemeral environment does not alter the host RPM database.

Question 526

After a lab configuration change, verify: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. Which result most directly proves the desired system state?

  1. The intended machine's `rpm -q package-name` reports installation after reconnecting to that same host.
  2. `flatpak list --app` includes `org.example.Editor` and its intended origin.
  3. `rpm -q example` and `dnf history info` show the installed transaction and dependencies.
  4. The target package and action appear under the expected transaction ID without guessing which manual file changed.

Explanation

Correct Answer

A:

The intended machine's `rpm -q package-name` reports installation after reconnecting to that same host. This check confirms the expected effect of: Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM. It distinguishes the intended result from the original failure mechanism: Installing inside an ephemeral environment does not alter the host RPM database.

Incorrect Answers

B:

`flatpak list --app` includes `org.example.Editor` and its intended origin. That verifies a separate lab task: A desktop lab task requires installing a named Flatpak application, but the administrator runs `dnf install` for its Flatpak ID. It does not validate the implementation required here: Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM.

C:

`rpm -q example` and `dnf history info` show the installed transaction and dependencies. That verifies a separate lab task: A lab host cannot install a local signed RPM because an engineer assumes a bare filename will automatically resolve dependency packages. It does not validate the implementation required here: Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM.

D:

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: Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM.

Question 527

In an EX200-style practice lab, this condition exists: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. Which explanation correctly identifies the underlying issue?

  1. Flatpak application lifecycle is managed separately from RPM transactions.
  2. Installing inside an ephemeral environment does not alter the host RPM database.
  3. RPM package management installs files, dependencies and lifecycle metadata that ad hoc copying lacks.
  4. Package capability providers and executable filenames do not always equal RPM package names.

Explanation

Correct Answer

B:

Installing inside an ephemeral environment does not alter the host RPM database. This explains the task's initial state: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. The supported lab action is: Use host `cat /etc/os-release`, `hostnamectl`, and `rpm -q` before installing the package on the correct persistent RHEL VM.

Incorrect Answers

A:

Flatpak application lifecycle is managed separately from RPM transactions. This mechanism applies to another scenario: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. 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:

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.

Question 528

After completing this practical task on a test RHEL10 instance: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. Which operational safeguard helps keep the result correct and safe?

  1. Pin only justified versions and review security update exceptions.
  2. Review transaction proposals and preserve business data before package retirement.
  3. Confirm target host identity and deployment scope before every package change.
  4. Check package-managed status before overwriting or deleting a file during repair.

Explanation

Correct Answer

C:

Confirm target host identity and deployment scope before every package change. This guards against recurrence of: Installing inside an ephemeral environment does not alter the host RPM database. Confirm the lab's final state by: The intended machine's `rpm -q package-name` reports installation after reconnecting to that same host.

Incorrect Answers

A:

Pin only justified versions and review security update exceptions. That control is best suited to a separate scenario: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. It is not the best safeguard for the current mechanism: Installing inside an ephemeral environment does not alter the host RPM database.

B:

Review transaction proposals and preserve business data before package retirement. That control is best suited to a separate scenario: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. It is not the best safeguard for the current mechanism: Installing inside an ephemeral environment does not alter the host RPM database.

D:

Check package-managed status before overwriting or deleting a file during repair. That control is best suited to a separate scenario: A troubleshooting team wants to know exactly which files an installed RPM delivered before modifying a configuration. It is not the best safeguard for the current mechanism: Installing inside an ephemeral environment does not alter the host RPM database.

Question 529

Lab exercise on an isolated enterprise lab VM: A maintenance script must report whether a given process name exists without exiting with a misleading success status. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.
  2. Use `if test -f /etc/hosts; then echo present; else exit 1; fi` in a shell script.
  3. Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.
  4. Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command.

Explanation

Correct Answer

A:

Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation. This directly addresses the lab target: A maintenance script must report whether a given process name exists without exiting with a misleading success status. The underlying behavior is: An exact process-name match requires `-x` instead of a broad substring search. Verification: The known present and missing fixture processes produce different status messages.

Incorrect Answers

B:

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: An exact process-name match requires `-x` instead of a broad substring search.

C:

Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script. This is an appropriate step for a DIFFERENT exercise, specifically: A shell script writes raw command output but needs its first line to include the current hostname from the target host. It does not address the required lab state, whose mechanism is: An exact process-name match requires `-x` instead of a broad substring search.

D:

Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command. This is an appropriate step for a DIFFERENT exercise, specifically: A shell script receives `source` and `destination` as positional parameters and currently copies an empty path when arguments are missing. It does not address the required lab state, whose mechanism is: An exact process-name match requires `-x` instead of a broad substring search.

Question 530

In a hands-on RHCSA practice VM, the assigned outcome was: A maintenance script must report whether a given process name exists without exiting with a misleading success status. What specific verification would demonstrate the target state?

  1. A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs.
  2. The known present and missing fixture processes produce different status messages.
  3. The script runs under a restricted environment and resolves required binaries.
  4. Arguments containing spaces are printed as single intended entries and the loop count matches input count.

Explanation

Correct Answer

B:

The known present and missing fixture processes produce different status messages. This check confirms the expected effect of: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation. It distinguishes the intended result from the original failure mechanism: An exact process-name match requires `-x` instead of a broad substring search.

Incorrect Answers

A:

A fixture containing backslashes is printed unchanged and no unexpected interpolation occurs. That verifies a separate lab task: A script asks users for a name but accidentally treats backslash sequences in the input as control codes. It does not validate the implementation required here: Use `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.

C:

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 `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.

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 `if pgrep -x "$1" >/dev/null; then echo running; else echo absent; fi` after argument validation.