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 69

Question 680

Following lab verification, document the preventive or persistence-oriented procedure for: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. Which practice is most suitable?

  1. Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area.
  2. Use consistent UID/GID mapping and least-privilege export settings.
  3. Validate map syntax and restart/enable autofs after controlled changes.
  4. Include filesystem shrink capability in capacity design decisions before provisioning.

Explanation

Correct Answer

A:

Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area. This guards against recurrence of: The sticky bit constrains unlink and rename in a shared writable directory. Confirm the lab's final state by: Two test users can create files but one cannot remove the other's file without applicable privilege.

Incorrect Answers

B:

Use consistent UID/GID mapping and least-privilege export settings. That control is best suited to a separate scenario: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.

C:

Validate map syntax and restart/enable autofs after controlled changes. That control is best suited to a separate scenario: A large remote home-directory NFS tree should mount on demand rather than all at login. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.

D:

Include filesystem shrink capability in capacity design decisions before provisioning. That control is best suited to a separate scenario: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.

Question 681

On an offline training clone, perform the following practical task: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. Which action should be carried out after confirming the lab prerequisites?

  1. Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.
  2. Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.
  3. Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.
  4. Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.

Explanation

Correct Answer

C:

Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method. This directly addresses the lab target: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. The underlying behavior is: Installing a kernel does not guarantee the desired boot entry is selected. Verification: `grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`.

Incorrect Answers

A:

Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly. This is an appropriate step for a DIFFERENT exercise, specifically: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It does not address the required lab state, whose mechanism is: Installing a kernel does not guarantee the desired boot entry is selected.

B:

Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions. This is an appropriate step for a DIFFERENT exercise, specifically: A recurring cron script runs as root because it was inserted into the system crontab, while it should run as a least-privilege reporting account. It does not address the required lab state, whose mechanism is: Installing a kernel does not guarantee the desired boot entry is selected.

D:

Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification. This is an appropriate step for a DIFFERENT exercise, specifically: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. It does not address the required lab state, whose mechanism is: Installing a kernel does not guarantee the desired boot entry is selected.

Question 682

The lab examiner asks for evidence after this assignment: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. What is the decisive verification step?

  1. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.
  2. `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.
  3. The source list displays the replacement server and offset converges within the intended test tolerance.
  4. `grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`.

Explanation

Correct Answer

D:

`grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`. This check confirms the expected effect of: Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method. It distinguishes the intended result from the original failure mechanism: Installing a kernel does not guarantee the desired boot entry is selected.

Incorrect Answers

A:

`systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot. That verifies a separate lab task: A daemon is started manually after package installation but must be reliably available after reboots. It does not validate the implementation required here: Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.

B:

`chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status. That verifies a separate lab task: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. It does not validate the implementation required here: Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.

C:

The source list displays the replacement server and offset converges within the intended test tolerance. That verifies a separate lab task: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It does not validate the implementation required here: Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.

Question 683

A training host has this situation: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. Which system behavior best explains the original failure or risk?

  1. Installing a kernel does not guarantee the desired boot entry is selected.
  2. DNF update resolves and records package lifecycle changes through configured repositories.
  3. Direct file copying bypasses RPM lifecycle metadata and dependency handling.
  4. Template unit instance identifiers distinguish multiple managed services.

Explanation

Correct Answer

A:

Installing a kernel does not guarantee the desired boot entry is selected. This explains the task's initial state: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. The supported lab action is: Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.

Incorrect Answers

B:

DNF update resolves and records package lifecycle changes through configured repositories. This mechanism applies to another scenario: An RPM package on a training node is stale; the administrator needs to apply approved security updates without reinstalling everything. The given lab state instead requires the more specific cause in the correct choice.

C:

Direct file copying bypasses RPM lifecycle metadata and dependency handling. This mechanism applies to another scenario: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. The given lab state instead requires the more specific cause in the correct choice.

D:

Template unit instance identifiers distinguish multiple managed services. This mechanism applies to another scenario: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. The given lab state instead requires the more specific cause in the correct choice.

Question 684

A student has implemented the following configuration: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. What repeatable control best reduces regressions or unsafe changes?

  1. Record firmware mode and test recovery entry after bootloader configuration changes.
  2. Verify selected kernel and retain a known-good fallback after kernel maintenance.
  3. Review timer-to-service linkage and timer state after every deployment.
  4. Review executable paths and file ownership as part of service deployment testing.

Explanation

Correct Answer

B:

Verify selected kernel and retain a known-good fallback after kernel maintenance. This guards against recurrence of: Installing a kernel does not guarantee the desired boot entry is selected. Confirm the lab's final state by: `grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`.

Incorrect Answers

A:

Record firmware mode and test recovery entry after bootloader configuration changes. That control is best suited to a separate scenario: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It is not the best safeguard for the current mechanism: Installing a kernel does not guarantee the desired boot entry is selected.

C:

Review timer-to-service linkage and timer state after every deployment. That control is best suited to a separate scenario: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. It is not the best safeguard for the current mechanism: Installing a kernel does not guarantee the desired boot entry is selected.

D:

Review executable paths and file ownership as part of service deployment testing. That control is best suited to a separate scenario: A new custom service has an `ExecStart` path that no longer exists after the application was moved. It is not the best safeguard for the current mechanism: Installing a kernel does not guarantee the desired boot entry is selected.

Question 685

You are responsible for a local virtualization classroom. The required hands-on outcome is: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. Select the most appropriate implementation step.

  1. Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`.
  2. Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.
  3. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.
  4. Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

Explanation

Correct Answer

D:

Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured. This directly addresses the lab target: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. The underlying behavior is: Firewalld permissions do not start application daemons or guarantee boot persistence. Verification: The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled.

Incorrect Answers

A:

Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`. This is an appropriate step for a DIFFERENT exercise, specifically: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. It does not address the required lab state, whose mechanism is: Firewalld permissions do not start application daemons or guarantee boot persistence.

B:

Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It does not address the required lab state, whose mechanism is: Firewalld permissions do not start application daemons or guarantee boot persistence.

C:

Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. It does not address the required lab state, whose mechanism is: Firewalld permissions do not start application daemons or guarantee boot persistence.

Question 686

After a lab configuration change, verify: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. Which result most directly proves the desired system state?

  1. The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled.
  2. The port remains listed in permanent configuration and works after a controlled reboot.
  3. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.
  4. `ip -6 route` shows only the intended routes and a local subnet test succeeds.

Explanation

Correct Answer

A:

The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled. This check confirms the expected effect of: Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured. It distinguishes the intended result from the original failure mechanism: Firewalld permissions do not start application daemons or guarantee boot persistence.

Incorrect Answers

B:

The port remains listed in permanent configuration and works after a controlled reboot. That verifies a separate lab task: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. It does not validate the implementation required here: Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

C:

After reconnect or reboot `nmcli con show` and `ip addr` still report the address. That verifies a separate lab task: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not validate the implementation required here: Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

D:

`ip -6 route` shows only the intended routes and a local subnet test succeeds. That verifies a separate lab task: An IPv6 connection receives a default route from router advertisements when policy requires the test host to use only a specified local IPv6 subnet. It does not validate the implementation required here: Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

Question 687

In an EX200-style practice lab, this condition exists: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. Which explanation correctly identifies the underlying issue?

  1. ICMP reachability to a gateway does not prove DNS or TCP application availability.
  2. Firewalld permissions do not start application daemons or guarantee boot persistence.
  3. Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.
  4. Firewalld runtime rules and permanent rules are separate states.

Explanation

Correct Answer

B:

Firewalld permissions do not start application daemons or guarantee boot persistence. This explains the task's initial state: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. The supported lab action is: Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

Incorrect Answers

A:

ICMP reachability to a gateway does not prove DNS or TCP application availability. This mechanism applies to another scenario: The host can ping its gateway but an HTTPS connection fails; the operator wants to blame DNS without checking name resolution. The given lab state instead requires the more specific cause in the correct choice.

C:

Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default. This mechanism applies to another scenario: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. The given lab state instead requires the more specific cause in the correct choice.

D:

Firewalld runtime rules and permanent rules are separate states. This mechanism applies to another scenario: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. The given lab state instead requires the more specific cause in the correct choice.

Question 688

After completing this practical task on a local virtualization classroom: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. Which operational safeguard helps keep the result correct and safe?

  1. Audit both DNS source and search domains when moving between networks.
  2. Set the static hostname and confirm it is resolvable under the site's DNS plan.
  3. Confirm unit enablement, listener, zone and end-to-end client response together.
  4. Use minimum required allowed services while retaining firewalld enforcement.

Explanation

Correct Answer

C:

Confirm unit enablement, listener, zone and end-to-end client response together. This guards against recurrence of: Firewalld permissions do not start application daemons or guarantee boot persistence. Confirm the lab's final state by: The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled.

Incorrect Answers

A:

Audit both DNS source and search domains when moving between networks. That control is best suited to a separate scenario: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. It is not the best safeguard for the current mechanism: Firewalld permissions do not start application daemons or guarantee boot persistence.

B:

Set the static hostname and confirm it is resolvable under the site's DNS plan. That control is best suited to a separate scenario: A hostname change is applied only with the `hostname` runtime command and resets after restart. It is not the best safeguard for the current mechanism: Firewalld permissions do not start application daemons or guarantee boot persistence.

D:

Use minimum required allowed services while retaining firewalld enforcement. That control is best suited to a separate scenario: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It is not the best safeguard for the current mechanism: Firewalld permissions do not start application daemons or guarantee boot persistence.

Question 689

Lab exercise on a nonproduction Linux administration sandbox: 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 proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.
  2. Use `usermod -g appops svc_labs` after ensuring the target group exists and reviewing owned files.
  3. After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data.
  4. Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access.

Explanation

Correct Answer

A:

Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`. This directly addresses the lab target: 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 underlying behavior is: A process inherits its group credentials when its session begins and may not pick up group changes dynamically. Verification: The new session reflects the updated group list and can access the permitted lab directory.

Incorrect Answers

B:

Use `usermod -g appops svc_labs` after ensuring the target group exists and reviewing owned files. This is an appropriate step for a DIFFERENT exercise, specifically: A team requires a default primary group different from the user-private group created with the account. It does not address the required lab state, whose mechanism is: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

C:

After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data. This is an appropriate step for a DIFFERENT exercise, specifically: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. It does not address the required lab state, whose mechanism is: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

D:

Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access. This is an appropriate step for a DIFFERENT exercise, specifically: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. It does not address the required lab state, whose mechanism is: A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

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`.