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 33

Question 320

After completing this practical task on a disposable RHEL10 training node: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. Which operational safeguard helps keep the result correct and safe?

  1. Verify port-label assignment and firewall exposure separately for nonstandard listener ports.
  2. Check existing assignments before modifying SELinux port labels.
  3. Use persistent Boolean changes only when justified and test their effects after restart.
  4. Keep a verified break-glass console path before tightening authentication methods.

Explanation

Correct Answer

C:

Use persistent Boolean changes only when justified and test their effects after restart. This guards against recurrence of: `setsebool` without `-P` changes runtime policy only. Confirm the lab's final state by: The Boolean remains on after reboot and `getsebool` confirms the value.

Incorrect Answers

A:

Verify port-label assignment and firewall exposure separately for nonstandard listener ports. That control is best suited to a separate scenario: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. It is not the best safeguard for the current mechanism: `setsebool` without `-P` changes runtime policy only.

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: `setsebool` without `-P` changes runtime policy only.

D:

Keep a verified break-glass console path before tightening authentication methods. That control is best suited to a separate scenario: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. It is not the best safeguard for the current mechanism: `setsebool` without `-P` changes runtime policy only.

Question 321

Lab exercise on an offline training clone: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory.
  2. Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.
  3. Use a text editor such as `vi /tmp/lab.conf`, change the named setting, and save after checking the file's original contents.
  4. Run `find /srv/labs -type f -mtime -1 -print` and examine the returned paths.

Explanation

Correct Answer

A:

Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory. This directly addresses the lab target: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. The underlying behavior is: Using `-C` sets a stable archive root and gzip is selected using `-z`. Verification: `tar -tzf /tmp/projectA.tgz` lists the expected tree relative to `projectA/` without absolute paths.

Incorrect Answers

B:

Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record. This is an appropriate step for a DIFFERENT exercise, specifically: A team must rename a log file atomically inside one local file system before starting a new capture. It does not address the required lab state, whose mechanism is: Using `-C` sets a stable archive root and gzip is selected using `-z`.

C:

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: Using `-C` sets a stable archive root and gzip is selected using `-z`.

D:

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: Using `-C` sets a stable archive root and gzip is selected using `-z`.

Question 322

In a hands-on RHCSA practice VM, the assigned outcome was: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. What specific verification would demonstrate the target state?

  1. Only anchored service account lines with the expected prefix, letters and numeric suffix appear.
  2. `tar -tzf /tmp/projectA.tgz` lists the expected tree relative to `projectA/` without absolute paths.
  3. `readlink /usr/local/bin/lab-report` shows the intended target and executing the shortcut reaches it.
  4. The returned count matches manually inspected lines starting with 500 through 599 and excludes embedded numbers.

Explanation

Correct Answer

B:

`tar -tzf /tmp/projectA.tgz` lists the expected tree relative to `projectA/` without absolute paths. This check confirms the expected effect of: Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory. It distinguishes the intended result from the original failure mechanism: Using `-C` sets a stable archive root and gzip is selected using `-z`.

Incorrect Answers

A:

Only anchored service account lines with the expected prefix, letters and numeric suffix appear. That verifies a separate lab task: A text filter should identify accounts that start with `svc-` and end in a number but a simple substring rule admits unrelated names. It does not validate the implementation required here: Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory.

C:

`readlink /usr/local/bin/lab-report` shows the intended target and executing the shortcut reaches it. That verifies a separate lab task: A shared tools shortcut should point across directories to an existing shell script while remaining a symbolic reference. It does not validate the implementation required here: Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory.

D:

The returned count matches manually inspected lines starting with 500 through 599 and excludes embedded numbers. That verifies a separate lab task: A lab report contains 5xx server responses mixed with successful lines; a student must count only lines beginning with an HTTP 5xx code. It does not validate the implementation required here: Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory.

Question 323

A trainee is diagnosing: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. Which root cause should they recognize before changing the system?

  1. `find` age predicates filter by file metadata and differ from filename searches.
  2. Colon-separated account records require field-aware matching rather than substring searches.
  3. Using `-C` sets a stable archive root and gzip is selected using `-z`.
  4. The umask removes requested permission bits when new filesystem objects are created.

Explanation

Correct Answer

C:

Using `-C` sets a stable archive root and gzip is selected using `-z`. This explains the task's initial state: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. The supported lab action is: Run `tar -czf /tmp/projectA.tgz -C /srv/labs projectA` on the sample directory.

Incorrect Answers

A:

`find` age predicates filter by file metadata and differ from filename searches. This mechanism applies to another scenario: A large fixture tree has many similarly named files; an operator must find only files updated during the last day. The given lab state instead requires the more specific cause in the correct choice.

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.

D:

The umask removes requested permission bits when new filesystem objects are created. This mechanism applies to another scenario: A newly created shared work directory gives files unexpectedly broad default permissions. The given lab state instead requires the more specific cause in the correct choice.

Question 324

For this Linux administration lab: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. Which safety and lifecycle check best prevents the same problem returning?

  1. Use hard links only for same-filesystem files and document how unlinking each name affects retention.
  2. Record host, port and expected key fingerprint in managed SSH client configuration.
  3. Require a dry-run match review before removing files in scripted maintenance jobs.
  4. Verify archive listings before transferring, and retain a tested restore path.

Explanation

Correct Answer

D:

Verify archive listings before transferring, and retain a tested restore path. This guards against recurrence of: Using `-C` sets a stable archive root and gzip is selected using `-z`. Confirm the lab's final state by: `tar -tzf /tmp/projectA.tgz` lists the expected tree relative to `projectA/` without absolute paths.

Incorrect Answers

A:

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: Using `-C` sets a stable archive root and gzip is selected using `-z`.

B:

Record host, port and expected key fingerprint in managed SSH client configuration. That control is best suited to a separate scenario: An SSH lab service listens on a deliberately nonstandard port 2222, but a tester keeps connecting to the default port. It is not the best safeguard for the current mechanism: Using `-C` sets a stable archive root and gzip is selected using `-z`.

C:

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: Using `-C` sets a stable archive root and gzip is selected using `-z`.

Question 325

A student working on a local virtualization classroom receives this assignment: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. Which answer gives the correct practical approach?

  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. Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder.
  3. Use `sudo dnf install /tmp/signed-example.rpm` with configured repositories available for dependencies.
  4. Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.

Explanation

Correct Answer

B:

Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder. This directly addresses the lab target: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. The underlying behavior is: Flatpak application installation depends on an explicitly configured remote repository. Verification: `flatpak remotes` lists the approved remote and its actual configured URL.

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: Flatpak application installation depends on an explicitly configured remote repository.

C:

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: Flatpak application installation depends on an explicitly configured remote repository.

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 installation depends on an explicitly configured remote repository.

Question 326

You have attempted this task on a local virtualization classroom: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. Which command output or observation best confirms its success?

  1. The intended machine's `rpm -q package-name` reports installation after reconnecting to that same host.
  2. `rpm -q packagename` reports not installed and required unrelated packages remain present.
  3. `flatpak remotes` lists the approved remote and its actual configured URL.
  4. `rpm -q example` and `dnf history info` show the installed transaction and dependencies.

Explanation

Correct Answer

C:

`flatpak remotes` lists the approved remote and its actual configured URL. This check confirms the expected effect of: Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder. It distinguishes the intended result from the original failure mechanism: Flatpak application installation depends on an explicitly configured remote repository.

Incorrect Answers

A:

The intended machine's `rpm -q package-name` reports installation after reconnecting to that same host. That verifies a separate lab task: An application package is missing after a reboot because it was installed into a transient build container, not the intended host. It does not validate the implementation required here: Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder.

B:

`rpm -q packagename` reports not installed and required unrelated packages remain present. That verifies a separate lab task: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. It does not validate the implementation required here: Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder.

D:

`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: Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder.

Question 327

Troubleshoot the following RHEL 10 lab situation: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. Identify the key Linux mechanism behind the issue.

  1. Flatpak application lifecycle is managed separately from RPM transactions.
  2. DNF cannot resolve packages from an unregistered or disabled repository source.
  3. RPM package management installs files, dependencies and lifecycle metadata that ad hoc copying lacks.
  4. Flatpak application installation depends on an explicitly configured remote repository.

Explanation

Correct Answer

D:

Flatpak application installation depends on an explicitly configured remote repository. This explains the task's initial state: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. The supported lab action is: Configure the authorized remote with `flatpak remote-add --if-not-exists labapps https://example.invalid/labapps.flatpakrepo` using a real lab-provided URL instead of the illustrative placeholder.

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.

B:

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.

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.

Question 328

Following lab verification, document the preventive or persistence-oriented procedure for: An approved Flatpak runtime is already enabled in the lab, but no remote source is configured for application installation. Which practice is most suitable?

  1. Only use verified trusted remotes and validate their signature trust before deployment.
  2. Pin only justified versions and review security update exceptions.
  3. Review unused runtime cleanup separately and record approved desktop application removals.
  4. Confirm target host identity and deployment scope before every package change.

Explanation

Correct Answer

A:

Only use verified trusted remotes and validate their signature trust before deployment. This guards against recurrence of: Flatpak application installation depends on an explicitly configured remote repository. Confirm the lab's final state by: `flatpak remotes` lists the approved remote and its actual configured URL.

Incorrect Answers

B:

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: Flatpak application installation depends on an explicitly configured remote repository.

C:

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: Flatpak application installation depends on an explicitly configured remote repository.

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: Flatpak application installation depends on an explicitly configured remote repository.

Question 329

On a nonproduction Linux administration sandbox, perform the following practical task: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. Which action should be carried out after confirming the lab prerequisites?

  1. Check `[ "$#" -eq 2 ] || exit 2` and use quoted `"$1"` and `"$2"` in the copy command.
  2. Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.
  3. Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.
  4. Use `for dir in "$@"; do printf '%s\n' "$dir"; done` with arguments supplied at invocation.

Explanation

Correct Answer

C:

Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script. This directly addresses the lab target: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. The underlying behavior is: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization. Verification: The script runs under a restricted environment and resolves required binaries.

Incorrect Answers

A:

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: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

B:

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: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

D:

Use `for dir in "$@"; do printf '%s\n' "$dir"; done` with arguments supplied at invocation. This is an appropriate step for a DIFFERENT exercise, specifically: A housekeeping script must print each user-provided directory rather than always print one hard-coded value. It does not address the required lab state, whose mechanism is: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

Question 330

The lab examiner asks for evidence after this assignment: A cron-invoked script prints `command not found` for a utility present in the interactive user's shell. What is the decisive verification step?

  1. The output contains one result per unit and no unrequested service is started.
  2. A fixture with no matches reports zero while actual unreadable-file errors remain flagged.
  3. The resulting filename contains the current date digits and `tar -tzf` lists expected members.
  4. The script runs under a restricted environment and resolves required binaries.

Explanation

Correct Answer

D:

The script runs under a restricted environment and resolves required binaries. This check confirms the expected effect of: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script. It distinguishes the intended result from the original failure mechanism: Noninteractive jobs do not necessarily inherit an interactive user's PATH and shell initialization.

Incorrect Answers

A:

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 a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.

B:

A fixture with no matches reports zero while actual unreadable-file errors remain flagged. That verifies a separate lab task: A reporting script pipes `grep` through `wc` and treats a zero-match grep exit as a catastrophic error even though zero results are valid. It does not validate the implementation required here: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.

C:

The resulting filename contains the current date digits and `tar -tzf` lists expected members. That verifies a separate lab task: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. It does not validate the implementation required here: Use a controlled PATH declaration such as `PATH=/usr/sbin:/usr/bin:/sbin:/bin` or explicit command paths in the script.