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 17

Question 160

After completing this practical task on a local virtualization classroom: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. Which operational safeguard helps keep the result correct and safe?

  1. Use persistent Boolean changes only when justified and test their effects after restart.
  2. Provision and rotate private keys under managed mode and ownership controls.
  3. Use policy-backed fcontext mappings for nonstandard service directories.
  4. Check runtime and configured SELinux modes after policy changes.

Explanation

Correct Answer

C:

Use policy-backed fcontext mappings for nonstandard service directories. This guards against recurrence of: `chcon` changes an inode label temporarily without updating the default file context database. Confirm the lab's final state by: `matchpathcon` and `ls -Z` agree after relabeling and a reboot.

Incorrect Answers

A:

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: `chcon` changes an inode label temporarily without updating the default file context database.

B:

Provision and rotate private keys under managed mode and ownership controls. That control is best suited to a separate scenario: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. It is not the best safeguard for the current mechanism: `chcon` changes an inode label temporarily without updating the default file context database.

D:

Check runtime and configured SELinux modes after policy changes. That control is best suited to a separate scenario: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. It is not the best safeguard for the current mechanism: `chcon` changes an inode label temporarily without updating the default file context database.

Question 161

Lab exercise on a nonproduction Linux administration sandbox: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields.
  2. Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator.
  3. Use unquoted glob expansion only for the intended directory, e.g. `for f in /tmp/lab-conf/*.conf; do ...; done`, with a no-match guard.
  4. Use `tail -n 30 -f /tmp/labapp.log` to follow appended fixture events in a test terminal.

Explanation

Correct Answer

A:

Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields. This directly addresses the lab target: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. The underlying behavior is: Colon-separated account records require field-aware matching rather than substring searches. Verification: The numeric result matches a manual sample from `/etc/passwd` and excludes strings in other fields.

Incorrect Answers

B:

Use `printf '%s\n' 'cycle complete' >> /tmp/ops-history.log` rather than the overwrite operator. This is an appropriate step for a DIFFERENT exercise, specifically: An hourly shell job unintentionally overwrites yesterday's operational notes each time it records a new line. It does not address the required lab state, whose mechanism is: Colon-separated account records require field-aware matching rather than substring searches.

C:

Use unquoted glob expansion only for the intended directory, e.g. `for f in /tmp/lab-conf/*.conf; do ...; done`, with a no-match guard. This is an appropriate step for a DIFFERENT exercise, specifically: A shell script is supposed to process every `.conf` file, but its wildcard is quoted as a single literal. It does not address the required lab state, whose mechanism is: Colon-separated account records require field-aware matching rather than substring searches.

D:

Use `tail -n 30 -f /tmp/labapp.log` to follow appended fixture events in a test terminal. This is an appropriate step for a DIFFERENT exercise, specifically: An operator follows a live application log but accidentally reads only the first ten lines during troubleshooting. It does not address the required lab state, whose mechanism is: Colon-separated account records require field-aware matching rather than substring searches.

Question 162

In a hands-on RHCSA practice VM, the assigned outcome was: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. What specific verification would demonstrate the target state?

  1. `ssh -o BatchMode=yes student@hostB true` succeeds using an authorized key on the isolated lab.
  2. The numeric result matches a manual sample from `/etc/passwd` and excludes strings in other fields.
  3. The displayed files belong to the installed package release and provide its appropriate local examples.
  4. `test ! -e /tmp/app.log && test -f /tmp/app.log.old` confirms the intended name transition.

Explanation

Correct Answer

B:

The numeric result matches a manual sample from `/etc/passwd` and excludes strings in other fields. This check confirms the expected effect of: Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields. It distinguishes the intended result from the original failure mechanism: Colon-separated account records require field-aware matching rather than substring searches.

Incorrect Answers

A:

`ssh -o BatchMode=yes student@hostB true` succeeds using an authorized key on the isolated lab. That verifies a separate lab task: Two lab hosts need noninteractive operator access and password prompts interrupt file-copy automation. It does not validate the implementation required here: Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields.

C:

The displayed files belong to the installed package release and provide its appropriate local examples. That verifies a separate lab task: A junior administrator wants usage examples for a locally installed system package but searches an unrelated online version. It does not validate the implementation required here: Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields.

D:

`test ! -e /tmp/app.log && test -f /tmp/app.log.old` confirms the intended name transition. That verifies a separate lab task: A team must rename a log file atomically inside one local file system before starting a new capture. It does not validate the implementation required here: Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields.

Question 163

A trainee is diagnosing: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. Which root cause should they recognize before changing the system?

  1. Extended regular expressions need explicit anchors and quantifiers for exact whole-line matching.
  2. A symbolic link stores a target path; unlike a hard link it may cross filesystem boundaries.
  3. Colon-separated account records require field-aware matching rather than substring searches.
  4. Bzip2-compressed tar archives use the `-j` decompression option, not the gzip `-z` option.

Explanation

Correct Answer

C:

Colon-separated account records require field-aware matching rather than substring searches. This explains the task's initial state: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. The supported lab action is: Run `awk -F: '$7=="/bin/bash" {n++} END{print n+0}' /etc/passwd` to count exact shell fields.

Incorrect Answers

A:

Extended regular expressions need explicit anchors and quantifiers for exact whole-line matching. This mechanism applies to another scenario: A text filter should identify accounts that start with `svc-` and end in a number but a simple substring rule admits unrelated names. The given lab state instead requires the more specific cause in the correct choice.

B:

A symbolic link stores a target path; unlike a hard link it may cross filesystem boundaries. This mechanism applies to another scenario: A shared tools shortcut should point across directories to an existing shell script while remaining a symbolic reference. The given lab state instead requires the more specific cause in the correct choice.

D:

Bzip2-compressed tar archives use the `-j` decompression option, not the gzip `-z` option. This mechanism applies to another scenario: A restore workflow is given a `.tar.bz2` training archive and a previous attempt used gzip extraction flags. The given lab state instead requires the more specific cause in the correct choice.

Question 164

For this Linux administration lab: A training data file lists one account per line, and the goal is counting accounts whose shells are `/bin/bash`. Which safety and lifecycle check best prevents the same problem returning?

  1. Start scripted changes with an explicit `cd` guarded by failure checking and record the resolved target path.
  2. Make reviewed minimal edits and keep a backup or version-controlled copy of lab configuration.
  3. Verify archive listings before transferring, and retain a tested restore path.
  4. Verify record delimiters and test scripts against a representative sample before aggregating.

Explanation

Correct Answer

D:

Verify record delimiters and test scripts against a representative sample before aggregating. This guards against recurrence of: Colon-separated account records require field-aware matching rather than substring searches. Confirm the lab's final state by: The numeric result matches a manual sample from `/etc/passwd` and excludes strings in other fields.

Incorrect Answers

A:

Start scripted changes with an explicit `cd` guarded by failure checking and record the resolved target path. That control is best suited to a separate scenario: On a disposable RHEL 10 training host, an operator enters a nested work directory but later edits the wrong file because the current path was assumed. It is not the best safeguard for the current mechanism: Colon-separated account records require field-aware matching rather than substring searches.

B:

Make reviewed minimal edits and keep a backup or version-controlled copy of lab configuration. That control is best suited to a separate scenario: An operator needs to change a configuration line without deleting other settings in a small text file. It is not the best safeguard for the current mechanism: Colon-separated account records require field-aware matching rather than substring searches.

C:

Verify archive listings before transferring, and retain a tested restore path. That control is best suited to a separate scenario: A file collection must be archived with gzip while preserving its directory tree for off-host lab backup. It is not the best safeguard for the current mechanism: Colon-separated account records require field-aware matching rather than substring searches.

Question 165

A student working on a test RHEL10 instance receives this assignment: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. 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. Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.
  3. Use `flatpak install labapps org.example.Editor` after configuring the approved Flatpak remote.
  4. Use `rpm -ql package-name` for its installed file manifest and `rpm -qc package-name` for configuration files.

Explanation

Correct Answer

B:

Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable. This directly addresses the lab target: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. The underlying behavior is: Package capability providers and executable filenames do not always equal RPM package names. Verification: The owning RPM is listed and after installation `rpm -qf /usr/bin/executable-name` resolves it.

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: Package capability providers and executable filenames do not always equal RPM package names.

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: Package capability providers and executable filenames do not always equal RPM package names.

D:

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: Package capability providers and executable filenames do not always equal RPM package names.

Question 166

You have attempted this task on a test RHEL10 instance: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. Which command output or observation best confirms its success?

  1. The expected config file is listed as package-managed and its ownership is traceable.
  2. The target package and action appear under the expected transaction ID without guessing which manual file changed.
  3. The owning RPM is listed and after installation `rpm -qf /usr/bin/executable-name` resolves it.
  4. `rpm -q example` and `dnf history info` show the installed transaction and dependencies.

Explanation

Correct Answer

C:

The owning RPM is listed and after installation `rpm -qf /usr/bin/executable-name` resolves it. This check confirms the expected effect of: Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable. It distinguishes the intended result from the original failure mechanism: Package capability providers and executable filenames do not always equal RPM package names.

Incorrect Answers

A:

The expected config file is listed as package-managed and its ownership is traceable. That verifies a separate lab task: A troubleshooting team wants to know exactly which files an installed RPM delivered before modifying a configuration. It does not validate the implementation required here: Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.

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: Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.

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: Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.

Question 167

Troubleshoot the following RHEL 10 lab situation: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. Identify the key Linux mechanism behind the issue.

  1. RPM package management installs files, dependencies and lifecycle metadata that ad hoc copying lacks.
  2. DNF removal resolves dependencies and may remove related packages, which requires plan review.
  3. Package databases record installed paths and specially flagged config files.
  4. Package capability providers and executable filenames do not always equal RPM package names.

Explanation

Correct Answer

D:

Package capability providers and executable filenames do not always equal RPM package names. This explains the task's initial state: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. The supported lab action is: Use `dnf provides '*/executable-name'` to identify which approved RPM actually supplies the executable.

Incorrect Answers

A:

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.

B:

DNF removal resolves dependencies and may remove related packages, which requires plan review. This mechanism applies to another scenario: A retired tool remains installed after a change freeze and needs removal without deleting unrelated data directories. The given lab state instead requires the more specific cause in the correct choice.

C:

Package databases record installed paths and specially flagged config files. This mechanism applies to another scenario: A troubleshooting team wants to know exactly which files an installed RPM delivered before modifying a configuration. The given lab state instead requires the more specific cause in the correct choice.

Question 168

Following lab verification, document the preventive or persistence-oriented procedure for: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. Which practice is most suitable?

  1. Validate package ownership and source repository before installations.
  2. Capture the DNF transaction ID during major package changes for later review.
  3. Manage repositories as reviewed configuration and verify package-signature policy before installs.
  4. Check repository enablement before weakening signature checks or adding unrelated mirrors.

Explanation

Correct Answer

A:

Validate package ownership and source repository before installations. This guards against recurrence of: Package capability providers and executable filenames do not always equal RPM package names. Confirm the lab's final state by: The owning RPM is listed and after installation `rpm -qf /usr/bin/executable-name` resolves it.

Incorrect Answers

B:

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: Package capability providers and executable filenames do not always equal RPM package names.

C:

Manage repositories as reviewed configuration and verify package-signature policy before installs. That control is best suited to a separate scenario: A training VM has a reachable approved RPM repository but `dnf` reports no package metadata because the repository is not configured. It is not the best safeguard for the current mechanism: Package capability providers and executable filenames do not always equal RPM package names.

D:

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: Package capability providers and executable filenames do not always equal RPM package names.

Question 169

On an isolated enterprise lab VM, perform the following practical task: A shell script writes raw command output but needs its first line to include the current hostname from the target host. Which action should be carried out after confirming the lab prerequisites?

  1. Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`.
  2. Use `for dir in "$@"; do printf '%s\n' "$dir"; done` with arguments supplied at invocation.
  3. Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.
  4. Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`.

Explanation

Correct Answer

C:

Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script. This directly addresses the lab target: A shell script writes raw command output but needs its first line to include the current hostname from the target host. The underlying behavior is: Command substitution captures a command's standard output as data. Verification: The printed host label matches `hostname -s` without treating it as an executable.

Incorrect Answers

A:

Use `for path in /tmp/lab-tree/*; do [ -d "$path" ] || continue; printf '%s\n' "$path"; done`. This is an appropriate step for a DIFFERENT exercise, specifically: A daily job must print only directories under a sample tree but currently loops through both files and directories. It does not address the required lab state, whose mechanism is: Command substitution captures a command's standard output as data.

B:

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: Command substitution captures a command's standard output as data.

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: Command substitution captures a command's standard output as data.

Question 170

The lab examiner asks for evidence after this assignment: A shell script writes raw command output but needs its first line to include the current hostname from the target host. What is the decisive verification step?

  1. The known present and missing fixture processes produce different status messages.
  2. The output contains one result per unit and no unrequested service is started.
  3. In a fixture where the first command exits 1, the second command does not run.
  4. The printed host label matches `hostname -s` without treating it as an executable.

Explanation

Correct Answer

D:

The printed host label matches `hostname -s` without treating it as an executable. This check confirms the expected effect of: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script. It distinguishes the intended result from the original failure mechanism: Command substitution captures a command's standard output as data.

Incorrect Answers

A:

The known present and missing fixture processes produce different status messages. That verifies a separate lab task: A maintenance script must report whether a given process name exists without exiting with a misleading success status. It does not validate the implementation required here: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

B:

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 `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

C:

In a fixture where the first command exits 1, the second command does not run. That verifies a separate lab task: A script invokes two commands on one line with a semicolon and prints success even if the first fails. It does not validate the implementation required here: Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.