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 60

Question 590

After a lab configuration change, verify: A new user must have a private home directory rather than inherited group-read access. Which result most directly proves the desired system state?

  1. `stat -c '%a %U:%G'` reports the expected properties and a different test user cannot traverse the home.
  2. `id trainee1` includes `analysts` and the prior supplementary groups remain.
  3. `passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors.
  4. `chage -l contractor1` shows the intended account expiration date.

Explanation

Correct Answer

A:

`stat -c '%a %U:%G'` reports the expected properties and a different test user cannot traverse the home. This check confirms the expected effect of: Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`. It distinguishes the intended result from the original failure mechanism: Directory traversal and ownership control privacy of files below the home directory.

Incorrect Answers

B:

`id trainee1` includes `analysts` and the prior supplementary groups remain. That verifies a separate lab task: A user must join the `analysts` group without losing their existing supplementary groups. It does not validate the implementation required here: Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.

C:

`passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors. That verifies a separate lab task: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. It does not validate the implementation required here: Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.

D:

`chage -l contractor1` shows the intended account expiration date. That verifies a separate lab task: A short-term external account must stop being usable on a specified end date while its password policy remains unchanged. It does not validate the implementation required here: Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.

Question 591

In an EX200-style practice lab, this condition exists: A new user must have a private home directory rather than inherited group-read access. Which explanation correctly identifies the underlying issue?

  1. Linux group creation establishes a named group but does not automatically add users or set file ownership.
  2. Directory traversal and ownership control privacy of files below the home directory.
  3. An invalid sudoers grammar can deny administrative access unexpectedly.
  4. Account expiration is separate from password expiration or maximum password age.

Explanation

Correct Answer

B:

Directory traversal and ownership control privacy of files below the home directory. This explains the task's initial state: A new user must have a private home directory rather than inherited group-read access. The supported lab action is: Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.

Incorrect Answers

A:

Linux group creation establishes a named group but does not automatically add users or set file ownership. This mechanism applies to another scenario: A project team needs a new local group `analysts` to own shared reports. The given lab state instead requires the more specific cause in the correct choice.

C:

An invalid sudoers grammar can deny administrative access unexpectedly. This mechanism applies to another scenario: An operator edits `/etc/sudoers` using an ordinary editor and introduces invalid syntax, breaking privilege escalation. The given lab state instead requires the more specific cause in the correct choice.

D:

Account expiration is separate from password expiration or maximum password age. This mechanism applies to another scenario: A short-term external account must stop being usable on a specified end date while its password policy remains unchanged. The given lab state instead requires the more specific cause in the correct choice.

Question 592

After completing this practical task on a local virtualization classroom: A new user must have a private home directory rather than inherited group-read access. Which operational safeguard helps keep the result correct and safe?

  1. Review administrative group memberships on every role transfer.
  2. Always validate sudoers changes with `visudo -c` before ending the recovery session.
  3. Apply secure home defaults and review them at account creation.
  4. Review approved shells during interactive account provisioning.

Explanation

Correct Answer

C:

Apply secure home defaults and review them at account creation. This guards against recurrence of: Directory traversal and ownership control privacy of files below the home directory. Confirm the lab's final state by: `stat -c '%a %U:%G'` reports the expected properties and a different test user cannot traverse the home.

Incorrect Answers

A:

Review administrative group memberships on every role transfer. That control is best suited to a separate scenario: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. It is not the best safeguard for the current mechanism: Directory traversal and ownership control privacy of files below the home directory.

B:

Always validate sudoers changes with `visudo -c` before ending the recovery session. That control is best suited to a separate scenario: An operator edits `/etc/sudoers` using an ordinary editor and introduces invalid syntax, breaking privilege escalation. It is not the best safeguard for the current mechanism: Directory traversal and ownership control privacy of files below the home directory.

D:

Review approved shells during interactive account provisioning. That control is best suited to a separate scenario: A lab user was mistakenly assigned `/bin/false` as login shell and cannot open an authorized interactive session. It is not the best safeguard for the current mechanism: Directory traversal and ownership control privacy of files below the home directory.

Question 593

Lab exercise on a nonproduction Linux administration sandbox: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.
  2. Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population.
  3. Check `semanage port -l | grep http_port_t`; if 8088 is unassigned, use `semanage port -a -t http_port_t -p tcp 8088`.
  4. Set `umask 077` in the sensitive workflow before creating the secret fixture.

Explanation

Correct Answer

A:

Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload. This directly addresses the lab target: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. The underlying behavior is: Firewall policies are matched by zones, independently of service startup or SELinux port rights. Verification: The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted.

Incorrect Answers

B:

Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population. This is an appropriate step for a DIFFERENT exercise, specifically: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. It does not address the required lab state, whose mechanism is: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

C:

Check `semanage port -l | grep http_port_t`; if 8088 is unassigned, use `semanage port -a -t http_port_t -p tcp 8088`. This is an appropriate step for a DIFFERENT exercise, specifically: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. It does not address the required lab state, whose mechanism is: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

D:

Set `umask 077` in the sensitive workflow before creating the secret fixture. This is an appropriate step for a DIFFERENT exercise, specifically: A shell session creates files with default modes exposing group-readable secrets to unrelated users. It does not address the required lab state, whose mechanism is: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

Question 594

In a hands-on RHCSA practice VM, the assigned outcome was: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. What specific verification would demonstrate the target state?

  1. A known private-key client logs in as the expected user while unauthorized keys fail.
  2. The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted.
  3. `getenforce` shows permissive during the test, then enforcing after restoration without assuming persistence.
  4. The Boolean remains on after reboot and `getsebool` confirms the value.

Explanation

Correct Answer

B:

The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted. This check confirms the expected effect of: Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload. It distinguishes the intended result from the original failure mechanism: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

Incorrect Answers

A:

A known private-key client logs in as the expected user while unauthorized keys fail. That verifies a separate lab task: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. It does not validate the implementation required here: Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.

C:

`getenforce` shows permissive during the test, then enforcing after restoration without assuming persistence. That verifies a separate lab task: An administrator temporarily changes SELinux to permissive mode for diagnostics and believes it will remain so after reboot. It does not validate the implementation required here: Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.

D:

The Boolean remains on after reboot and `getsebool` confirms the value. That verifies a separate lab task: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. It does not validate the implementation required here: Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.

Question 595

A trainee is diagnosing: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. Which root cause should they recognize before changing the system?

  1. `chcon` changes an inode label temporarily without updating the default file context database.
  2. SSH private credentials require protected ownership and permissions distinct from public authorized keys.
  3. Firewall policies are matched by zones, independently of service startup or SELinux port rights.
  4. A umask subtracts permission bits from default requested modes at object creation.

Explanation

Correct Answer

C:

Firewall policies are matched by zones, independently of service startup or SELinux port rights. This explains the task's initial state: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. The supported lab action is: Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.

Incorrect Answers

A:

`chcon` changes an inode label temporarily without updating the default file context database. This mechanism applies to another scenario: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. The given lab state instead requires the more specific cause in the correct choice.

B:

SSH private credentials require protected ownership and permissions distinct from public authorized keys. This mechanism applies to another scenario: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. The given lab state instead requires the more specific cause in the correct choice.

D:

A umask subtracts permission bits from default requested modes at object creation. This mechanism applies to another scenario: A shell session creates files with default modes exposing group-readable secrets to unrelated users. The given lab state instead requires the more specific cause in the correct choice.

Question 596

For this Linux administration lab: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. Which safety and lifecycle check best prevents the same problem returning?

  1. Diagnose DAC and SELinux separately, keeping both minimum necessary permissions and labels.
  2. Check existing assignments before modifying SELinux port labels.
  3. Keep SELinux write types restricted to paths with documented write requirements.
  4. Check active zone, SELinux port permission and service listener together.

Explanation

Correct Answer

D:

Check active zone, SELinux port permission and service listener together. This guards against recurrence of: Firewall policies are matched by zones, independently of service startup or SELinux port rights. Confirm the lab's final state by: The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted.

Incorrect Answers

A:

Diagnose DAC and SELinux separately, keeping both minimum necessary permissions and labels. That control is best suited to a separate scenario: A custom service path is mislabeled and a technician repeatedly applies `chmod 777` without resolving access denials. It is not the best safeguard for the current mechanism: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

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: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

C:

Keep SELinux write types restricted to paths with documented write requirements. That control is best suited to a separate scenario: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. It is not the best safeguard for the current mechanism: Firewall policies are matched by zones, independently of service startup or SELinux port rights.

Question 597

A student working on a test RHEL10 instance receives this assignment: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. Which answer gives the correct practical approach?

  1. Run `tar -tf /tmp/delivery.tar` and only then extract the trusted fixture into a new disposable staging directory.
  2. Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`.
  3. Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required.
  4. Use `tail -n 30 -f /tmp/labapp.log` to follow appended fixture events in a test terminal.

Explanation

Correct Answer

B:

Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`. This directly addresses the lab target: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. The underlying behavior is: Hard links name the same inode and cannot ordinarily link across separate file systems. Verification: `stat -c '%i %h'` reports the same inode and an increased link count for both paths.

Incorrect Answers

A:

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: Hard links name the same inode and cannot ordinarily link across separate file systems.

C:

Use `cp -p /tmp/source.conf /tmp/review.conf` when preservation of source metadata is required. This is an appropriate step for a DIFFERENT exercise, specifically: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. It does not address the required lab state, whose mechanism is: Hard links name the same inode and cannot ordinarily link across separate file systems.

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: Hard links name the same inode and cannot ordinarily link across separate file systems.

Question 598

You have attempted this task on a test RHEL10 instance: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. Which command output or observation best confirms its success?

  1. The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion.
  2. The operator identifies documented syntax for `enable --now` and `is-enabled` from local manual pages.
  3. `stat -c '%i %h'` reports the same inode and an increased link count for both paths.
  4. The extracted files match `tar -tjf` listing and reside under the lab restore directory.

Explanation

Correct Answer

C:

`stat -c '%i %h'` reports the same inode and an increased link count for both paths. This check confirms the expected effect of: Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`. It distinguishes the intended result from the original failure mechanism: Hard links name the same inode and cannot ordinarily link across separate file systems.

Incorrect Answers

A:

The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion. That verifies a separate lab task: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. It does not validate the implementation required here: Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`.

B:

The operator identifies documented syntax for `enable --now` and `is-enabled` from local manual pages. That verifies a separate lab task: The team needs the documented purpose and arguments of `systemctl` without accessing the Internet during training. It does not validate the implementation required here: Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`.

D:

The extracted files match `tar -tjf` listing and reside under the lab restore directory. That verifies a separate lab task: A restore workflow is given a `.tar.bz2` training archive and a previous attempt used gzip extraction flags. It does not validate the implementation required here: Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`.

Question 599

Troubleshoot the following RHEL 10 lab situation: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. Identify the key Linux mechanism behind the issue.

  1. Archive extraction can create paths and overwrite files relative to the extraction root.
  2. Bzip2-compressed tar archives use the `-j` decompression option, not the gzip `-z` option.
  3. Public-key authentication requires an authorized matching key in the correct user account.
  4. Hard links name the same inode and cannot ordinarily link across separate file systems.

Explanation

Correct Answer

D:

Hard links name the same inode and cannot ordinarily link across separate file systems. This explains the task's initial state: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. The supported lab action is: Create a hard link with `ln /tmp/inode-lab/record /tmp/inode-lab/record.link`.

Incorrect Answers

A:

Archive extraction can create paths and overwrite files relative to the extraction root. This mechanism applies to another scenario: A prebuilt archive contains paths the student has not inspected; extracting it as root into `/` would be risky. The given lab state instead requires the more specific cause in the correct choice.

B:

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.

C:

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.

Question 600

Following lab verification, document the preventive or persistence-oriented procedure for: Two paths should reference the same inode so edits through either name appear in the other, entirely on one file system. Which practice is most suitable?

  1. Use hard links only for same-filesystem files and document how unlinking each name affects retention.
  2. Constrain glob paths and check match existence before iterating over files.
  3. Check effective identity and environment before privileged operations, then return to a normal account.
  4. Manage known host fingerprints and investigate unexpected key changes instead of setting StrictHostKeyChecking=no.

Explanation

Correct Answer

A:

Use hard links only for same-filesystem files and document how unlinking each name affects retention. This guards against recurrence of: Hard links name the same inode and cannot ordinarily link across separate file systems. Confirm the lab's final state by: `stat -c '%i %h'` reports the same inode and an increased link count for both paths.

Incorrect Answers

B:

Constrain glob paths and check match existence before iterating over files. That control is best suited to a separate scenario: A shell script is supposed to process every `.conf` file, but its wildcard is quoted as a single literal. It is not the best safeguard for the current mechanism: Hard links name the same inode and cannot ordinarily link across separate file systems.

C:

Check effective identity and environment before privileged operations, then return to a normal account. That control is best suited to a separate scenario: A student becomes root with `su` but finds the previous user's PATH and working directory still active during an administrative test. It is not the best safeguard for the current mechanism: Hard links name the same inode and cannot ordinarily link across separate file systems.

D:

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: Hard links name the same inode and cannot ordinarily link across separate file systems.