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 72

Question 710

You have attempted this task on a local virtualization classroom: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. Which command output or observation best confirms its success?

  1. The mount options show `rw` and a controlled authorized file creation succeeds.
  2. Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map.
  3. A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data.
  4. The verification returns no invalid-entry errors before the reboot and the mount becomes active.

Explanation

Correct Answer

C:

A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data. This check confirms the expected effect of: Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration. It distinguishes the intended result from the original failure mechanism: A mountpoint name does not prove which remote host/export currently backs it.

Incorrect Answers

A:

The mount options show `rw` and a controlled authorized file creation succeeds. That verifies a separate lab task: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. It does not validate the implementation required here: Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration.

B:

Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map. That verifies a separate lab task: A large remote home-directory NFS tree should mount on demand rather than all at login. It does not validate the implementation required here: Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration.

D:

The verification returns no invalid-entry errors before the reboot and the mount becomes active. That verifies a separate lab task: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It does not validate the implementation required here: Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration.

Question 711

Troubleshoot the following RHEL 10 lab situation: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. Identify the key Linux mechanism behind the issue.

  1. Autofs configuration changes may need the map service to reload before affecting new mounts.
  2. Mount option flags can override normal file permission expectations.
  3. A busy mount cannot be detached normally while processes retain open references.
  4. A mountpoint name does not prove which remote host/export currently backs it.

Explanation

Correct Answer

D:

A mountpoint name does not prove which remote host/export currently backs it. This explains the task's initial state: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. The supported lab action is: Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration.

Incorrect Answers

A:

Autofs configuration changes may need the map service to reload before affecting new mounts. This mechanism applies to another scenario: A new autofs indirect map was edited but clients keep using the previous exported path. The given lab state instead requires the more specific cause in the correct choice.

B:

Mount option flags can override normal file permission expectations. This mechanism applies to another scenario: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. The given lab state instead requires the more specific cause in the correct choice.

C:

A busy mount cannot be detached normally while processes retain open references. This mechanism applies to another scenario: A student tries to unmount an NFS training mount while another process has its current directory inside it. The given lab state instead requires the more specific cause in the correct choice.

Question 712

Following lab verification, document the preventive or persistence-oriented procedure for: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. Which practice is most suitable?

  1. Verify resolved mount source during network filesystem migrations.
  2. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.
  3. Use stable identifiers and run `findmnt --verify` before rebooting.
  4. Check effective mount flags before broadly changing ownership or file modes.

Explanation

Correct Answer

A:

Verify resolved mount source during network filesystem migrations. This guards against recurrence of: A mountpoint name does not prove which remote host/export currently backs it. Confirm the lab's final state by: A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data.

Incorrect Answers

B:

Treat fstab modifications as high-impact and test mount behavior while a recovery console is available. That control is best suited to a separate scenario: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It is not the best safeguard for the current mechanism: A mountpoint name does not prove which remote host/export currently backs it.

C:

Use stable identifiers and run `findmnt --verify` before rebooting. That control is best suited to a separate scenario: A static XFS mount works when issued manually but vanishes after every reboot. It is not the best safeguard for the current mechanism: A mountpoint name does not prove which remote host/export currently backs it.

D:

Check effective mount flags before broadly changing ownership or file modes. That control is best suited to a separate scenario: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. It is not the best safeguard for the current mechanism: A mountpoint name does not prove which remote host/export currently backs it.

Question 713

On a nonproduction Linux administration sandbox, perform the following practical task: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. Which action should be carried out after confirming the lab prerequisites?

  1. Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.
  2. Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference.
  3. Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`.
  4. Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.

Explanation

Correct Answer

C:

Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`. This directly addresses the lab target: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. The underlying behavior is: A saved daemon configuration change may not automatically change the running daemon state. Verification: The source list displays the replacement server and offset converges within the intended test tolerance.

Incorrect Answers

A:

Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system. This is an appropriate step for a DIFFERENT exercise, specifically: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. It does not address the required lab state, whose mechanism is: A saved daemon configuration change may not automatically change the running daemon state.

B:

Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference. This is an appropriate step for a DIFFERENT exercise, specifically: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. It does not address the required lab state, whose mechanism is: A saved daemon configuration change may not automatically change the running daemon state.

D:

Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed. This is an appropriate step for a DIFFERENT exercise, specifically: A daemon is started manually after package installation but must be reliably available after reboots. It does not address the required lab state, whose mechanism is: A saved daemon configuration change may not automatically change the running daemon state.

Question 714

The lab examiner asks for evidence after this assignment: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. What is the decisive verification step?

  1. `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.
  2. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.
  3. `grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`.
  4. The source list displays the replacement server and offset converges within the intended test tolerance.

Explanation

Correct Answer

D:

The source list displays the replacement server and offset converges within the intended test tolerance. This check confirms the expected effect of: Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`. It distinguishes the intended result from the original failure mechanism: A saved daemon configuration change may not automatically change the running daemon state.

Incorrect Answers

A:

`systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged. That verifies a separate lab task: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. It does not validate the implementation required here: Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`.

B:

`systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit. That verifies a separate lab task: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. It does not validate the implementation required here: Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`.

C:

`grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`. That verifies a separate lab task: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. It does not validate the implementation required here: Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`.

Question 715

A training host has this situation: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. Which system behavior best explains the original failure or risk?

  1. A saved daemon configuration change may not automatically change the running daemon state.
  2. An `at` job is one-shot, unlike a recurring cron schedule.
  3. Runtime activation and boot-time activation are separate systemd states.
  4. Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.

Explanation

Correct Answer

A:

A saved daemon configuration change may not automatically change the running daemon state. This explains the task's initial state: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. The supported lab action is: Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`.

Incorrect Answers

B:

An `at` job is one-shot, unlike a recurring cron schedule. This mechanism applies to another scenario: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. The given lab state instead requires the more specific cause in the correct choice.

C:

Runtime activation and boot-time activation are separate systemd states. This mechanism applies to another scenario: A daemon is started manually after package installation but must be reliably available after reboots. The given lab state instead requires the more specific cause in the correct choice.

D:

Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS. This mechanism applies to another scenario: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. The given lab state instead requires the more specific cause in the correct choice.

Question 716

A student has implemented the following configuration: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. What repeatable control best reduces regressions or unsafe changes?

  1. Maintain approved time servers and monitor drift/offset after network changes.
  2. Record both the configuration file change and observed runtime source.
  3. Test full cold-boot readiness, not just whether a unit says active.
  4. Record firmware mode and test recovery entry after bootloader configuration changes.

Explanation

Correct Answer

B:

Record both the configuration file change and observed runtime source. This guards against recurrence of: A saved daemon configuration change may not automatically change the running daemon state. Confirm the lab's final state by: The source list displays the replacement server and offset converges within the intended test tolerance.

Incorrect Answers

A:

Maintain approved time servers and monitor drift/offset after network changes. That control is best suited to a separate scenario: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. It is not the best safeguard for the current mechanism: A saved daemon configuration change may not automatically change the running daemon state.

C:

Test full cold-boot readiness, not just whether a unit says active. That control is best suited to a separate scenario: A service is enabled and active, but the actual application fails after boot because a required mount is not available in time. It is not the best safeguard for the current mechanism: A saved daemon configuration change may not automatically change the running daemon state.

D:

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: A saved daemon configuration change may not automatically change the running daemon state.

Question 717

You are responsible for a test RHEL10 instance. The required hands-on outcome is: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. Select the most appropriate implementation step.

  1. Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot.
  2. Define the appropriate persistent fcontext mapping with `semanage fcontext` and reapply it using `restorecon`.
  3. Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.
  4. Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed.

Explanation

Correct Answer

D:

Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed. This directly addresses the lab target: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. The underlying behavior is: Boot-time configuration and current kernel enforcement state are separate values. Verification: Current and configured SELinux modes converge to the intended approved state after reboot.

Incorrect Answers

A:

Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot. This is an appropriate step for a DIFFERENT exercise, specifically: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. It does not address the required lab state, whose mechanism is: Boot-time configuration and current kernel enforcement state are separate values.

B:

Define the appropriate persistent fcontext mapping with `semanage fcontext` and reapply it using `restorecon`. This is an appropriate step for a DIFFERENT exercise, specifically: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. It does not address the required lab state, whose mechanism is: Boot-time configuration and current kernel enforcement state are separate values.

C:

Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload. This is an appropriate step for a DIFFERENT exercise, specifically: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. It does not address the required lab state, whose mechanism is: Boot-time configuration and current kernel enforcement state are separate values.

Question 718

After a lab configuration change, verify: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. Which result most directly proves the desired system state?

  1. Current and configured SELinux modes converge to the intended approved state after reboot.
  2. SELinux context inspection shows read-only content separately from write-capable uploads and the application functions.
  3. `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.
  4. `getsebool` reports on after reboot and the documented DB connection test succeeds.

Explanation

Correct Answer

A:

Current and configured SELinux modes converge to the intended approved state after reboot. This check confirms the expected effect of: Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed. It distinguishes the intended result from the original failure mechanism: Boot-time configuration and current kernel enforcement state are separate values.

Incorrect Answers

B:

SELinux context inspection shows read-only content separately from write-capable uploads and the application functions. That verifies a separate lab task: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. It does not validate the implementation required here: Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed.

C:

`stat` reports expected modes and the user's valid SSH connection works without insecure key exposure. That verifies a separate lab task: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. It does not validate the implementation required here: Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed.

D:

`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: Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed.

Question 719

In an EX200-style practice lab, this condition exists: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. Which explanation correctly identifies the underlying issue?

  1. Port type modifications and adding new mappings are different policy operations.
  2. Boot-time configuration and current kernel enforcement state are separate values.
  3. A running SSH daemon does not imply any given user/key is authorized.
  4. SSH authentication methods are enforced by sshd configuration and authorized key material.

Explanation

Correct Answer

B:

Boot-time configuration and current kernel enforcement state are separate values. This explains the task's initial state: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. The supported lab action is: Use `sestatus` to compare current and configured modes, then follow approved immediate `setenforce` and reboot procedures as needed.

Incorrect Answers

A:

Port type modifications and adding new mappings are different policy operations. This mechanism applies to another scenario: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. The given lab state instead requires the more specific cause in the correct choice.

C:

A running SSH daemon does not imply any given user/key is authorized. This mechanism applies to another scenario: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. The given lab state instead requires the more specific cause in the correct choice.

D:

SSH authentication methods are enforced by sshd configuration and authorized key material. This mechanism applies to another scenario: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. The given lab state instead requires the more specific cause in the correct choice.

Question 720

After completing this practical task on a test RHEL10 instance: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. Which operational safeguard helps keep the result correct and safe?

  1. Reapply default file contexts after moving service data into standard labeled directories.
  2. Test positive and negative access after SSH authorization changes.
  3. Record both fields in security posture checks and require a reboot verification for boot setting changes.
  4. Use persistent Boolean changes only when justified and test their effects after restart.

Explanation

Correct Answer

C:

Record both fields in security posture checks and require a reboot verification for boot setting changes. This guards against recurrence of: Boot-time configuration and current kernel enforcement state are separate values. Confirm the lab's final state by: Current and configured SELinux modes converge to the intended approved state after reboot.

Incorrect Answers

A:

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: Boot-time configuration and current kernel enforcement state are separate values.

B:

Test positive and negative access after SSH authorization changes. That control is best suited to a separate scenario: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. It is not the best safeguard for the current mechanism: Boot-time configuration and current kernel enforcement state are separate values.

D:

Use persistent Boolean changes only when justified and test their effects after restart. That control is best suited to a separate scenario: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. It is not the best safeguard for the current mechanism: Boot-time configuration and current kernel enforcement state are separate values.