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 49

Question 480

After completing this practical task on a test RHEL10 instance: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. Which operational safeguard helps keep the result correct and safe?

  1. Check active zone, SELinux port permission and service listener together.
  2. Reapply default file contexts after moving service data into standard labeled directories.
  3. Provision and rotate private keys under managed mode and ownership controls.
  4. Check runtime and configured SELinux modes after policy changes.

Explanation

Correct Answer

C:

Provision and rotate private keys under managed mode and ownership controls. This guards against recurrence of: SSH private credentials require protected ownership and permissions distinct from public authorized keys. Confirm the lab's final state by: `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.

Incorrect Answers

A:

Check active zone, SELinux port permission and service listener together. That control is best suited to a separate scenario: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. It is not the best safeguard for the current mechanism: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

B:

Reapply default file contexts after moving service data into standard labeled directories. That control is best suited to a separate scenario: A protected lab directory was copied from `/home` and now has inappropriate user-home SELinux contexts under `/var/www/html`. It is not the best safeguard for the current mechanism: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

Question 481

Lab exercise on an isolated enterprise lab VM: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required.
  2. Use `mv /tmp/app.log /tmp/app.log.old` after checking the destination will not overwrite an existing record.
  3. Run `find /srv/labs -type f -mtime -1 -print` and examine the returned paths.
  4. Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.

Explanation

Correct Answer

A:

Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required. This directly addresses the lab target: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. The underlying behavior is: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes. Verification: `stat -c '%a %y'` on source and destination confirms equivalent permissions and modification time.

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: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

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: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

D:

Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory. This is an appropriate step for a DIFFERENT exercise, specifically: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. It does not address the required lab state, whose mechanism is: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

Question 482

In a hands-on RHCSA practice VM, the assigned outcome was: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. What specific verification would demonstrate the target state?

  1. The displayed files belong to the installed package release and provide its appropriate local examples.
  2. `stat -c '%a %y'` on source and destination confirms equivalent permissions and modification time.
  3. A successful SSH session connects to the expected lab host and `ss -tln` shows the listener on 2222.
  4. A newly appended training event appears immediately without rerunning the command.

Explanation

Correct Answer

B:

`stat -c '%a %y'` on source and destination confirms equivalent permissions and modification time. This check confirms the expected effect of: Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required. It distinguishes the intended result from the original failure mechanism: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

Incorrect Answers

A:

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: Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required.

C:

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: Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required.

D:

A newly appended training event appears immediately without rerunning the command. That verifies a separate lab task: An operator follows a live application log but accidentally reads only the first ten lines during troubleshooting. It does not validate the implementation required here: Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required.

Question 483

A trainee is diagnosing: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. Which root cause should they recognize before changing the system?

  1. Public-key authentication requires an authorized matching key in the correct user account.
  2. SSH host-key validation helps prevent connecting to an impersonated endpoint.
  3. Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.
  4. Using `-C` sets a stable archive root and gzip is selected using `-z`.

Explanation

Correct Answer

C:

Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes. This explains the task's initial state: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. The supported lab action is: Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required.

Incorrect Answers

A:

Public-key authentication requires an authorized matching key in the correct user account. This mechanism applies to another scenario: Two lab hosts need noninteractive operator access and password prompts interrupt file-copy automation. The given lab state instead requires the more specific cause in the correct choice.

B:

SSH host-key validation helps prevent connecting to an impersonated endpoint. This mechanism applies to another scenario: A first SSH connection warns that the server identity is unknown, and a student proposes disabling host key checks globally. 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 484

For this Linux administration lab: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. Which safety and lifecycle check best prevents the same problem returning?

  1. Maintain positive and negative sample cases for account naming validation.
  2. Require a dry-run match review before removing files in scripted maintenance jobs.
  3. Manage known host fingerprints and investigate unexpected key changes instead of setting StrictHostKeyChecking=no.
  4. Select metadata-preserving copy flags only when ownership and permissions are intentionally retained.

Explanation

Correct Answer

D:

Select metadata-preserving copy flags only when ownership and permissions are intentionally retained. This guards against recurrence of: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes. Confirm the lab's final state by: `stat -c '%a %y'` on source and destination confirms equivalent permissions and modification time.

Incorrect Answers

A:

Maintain positive and negative sample cases for account naming validation. That control is best suited to a separate scenario: A text filter should identify accounts that start with `svc-` and end in a number but a simple substring rule admits unrelated names. It is not the best safeguard for the current mechanism: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

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: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

C:

Manage known host fingerprints and investigate unexpected key changes instead of setting StrictHostKeyChecking=no. That control is best suited to a separate scenario: A first SSH connection warns that the server identity is unknown, and a student proposes disabling host key checks globally. It is not the best safeguard for the current mechanism: Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.

Question 485

A student working on a disposable RHEL10 training node receives this assignment: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. Which answer gives the correct practical approach?

  1. Inspect `dnf history`, then `dnf history info <ID>` for the recorded transaction.
  2. Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks.
  3. Use `sudo dnf install /tmp/signed-example.rpm` with configured repositories available for dependencies.
  4. Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes.

Explanation

Correct Answer

B:

Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks. This directly addresses the lab target: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. The underlying behavior is: Default DNF resolution may choose a newer version than an explicit compatibility requirement. Verification: `rpm -q package-name` reports the approved release and relevant dependencies remain consistent.

Incorrect Answers

A:

Inspect `dnf history`, then `dnf history info <ID>` for the recorded transaction. This is an appropriate step for a DIFFERENT exercise, specifically: A student must audit a recently updated package and identify whether a DNF transaction caused a regression. It does not address the required lab state, whose mechanism is: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

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: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

D:

Run `flatpak uninstall org.example.Editor` after reviewing the installed app and any prompted runtime changes. This is an appropriate step for a DIFFERENT exercise, specifically: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. It does not address the required lab state, whose mechanism is: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

Question 486

You have attempted this task on a disposable RHEL10 training node: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. 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. `flatpak list --app` no longer includes that app, while `rpm -qa` remains unchanged.
  3. `rpm -q package-name` reports the approved release and relevant dependencies remain consistent.
  4. The owning RPM is listed and after installation `rpm -qf /usr/bin/executable-name` resolves it.

Explanation

Correct Answer

C:

`rpm -q package-name` reports the approved release and relevant dependencies remain consistent. This check confirms the expected effect of: Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks. It distinguishes the intended result from the original failure mechanism: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

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: Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks.

B:

`flatpak list --app` no longer includes that app, while `rpm -qa` remains unchanged. That verifies a separate lab task: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. It does not validate the implementation required here: Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks.

D:

The owning RPM is listed and after installation `rpm -qf /usr/bin/executable-name` resolves it. That verifies a separate lab task: A software deployment reports success but the executable is absent; the chosen package name was only a virtual capability. It does not validate the implementation required here: Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks.

Question 487

Troubleshoot the following RHEL 10 lab situation: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. Identify the key Linux mechanism behind the issue.

  1. DNF cannot resolve packages from an unregistered or disabled repository source.
  2. Flatpak application lifecycle is managed separately from RPM transactions.
  3. Unsigned or untrusted repository sources should not be implicitly accepted just to satisfy an install.
  4. Default DNF resolution may choose a newer version than an explicit compatibility requirement.

Explanation

Correct Answer

D:

Default DNF resolution may choose a newer version than an explicit compatibility requirement. This explains the task's initial state: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. The supported lab action is: Use `dnf list --showduplicates package-name`, then install a specifically available `name-version-release` after dependency checks.

Incorrect Answers

A:

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.

B:

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:

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

Question 488

Following lab verification, document the preventive or persistence-oriented procedure for: A lab requirement says install one exact software release but `dnf install` picks the newest enabled version. Which practice is most suitable?

  1. Pin only justified versions and review security update exceptions.
  2. Review unused runtime cleanup separately and record approved desktop application removals.
  3. Capture the DNF transaction ID during major package changes for later review.
  4. Use the package manager and signature validation for offline/locally provided RPM artifacts.

Explanation

Correct Answer

A:

Pin only justified versions and review security update exceptions. This guards against recurrence of: Default DNF resolution may choose a newer version than an explicit compatibility requirement. Confirm the lab's final state by: `rpm -q package-name` reports the approved release and relevant dependencies remain consistent.

Incorrect Answers

B:

Review unused runtime cleanup separately and record approved desktop application removals. That control is best suited to a separate scenario: An operator needs to remove an obsolete Flatpak application without removing unrelated RPM software. It is not the best safeguard for the current mechanism: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

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: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

D:

Use the package manager and signature validation for offline/locally provided RPM artifacts. That control is best suited to a separate scenario: A lab host cannot install a local signed RPM because an engineer assumes a bare filename will automatically resolve dependency packages. It is not the best safeguard for the current mechanism: Default DNF resolution may choose a newer version than an explicit compatibility requirement.

Question 489

On an offline training clone, perform the following practical task: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. Which action should be carried out after confirming the lab prerequisites?

  1. Use `for unit in sshd crond chronyd firewalld NetworkManager; do systemctl is-active "$unit"; done`.
  2. Use `if [ "$count" -ge 10 ]; then ...; fi` after validating `count` is an integer.
  3. Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`.
  4. Use `host=$(hostname -s)` and `printf 'host=%s\n' "$host"` in the exercise script.

Explanation

Correct Answer

C:

Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`. This directly addresses the lab target: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. The underlying behavior is: Single quotes suppress shell substitutions; double-quoted variable expansion preserves values. Verification: The resulting filename contains the current date digits and `tar -tzf` lists expected members.

Incorrect Answers

A:

Use `for unit in sshd crond chronyd firewalld NetworkManager; do systemctl is-active "$unit"; done`. This is an appropriate step for a DIFFERENT exercise, specifically: A service check is intended to poll five named systemd units, but the script uses only the first literal unit. It does not address the required lab state, whose mechanism is: Single quotes suppress shell substitutions; double-quoted variable expansion preserves values.

B:

Use `if [ "$count" -ge 10 ]; then ...; fi` after validating `count` is an integer. This is an appropriate step for a DIFFERENT exercise, specifically: A script's `if` statement tests a numeric threshold using string comparison and misorders the values 9 and 10. It does not address the required lab state, whose mechanism is: Single quotes suppress shell substitutions; double-quoted variable expansion preserves values.

D:

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: Single quotes suppress shell substitutions; double-quoted variable expansion preserves values.

Question 490

The lab examiner asks for evidence after this assignment: A script generates a timestamped training archive but literal quotes around the `date` substitution prevent expansion. What is the decisive verification step?

  1. Known values 9 and 10 route to different expected branches.
  2. The file `/tmp/lab reports/status.txt` receives the line and no extra files are created.
  3. In a fixture where the first command exits 1, the second command does not run.
  4. The resulting filename contains the current date digits and `tar -tzf` lists expected members.

Explanation

Correct Answer

D:

The resulting filename contains the current date digits and `tar -tzf` lists expected members. This check confirms the expected effect of: Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`. It distinguishes the intended result from the original failure mechanism: Single quotes suppress shell substitutions; double-quoted variable expansion preserves values.

Incorrect Answers

A:

Known values 9 and 10 route to different expected branches. That verifies a separate lab task: A script's `if` statement tests a numeric threshold using string comparison and misorders the values 9 and 10. It does not validate the implementation required here: Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`.

B:

The file `/tmp/lab reports/status.txt` receives the line and no extra files are created. That verifies a separate lab task: A training script appends to a log whose path includes spaces and breaks because the variable is expanded unquoted. It does not validate the implementation required here: Use `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`.

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 `stamp=$(date +%Y%m%d)` and `tar -czf "/tmp/archive-$stamp.tgz" -C /srv/labs projectA`.