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 70

Question 690

In a hands-on RHCSA practice VM, the assigned outcome was: A Unix access test fails because a group was added in `/etc/group`, but a long-running user session still reports an old group set. What specific verification would demonstrate the target state?

  1. `getent passwd svc_labs` shows the selected UID and nonlogin shell.
  2. The new session reflects the updated group list and can access the permitted lab directory.
  3. `passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors.
  4. `getent passwd trainee1` ends with `/bin/bash` and an authorized test session starts.

Explanation

Correct Answer

B:

The new session reflects the updated group list and can access the permitted lab directory. This check confirms the expected effect of: Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`. It distinguishes the intended result from the original failure mechanism: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

Incorrect Answers

A:

`getent passwd svc_labs` shows the selected UID and nonlogin shell. That verifies a separate lab task: A service account must have a fixed UID and noninteractive shell for an isolated application, not a general human login. It does not validate the implementation required here: Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.

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: Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.

D:

`getent passwd trainee1` ends with `/bin/bash` and an authorized test session starts. That verifies a separate lab task: A lab user was mistakenly assigned `/bin/false` as login shell and cannot open an authorized interactive session. It does not validate the implementation required here: Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.

Question 691

A trainee is diagnosing: A Unix access test fails because a group was added in `/etc/group`, but a long-running user session still reports an old group set. Which root cause should they recognize before changing the system?

  1. Group membership may authorize privileged sudo actions through existing policy.
  2. Supplementary membership and primary group assignment are distinct account properties.
  3. A process inherits its group credentials when its session begins and may not pick up group changes dynamically.
  4. An invalid sudoers grammar can deny administrative access unexpectedly.

Explanation

Correct Answer

C:

A process inherits its group credentials when its session begins and may not pick up group changes dynamically. This explains the task's initial state: A Unix access test fails because a group was added in `/etc/group`, but a long-running user session still reports an old group set. The supported lab action is: Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.

Incorrect Answers

A:

Group membership may authorize privileged sudo actions through existing policy. This mechanism applies to another scenario: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. The given lab state instead requires the more specific cause in the correct choice.

B:

Supplementary membership and primary group assignment are distinct account properties. This mechanism applies to another scenario: A trainee is no longer authorized for the `analysts` supplemental group, but should retain their primary group. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 692

For this Linux administration lab: A Unix access test fails because a group was added in `/etc/group`, but a long-running user session still reports an old group set. Which safety and lifecycle check best prevents the same problem returning?

  1. Avoid interactive shells and shared credentials for application identities.
  2. Include end dates in contractor onboarding and remove access at offboarding.
  3. Review file ownership and service permissions after primary GID changes.
  4. Reauthenticate or restart dependent services after membership changes.

Explanation

Correct Answer

D:

Reauthenticate or restart dependent services after membership changes. This guards against recurrence of: A process inherits its group credentials when its session begins and may not pick up group changes dynamically. Confirm the lab's final state by: The new session reflects the updated group list and can access the permitted lab directory.

Incorrect Answers

A:

Avoid interactive shells and shared credentials for application identities. That control is best suited to a separate scenario: A service account must have a fixed UID and noninteractive shell for an isolated application, not a general human login. It is not the best safeguard for the current mechanism: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

B:

Include end dates in contractor onboarding and remove access at offboarding. That control is best suited to a separate scenario: A short-term external account must stop being usable on a specified end date while its password policy remains unchanged. It is not the best safeguard for the current mechanism: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

C:

Review file ownership and service permissions after primary GID changes. That control is best suited to a separate scenario: A team requires a default primary group different from the user-private group created with the account. It is not the best safeguard for the current mechanism: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

Question 693

A student working on a test RHEL10 instance receives this assignment: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. Which answer gives the correct practical approach?

  1. Use `semanage fcontext -a -t httpd_sys_content_t '/srv/custom-web(/.*)?'` then `restorecon -Rv /srv/custom-web` after verifying appropriate policy.
  2. Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree.
  3. Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.
  4. Use `restorecon -Rv /var/www/html/lab` after verifying the default web-content context mapping.

Explanation

Correct Answer

B:

Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree. This directly addresses the lab target: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. The underlying behavior is: Overly broad writable SELinux types increase the service's available write surface. Verification: SELinux context inspection shows read-only content separately from write-capable uploads and the application functions.

Incorrect Answers

A:

Use `semanage fcontext -a -t httpd_sys_content_t '/srv/custom-web(/.*)?'` then `restorecon -Rv /srv/custom-web` after verifying appropriate policy. This is an appropriate step for a DIFFERENT exercise, specifically: A web service moved to `/srv/custom-web` encounters SELinux denials because content copied from a home directory carries the wrong label. It does not address the required lab state, whose mechanism is: Overly broad writable SELinux types increase the service's available write surface.

C:

Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. It does not address the required lab state, whose mechanism is: Overly broad writable SELinux types increase the service's available write surface.

D:

Use `restorecon -Rv /var/www/html/lab` after verifying the default web-content context mapping. This is an appropriate step for a DIFFERENT exercise, specifically: A protected lab directory was copied from `/home` and now has inappropriate user-home SELinux contexts under `/var/www/html`. It does not address the required lab state, whose mechanism is: Overly broad writable SELinux types increase the service's available write surface.

Question 694

You have attempted this task on a test RHEL10 instance: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. Which command output or observation best confirms its success?

  1. `ls -Z /srv/custom-web/index.html` reports the expected content type and the service reads the file.
  2. `getsebool` reports on after reboot and the documented DB connection test succeeds.
  3. SELinux context inspection shows read-only content separately from write-capable uploads and the application functions.
  4. `stat -c '%a %U:%G'` displays the restricted mode and an unrelated user cannot modify it.

Explanation

Correct Answer

C:

SELinux context inspection shows read-only content separately from write-capable uploads and the application functions. This check confirms the expected effect of: Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree. It distinguishes the intended result from the original failure mechanism: Overly broad writable SELinux types increase the service's available write surface.

Incorrect Answers

A:

`ls -Z /srv/custom-web/index.html` reports the expected content type and the service reads the file. That verifies a separate lab task: A web service moved to `/srv/custom-web` encounters SELinux denials because content copied from a home directory carries the wrong label. It does not validate the implementation required here: Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree.

B:

`getsebool` reports on after reboot and the documented DB connection test succeeds. That verifies a separate lab task: An application hosted by Apache needs outbound database connections but SELinux policy denies them even with network routing functional. It does not validate the implementation required here: Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree.

D:

`stat -c '%a %U:%G'` displays the restricted mode and an unrelated user cannot modify it. That verifies a separate lab task: A user accidentally gives write permission to everyone on an application's configuration file. It does not validate the implementation required here: Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree.

Question 695

Troubleshoot the following RHEL 10 lab situation: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. Identify the key Linux mechanism behind the issue.

  1. Boot-time configuration and current kernel enforcement state are separate values.
  2. SELinux port types control service bind permission independently of firewalld.
  3. SELinux Booleans can authorize specific service behavior without disabling the entire MAC policy.
  4. Overly broad writable SELinux types increase the service's available write surface.

Explanation

Correct Answer

D:

Overly broad writable SELinux types increase the service's available write surface. This explains the task's initial state: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. The supported lab action is: Restore `httpd_sys_content_t` for read-only content and narrowly set approved writable label on the upload subtree.

Incorrect Answers

A:

Boot-time configuration and current kernel enforcement state are separate values. This mechanism applies to another scenario: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. The given lab state instead requires the more specific cause in the correct choice.

B:

SELinux port types control service bind permission independently of firewalld. This mechanism applies to another scenario: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. The given lab state instead requires the more specific cause in the correct choice.

C:

SELinux Booleans can authorize specific service behavior without disabling the entire MAC policy. This mechanism applies to another scenario: An application hosted by Apache needs outbound database connections but SELinux policy denies them even with network routing functional. The given lab state instead requires the more specific cause in the correct choice.

Question 696

Following lab verification, document the preventive or persistence-oriented procedure for: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. Which practice is most suitable?

  1. Keep SELinux write types restricted to paths with documented write requirements.
  2. Use audited AVC evidence and type-appropriate remedies, keeping enforcing mode active.
  3. Use policy-backed fcontext mappings for nonstandard service directories.
  4. Enable only approved service-specific Booleans and review the resulting access scope.

Explanation

Correct Answer

A:

Keep SELinux write types restricted to paths with documented write requirements. This guards against recurrence of: Overly broad writable SELinux types increase the service's available write surface. Confirm the lab's final state by: SELinux context inspection shows read-only content separately from write-capable uploads and the application functions.

Incorrect Answers

B:

Use audited AVC evidence and type-appropriate remedies, keeping enforcing mode active. That control is best suited to a separate scenario: A lab administrator disables SELinux to stop web errors without checking whether a label denial caused them. It is not the best safeguard for the current mechanism: Overly broad writable SELinux types increase the service's available write surface.

C:

Use policy-backed fcontext mappings for nonstandard service directories. That control is best suited to a separate scenario: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. It is not the best safeguard for the current mechanism: Overly broad writable SELinux types increase the service's available write surface.

D:

Enable only approved service-specific Booleans and review the resulting access scope. That control is best suited to a separate scenario: An application hosted by Apache needs outbound database connections but SELinux policy denies them even with network routing functional. It is not the best safeguard for the current mechanism: Overly broad writable SELinux types increase the service's available write surface.

Question 697

On an isolated enterprise lab VM, perform the following practical task: A newly created shared work directory gives files unexpectedly broad default permissions. Which action should be carried out after confirming the lab prerequisites?

  1. Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory.
  2. Run `find /srv/labs -type f -mtime -1 -print` and examine the returned paths.
  3. Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file.
  4. Run `pwd`, then `cd /srv/labs/projectA` after checking it exists; use absolute paths for the target edit.

Explanation

Correct Answer

C:

Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file. This directly addresses the lab target: A newly created shared work directory gives files unexpectedly broad default permissions. The underlying behavior is: The umask removes requested permission bits when new filesystem objects are created. Verification: `umask` reports `0027`, while `stat -c %a /tmp/private-build/newfile` shows mode no broader than `640` for a normal creation.

Incorrect Answers

A:

Use `find /tmp/lab-build -maxdepth 1 -type f -name '*.tmp' -print` first; delete only reviewed matches within the disposable lab directory. This is an appropriate step for a DIFFERENT exercise, specifically: A cleanup task targets temporary build artifacts, but a wildcard could accidentally match production data. It does not address the required lab state, whose mechanism is: The umask removes requested permission bits when new filesystem objects are created.

B:

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: The umask removes requested permission bits when new filesystem objects are created.

D:

Run `pwd`, then `cd /srv/labs/projectA` after checking it exists; use absolute paths for the target edit. This is an appropriate step for a DIFFERENT exercise, specifically: On a disposable RHEL 10 training host, an operator enters a nested work directory but later edits the wrong file because the current path was assumed. It does not address the required lab state, whose mechanism is: The umask removes requested permission bits when new filesystem objects are created.

Question 698

The lab examiner asks for evidence after this assignment: A newly created shared work directory gives files unexpectedly broad default permissions. What is the decisive verification step?

  1. `stat -c '%a %y'` on source and destination confirms equivalent permissions and modification time.
  2. The preflight output shows only designated `.tmp` files and unrelated files remain after any approved deletion.
  3. `readlink /usr/local/bin/lab-report` shows the intended target and executing the shortcut reaches it.
  4. `umask` reports `0027`, while `stat -c %a /tmp/private-build/newfile` shows mode no broader than `640` for a normal creation.

Explanation

Correct Answer

D:

`umask` reports `0027`, while `stat -c %a /tmp/private-build/newfile` shows mode no broader than `640` for a normal creation. This check confirms the expected effect of: Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file. It distinguishes the intended result from the original failure mechanism: The umask removes requested permission bits when new filesystem objects are created.

Incorrect Answers

A:

`stat -c '%a %y'` on source and destination confirms equivalent permissions and modification time. That verifies a separate lab task: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. It does not validate the implementation required here: Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file.

B:

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: Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file.

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: Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file.

Question 699

A training host has this situation: A newly created shared work directory gives files unexpectedly broad default permissions. Which system behavior best explains the original failure or risk?

  1. The umask removes requested permission bits when new filesystem objects are created.
  2. Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes.
  3. Unix ugo/rwx permission bits control who may read or modify ordinary files.
  4. Using `-C` sets a stable archive root and gzip is selected using `-z`.

Explanation

Correct Answer

A:

The umask removes requested permission bits when new filesystem objects are created. This explains the task's initial state: A newly created shared work directory gives files unexpectedly broad default permissions. The supported lab action is: Set a more restrictive shell umask such as `umask 027` in the test session before creating the sample file.

Incorrect Answers

B:

Plain copy operations may produce destination metadata based on defaults rather than preserving source attributes. This mechanism applies to another scenario: A student copies a permission-sensitive fixture and unexpectedly changes its timestamp and permission bits. The given lab state instead requires the more specific cause in the correct choice.

C:

Unix ugo/rwx permission bits control who may read or modify ordinary files. This mechanism applies to another scenario: A private lab key file is incorrectly world-readable and must be accessible only to its owner. 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 700

A student has implemented the following configuration: A newly created shared work directory gives files unexpectedly broad default permissions. What repeatable control best reduces regressions or unsafe changes?

  1. Maintain positive and negative sample cases for account naming validation.
  2. Apply a reviewed umask in the appropriate persistent login startup policy for the intended account.
  3. Start scripted changes with an explicit `cd` guarded by failure checking and record the resolved target path.
  4. Use anchored regular expressions and independent sample positive/negative test lines.

Explanation

Correct Answer

B:

Apply a reviewed umask in the appropriate persistent login startup policy for the intended account. This guards against recurrence of: The umask removes requested permission bits when new filesystem objects are created. Confirm the lab's final state by: `umask` reports `0027`, while `stat -c %a /tmp/private-build/newfile` shows mode no broader than `640` for a normal creation.

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: The umask removes requested permission bits when new filesystem objects are created.

C:

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: The umask removes requested permission bits when new filesystem objects are created.

D:

Use anchored regular expressions and independent sample positive/negative test lines. That control is best suited to a separate scenario: A lab report contains 5xx server responses mixed with successful lines; a student must count only lines beginning with an HTTP 5xx code. It is not the best safeguard for the current mechanism: The umask removes requested permission bits when new filesystem objects are created.