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 55

Question 540

A student has implemented the following configuration: A previously working swap LV disappears after restart because no persistent swap entry was configured. What repeatable control best reduces regressions or unsafe changes?

  1. Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot.
  2. Audit swap entries and device UUIDs after storage migrations.
  3. Record PV mapping before hardware maintenance and always verify device identification.
  4. Track approved PV additions in capacity records and test before growing filesystems.

Explanation

Correct Answer

B:

Audit swap entries and device UUIDs after storage migrations. This guards against recurrence of: `swapon` applies at runtime but does not automatically create persistent boot activation. Confirm the lab's final state by: `swapon --show` lists the LV after controlled reboot and `findmnt --verify` finds no fstab error.

Incorrect Answers

A:

Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot. That control is best suited to a separate scenario: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.

C:

Record PV mapping before hardware maintenance and always verify device identification. That control is best suited to a separate scenario: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.

D:

Track approved PV additions in capacity records and test before growing filesystems. That control is best suited to a separate scenario: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. It is not the best safeguard for the current mechanism: `swapon` applies at runtime but does not automatically create persistent boot activation.

Question 541

You are responsible for a local virtualization classroom. The required hands-on outcome is: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. Select the most appropriate implementation step.

  1. Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported.
  2. Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.
  3. Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.
  4. Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.

Explanation

Correct Answer

D:

Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts. This directly addresses the lab target: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. The underlying behavior is: XFS on RHEL 10 supports growth but does not support shrinking. Verification: The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted.

Incorrect Answers

A:

Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported. This is an appropriate step for a DIFFERENT exercise, specifically: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. It does not address the required lab state, whose mechanism is: XFS on RHEL 10 supports growth but does not support shrinking.

B:

Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`. This is an appropriate step for a DIFFERENT exercise, specifically: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. It does not address the required lab state, whose mechanism is: XFS on RHEL 10 supports growth but does not support shrinking.

C:

Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`. This is an appropriate step for a DIFFERENT exercise, specifically: A student tries to unmount an NFS training mount while another process has its current directory inside it. It does not address the required lab state, whose mechanism is: XFS on RHEL 10 supports growth but does not support shrinking.

Question 542

After a lab configuration change, verify: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. Which result most directly proves the desired system state?

  1. The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted.
  2. The mount options show `rw` and a controlled authorized file creation succeeds.
  3. `findmnt /mnt/team` reports an NFS mount and a permitted test file is readable.
  4. `blkid /dev/vdd1` identifies `TYPE="vfat"` and the intended test host mounts it successfully.

Explanation

Correct Answer

A:

The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted. This check confirms the expected effect of: Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts. It distinguishes the intended result from the original failure mechanism: XFS on RHEL 10 supports growth but does not support shrinking.

Incorrect Answers

B:

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: Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.

C:

`findmnt /mnt/team` reports an NFS mount and a permitted test file is readable. That verifies a separate lab task: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. It does not validate the implementation required here: Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.

D:

`blkid /dev/vdd1` identifies `TYPE="vfat"` and the intended test host mounts it successfully. That verifies a separate lab task: A USB-compatible training partition must use the VFAT filesystem, but the operator formats it as XFS instead. It does not validate the implementation required here: Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.

Question 543

In an EX200-style practice lab, this condition exists: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. Which explanation correctly identifies the underlying issue?

  1. NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.
  2. XFS on RHEL 10 supports growth but does not support shrinking.
  3. Runtime mounting does not automatically write persistent boot mount configuration.
  4. Filesystem presence alone does not attach it into the directory namespace.

Explanation

Correct Answer

B:

XFS on RHEL 10 supports growth but does not support shrinking. This explains the task's initial state: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. The supported lab action is: Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.

Incorrect Answers

A:

NFS access depends on remote export policy and identity mapping in addition to client-side mode bits. This mechanism applies to another scenario: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. The given lab state instead requires the more specific cause in the correct choice.

C:

Runtime mounting does not automatically write persistent boot mount configuration. This mechanism applies to another scenario: A static XFS mount works when issued manually but vanishes after every reboot. The given lab state instead requires the more specific cause in the correct choice.

D:

Filesystem presence alone does not attach it into the directory namespace. This mechanism applies to another scenario: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. The given lab state instead requires the more specific cause in the correct choice.

Question 544

After completing this practical task on a local virtualization classroom: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. Which operational safeguard helps keep the result correct and safe?

  1. Check effective mount flags before broadly changing ownership or file modes.
  2. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.
  3. Include filesystem shrink capability in capacity design decisions before provisioning.
  4. Use stable identifiers and run `findmnt --verify` before rebooting.

Explanation

Correct Answer

C:

Include filesystem shrink capability in capacity design decisions before provisioning. This guards against recurrence of: XFS on RHEL 10 supports growth but does not support shrinking. Confirm the lab's final state by: The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted.

Incorrect Answers

A:

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: XFS on RHEL 10 supports growth but does not support shrinking.

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: XFS on RHEL 10 supports growth but does not support shrinking.

D:

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: XFS on RHEL 10 supports growth but does not support shrinking.

Question 545

Lab exercise on a nonproduction Linux administration sandbox: A new custom service has an `ExecStart` path that no longer exists after the application was moved. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely.
  2. Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.
  3. Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.
  4. Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.

Explanation

Correct Answer

A:

Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely. This directly addresses the lab target: A new custom service has an `ExecStart` path that no longer exists after the application was moved. The underlying behavior is: Systemd cannot start a unit whose configured executable is absent. Verification: `systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path.

Incorrect Answers

B:

Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized. This is an appropriate step for a DIFFERENT exercise, specifically: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. It does not address the required lab state, whose mechanism is: Systemd cannot start a unit whose configured executable is absent.

C:

Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate. This is an appropriate step for a DIFFERENT exercise, specifically: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. It does not address the required lab state, whose mechanism is: Systemd cannot start a unit whose configured executable is absent.

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: Systemd cannot start a unit whose configured executable is absent.

Question 546

In a hands-on RHCSA practice VM, the assigned outcome was: A new custom service has an `ExecStart` path that no longer exists after the application was moved. What specific verification would demonstrate the target state?

  1. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.
  2. `systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path.
  3. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.
  4. `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.

Explanation

Correct Answer

B:

`systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path. This check confirms the expected effect of: Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely. It distinguishes the intended result from the original failure mechanism: Systemd cannot start a unit whose configured executable is absent.

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: Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely.

C:

`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: Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely.

D:

`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: Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely.

Question 547

A trainee is diagnosing: A new custom service has an `ExecStart` path that no longer exists after the application was moved. Which root cause should they recognize before changing the system?

  1. An `at` job is one-shot, unlike a recurring cron schedule.
  2. A timer schedules activation of a corresponding service unit rather than executing arbitrary shell code by itself.
  3. Systemd cannot start a unit whose configured executable is absent.
  4. A scheduled job executes with the identity of the scheduler's configured user.

Explanation

Correct Answer

C:

Systemd cannot start a unit whose configured executable is absent. This explains the task's initial state: A new custom service has an `ExecStart` path that no longer exists after the application was moved. The supported lab action is: Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely.

Incorrect Answers

A:

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.

B:

A timer schedules activation of a corresponding service unit rather than executing arbitrary shell code by itself. This mechanism applies to another scenario: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. The given lab state instead requires the more specific cause in the correct choice.

D:

A scheduled job executes with the identity of the scheduler's configured user. This mechanism applies to another scenario: 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. The given lab state instead requires the more specific cause in the correct choice.

Question 548

For this Linux administration lab: A new custom service has an `ExecStart` path that no longer exists after the application was moved. Which safety and lifecycle check best prevents the same problem returning?

  1. Verify the queue and remove obsolete tasks with `atrm` before the execution time.
  2. Maintain approved time servers and monitor drift/offset after network changes.
  3. Document persistent default target configuration separately from runtime target switching.
  4. Review executable paths and file ownership as part of service deployment testing.

Explanation

Correct Answer

D:

Review executable paths and file ownership as part of service deployment testing. This guards against recurrence of: Systemd cannot start a unit whose configured executable is absent. Confirm the lab's final state by: `systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path.

Incorrect Answers

A:

Verify the queue and remove obsolete tasks with `atrm` before the execution time. That control is best suited to a separate scenario: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. It is not the best safeguard for the current mechanism: Systemd cannot start a unit whose configured executable is absent.

B:

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: Systemd cannot start a unit whose configured executable is absent.

C:

Document persistent default target configuration separately from runtime target switching. That control is best suited to a separate scenario: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. It is not the best safeguard for the current mechanism: Systemd cannot start a unit whose configured executable is absent.

Question 549

A student working on a test RHEL10 instance receives this assignment: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. Which answer gives the correct practical approach?

  1. Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.
  2. Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.
  3. Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.
  4. Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

Explanation

Correct Answer

B:

Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope. This directly addresses the lab target: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. The underlying behavior is: NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary. Verification: The profile reflects changed settings and existing remote management remains recoverable.

Incorrect Answers

A:

Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall. This is an appropriate step for a DIFFERENT exercise, specifically: A service listens on port 8443 but clients are blocked by the active public firewalld zone. It does not address the required lab state, whose mechanism is: NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary.

C:

Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally. This is an appropriate step for a DIFFERENT exercise, specifically: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It does not address the required lab state, whose mechanism is: NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary.

D:

Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured. This is an appropriate step for a DIFFERENT exercise, specifically: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It does not address the required lab state, whose mechanism is: NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary.

Question 550

You have attempted this task on a test RHEL10 instance: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. Which command output or observation best confirms its success?

  1. `nmcli dev show` and `getent hosts server.lab` show the approved DNS servers and expected name resolution.
  2. The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled.
  3. The profile reflects changed settings and existing remote management remains recoverable.
  4. The port remains listed in permanent configuration and works after a controlled reboot.

Explanation

Correct Answer

C:

The profile reflects changed settings and existing remote management remains recoverable. This check confirms the expected effect of: Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope. It distinguishes the intended result from the original failure mechanism: NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary.

Incorrect Answers

A:

`nmcli dev show` and `getent hosts server.lab` show the approved DNS servers and expected name resolution. That verifies a separate lab task: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. It does not validate the implementation required here: Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.

B:

The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled. That verifies a separate lab task: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It does not validate the implementation required here: Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.

D:

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: Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.