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 51

Question 500

For this Linux administration lab: A small swap logical volume on a training host is inactive after it has been created. Which safety and lifecycle check best prevents the same problem returning?

  1. Perform non-destructive detection before initializing any storage metadata.
  2. Record PV mapping before hardware maintenance and always verify device identification.
  3. Audit swap entries and device UUIDs after storage migrations.
  4. Record persistent swap configuration separately so availability survives reboot.

Explanation

Correct Answer

D:

Record persistent swap configuration separately so availability survives reboot. This guards against recurrence of: A logical volume is not active swap until formatted with swap metadata and enabled. Confirm the lab's final state by: `swapon --show` lists the intended swap device and `free -h` reflects its capacity.

Incorrect Answers

A:

Perform non-destructive detection before initializing any storage metadata. That control is best suited to a separate scenario: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. It is not the best safeguard for the current mechanism: A logical volume is not active swap until formatted with swap metadata and enabled.

B:

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: A logical volume is not active swap until formatted with swap metadata and enabled.

C:

Audit swap entries and device UUIDs after storage migrations. That control is best suited to a separate scenario: A previously working swap LV disappears after restart because no persistent swap entry was configured. It is not the best safeguard for the current mechanism: A logical volume is not active swap until formatted with swap metadata and enabled.

Question 501

A student working on a test RHEL10 instance receives this assignment: An ext4 training LV was expanded but file capacity remains unchanged. Which answer gives the correct practical approach?

  1. Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.
  2. Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.
  3. Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.
  4. Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported.

Explanation

Correct Answer

B:

Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state. This directly addresses the lab target: An ext4 training LV was expanded but file capacity remains unchanged. The underlying behavior is: ext4 filesystem capacity has a separate resize operation from LVM block capacity. Verification: `df -h /mnt/ext4lab` reflects the newly available capacity.

Incorrect Answers

A:

Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements. This is an appropriate step for a DIFFERENT exercise, specifically: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It does not address the required lab state, whose mechanism is: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

C:

Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`. This is an appropriate step for a DIFFERENT exercise, specifically: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It does not address the required lab state, whose mechanism is: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

D:

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: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

Question 502

You have attempted this task on a test RHEL10 instance: An ext4 training LV was expanded but file capacity remains unchanged. Which command output or observation best confirms its success?

  1. A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data.
  2. A permitted test user writes successfully without using insecure world-writable modes.
  3. `df -h /mnt/ext4lab` reflects the newly available capacity.
  4. `findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works.

Explanation

Correct Answer

C:

`df -h /mnt/ext4lab` reflects the newly available capacity. This check confirms the expected effect of: Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state. It distinguishes the intended result from the original failure mechanism: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

Incorrect Answers

A:

A freshly mounted path shows the new `server2.lab:/exports/team` source and expected sample data. That verifies a separate lab task: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. It does not validate the implementation required here: Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.

B:

A permitted test user writes successfully without using insecure world-writable modes. That verifies a separate lab task: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. It does not validate the implementation required here: Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.

D:

`findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works. That verifies a separate lab task: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It does not validate the implementation required here: Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.

Question 503

Troubleshoot the following RHEL 10 lab situation: An ext4 training LV was expanded but file capacity remains unchanged. Identify the key Linux mechanism behind the issue.

  1. Increasing block-device capacity does not automatically grow the filesystem metadata.
  2. Mount option flags can override normal file permission expectations.
  3. A directory's setgid bit can cause files and subdirectories to inherit its group.
  4. ext4 filesystem capacity has a separate resize operation from LVM block capacity.

Explanation

Correct Answer

D:

ext4 filesystem capacity has a separate resize operation from LVM block capacity. This explains the task's initial state: An ext4 training LV was expanded but file capacity remains unchanged. The supported lab action is: Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.

Incorrect Answers

A:

Increasing block-device capacity does not automatically grow the filesystem metadata. This mechanism applies to another scenario: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. 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 directory's setgid bit can cause files and subdirectories to inherit its group. This mechanism applies to another scenario: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. The given lab state instead requires the more specific cause in the correct choice.

Question 504

Following lab verification, document the preventive or persistence-oriented procedure for: An ext4 training LV was expanded but file capacity remains unchanged. Which practice is most suitable?

  1. Validate filesystem type and correct resizing utility before growing an LV-backed filesystem.
  2. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.
  3. Test boot and reconnect behavior with the NFS server intentionally offline in the lab.
  4. Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area.

Explanation

Correct Answer

A:

Validate filesystem type and correct resizing utility before growing an LV-backed filesystem. This guards against recurrence of: ext4 filesystem capacity has a separate resize operation from LVM block capacity. Confirm the lab's final state by: `df -h /mnt/ext4lab` reflects the newly available capacity.

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: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

C:

Test boot and reconnect behavior with the NFS server intentionally offline in the lab. That control is best suited to a separate scenario: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It is not the best safeguard for the current mechanism: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

D:

Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area. That control is best suited to a separate scenario: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. It is not the best safeguard for the current mechanism: ext4 filesystem capacity has a separate resize operation from LVM block capacity.

Question 505

On an isolated enterprise lab VM, perform the following practical task: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. Which action should be carried out after confirming the lab prerequisites?

  1. Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.
  2. Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference.
  3. Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.
  4. Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.

Explanation

Correct Answer

C:

Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification. This directly addresses the lab target: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. The underlying behavior is: Direct file copying bypasses RPM lifecycle metadata and dependency handling. Verification: `rpm -q lab-package` reports tracked installation and required dependencies.

Incorrect Answers

A:

Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement. This is an appropriate step for a DIFFERENT exercise, specifically: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It does not address the required lab state, whose mechanism is: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

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: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

D:

Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method. This is an appropriate step for a DIFFERENT exercise, specifically: 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 address the required lab state, whose mechanism is: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

Question 506

The lab examiner asks for evidence after this assignment: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. What is the decisive verification step?

  1. The source list displays the replacement server and offset converges within the intended test tolerance.
  2. `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.
  3. The service becomes stable and the journal no longer shows a rapid restart loop.
  4. `rpm -q lab-package` reports tracked installation and required dependencies.

Explanation

Correct Answer

D:

`rpm -q lab-package` reports tracked installation and required dependencies. This check confirms the expected effect of: Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification. It distinguishes the intended result from the original failure mechanism: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

Incorrect Answers

A:

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: Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.

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: Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.

C:

The service becomes stable and the journal no longer shows a rapid restart loop. That verifies a separate lab task: A service starts but restarts endlessly because `Restart=always` masks a broken configuration, filling logs. It does not validate the implementation required here: Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.

Question 507

A training host has this situation: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. Which system behavior best explains the original failure or risk?

  1. Direct file copying bypasses RPM lifecycle metadata and dependency handling.
  2. An `at` job is one-shot, unlike a recurring cron schedule.
  3. Cron evaluates scheduled commands repeatedly according to its five time fields.
  4. Timezone presentation and NTP clock synchronization are different configuration concerns.

Explanation

Correct Answer

A:

Direct file copying bypasses RPM lifecycle metadata and dependency handling. This explains the task's initial state: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. The supported lab action is: Use `dnf install /tmp/lab-package.rpm` with authentic signature and dependency verification.

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:

Cron evaluates scheduled commands repeatedly according to its five time fields. This mechanism applies to another scenario: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. The given lab state instead requires the more specific cause in the correct choice.

D:

Timezone presentation and NTP clock synchronization are different configuration concerns. This mechanism applies to another scenario: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. The given lab state instead requires the more specific cause in the correct choice.

Question 508

A student has implemented the following configuration: A local RPM file exists in the build directory, but a student tries to import its extracted binaries directly into `/usr/bin`. What repeatable control best reduces regressions or unsafe changes?

  1. Test full cold-boot readiness, not just whether a unit says active.
  2. Use managed package installations and maintain a rollbackable version record.
  3. Review timer-to-service linkage and timer state after every deployment.
  4. Record both the configuration file change and observed runtime source.

Explanation

Correct Answer

B:

Use managed package installations and maintain a rollbackable version record. This guards against recurrence of: Direct file copying bypasses RPM lifecycle metadata and dependency handling. Confirm the lab's final state by: `rpm -q lab-package` reports tracked installation and required dependencies.

Incorrect Answers

A:

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: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

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: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

D:

Record both the configuration file change and observed runtime source. That control is best suited to a separate scenario: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It is not the best safeguard for the current mechanism: Direct file copying bypasses RPM lifecycle metadata and dependency handling.

Question 509

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. Select the most appropriate implementation step.

  1. Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.
  2. Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required.
  3. Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.
  4. Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

Explanation

Correct Answer

D:

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 directly addresses the lab target: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. The underlying behavior is: Global zone-wide service allowances are broader than a source-limited access requirement. Verification: A test from the management subnet succeeds and an unauthorized source is denied.

Incorrect Answers

A:

Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope. This is an appropriate step for a DIFFERENT exercise, specifically: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not address the required lab state, whose mechanism is: Global zone-wide service allowances are broader than a source-limited access requirement.

B:

Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required. This is an appropriate step for a DIFFERENT exercise, specifically: An IPv6-only lab application cannot listen because the host connection has no configured static IPv6 address. It does not address the required lab state, whose mechanism is: Global zone-wide service allowances are broader than a source-limited access requirement.

C:

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: Global zone-wide service allowances are broader than a source-limited access requirement.

Question 510

After a lab configuration change, verify: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. Which result most directly proves the desired system state?

  1. A test from the management subnet succeeds and an unauthorized source is denied.
  2. `firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled.
  3. The port remains listed in permanent configuration and works after a controlled reboot.
  4. `firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects.

Explanation

Correct Answer

A:

A test from the management subnet succeeds and an unauthorized source is denied. This check confirms the expected effect of: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally. It distinguishes the intended result from the original failure mechanism: Global zone-wide service allowances are broader than a source-limited access requirement.

Incorrect Answers

B:

`firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled. That verifies a separate lab task: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It does not validate the implementation required here: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

C:

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 an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

D:

`firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects. That verifies a separate lab task: A service listens on port 8443 but clients are blocked by the active public firewalld zone. It does not validate the implementation required here: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.