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 47

Question 460

A student has implemented the following configuration: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. What repeatable control best reduces regressions or unsafe changes?

  1. Perform non-destructive detection before initializing any storage metadata.
  2. Verify extent allocation and redundancy before any VG reduction.
  3. Plan LV resizing and compatible filesystem growth as separate verified steps.
  4. Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot.

Explanation

Correct Answer

B:

Verify extent allocation and redundancy before any VG reduction. This guards against recurrence of: A PV cannot be safely removed from a VG while it still contains required extents. Confirm the lab's final state by: `pvs` shows the retired PV is no longer a member and the VG remains healthy.

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 PV cannot be safely removed from a VG while it still contains required extents.

C:

Plan LV resizing and compatible filesystem growth as separate verified steps. That control is best suited to a separate scenario: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. It is not the best safeguard for the current mechanism: A PV cannot be safely removed from a VG while it still contains required extents.

D:

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: A PV cannot be safely removed from a VG while it still contains required extents.

Question 461

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. Select the most appropriate implementation step.

  1. Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.
  2. Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.
  3. Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.
  4. After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online.

Explanation

Correct Answer

D:

After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online. This directly addresses the lab target: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. The underlying behavior is: Increasing block-device capacity does not automatically grow the filesystem metadata. Verification: `df -h /srv/archive` shows the extra space while `lvs` confirms the same already-expanded LV.

Incorrect Answers

A:

Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports. This is an appropriate step for a DIFFERENT exercise, specifically: A large remote home-directory NFS tree should mount on demand rather than all at login. It does not address the required lab state, whose mechanism is: Increasing block-device capacity does not automatically grow the filesystem metadata.

B:

Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state. This is an appropriate step for a DIFFERENT exercise, specifically: An ext4 training LV was expanded but file capacity remains unchanged. It does not address the required lab state, whose mechanism is: Increasing block-device capacity does not automatically grow the filesystem metadata.

C:

Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission. This is an appropriate step for a DIFFERENT exercise, specifically: A file under `/srv/team` is readable by its owner but inaccessible to the `analysts` group despite the group being listed in the account database. It does not address the required lab state, whose mechanism is: Increasing block-device capacity does not automatically grow the filesystem metadata.

Question 462

After a lab configuration change, verify: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. Which result most directly proves the desired system state?

  1. `df -h /srv/archive` shows the extra space while `lvs` confirms the same already-expanded LV.
  2. `blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID.
  3. After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.
  4. The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted.

Explanation

Correct Answer

A:

`df -h /srv/archive` shows the extra space while `lvs` confirms the same already-expanded LV. This check confirms the expected effect of: After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online. It distinguishes the intended result from the original failure mechanism: Increasing block-device capacity does not automatically grow the filesystem metadata.

Incorrect Answers

B:

`blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID. That verifies a separate lab task: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. It does not validate the implementation required here: After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online.

C:

After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type. That verifies a separate lab task: A static XFS mount works when issued manually but vanishes after every reboot. It does not validate the implementation required here: After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online.

D:

The replacement can be mounted and data verified while no unsupported XFS shrink command is attempted. That verifies a separate lab task: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. It does not validate the implementation required here: After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online.

Question 463

In an EX200-style practice lab, this condition exists: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. Which explanation correctly identifies the underlying issue?

  1. The sticky bit constrains unlink and rename in a shared writable directory.
  2. Increasing block-device capacity does not automatically grow the filesystem metadata.
  3. ext4 filesystem capacity has a separate resize operation from LVM block capacity.
  4. Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

Explanation

Correct Answer

B:

Increasing block-device capacity does not automatically grow the filesystem metadata. This explains the task's initial state: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. The supported lab action is: After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online.

Incorrect Answers

A:

The sticky bit constrains unlink and rename in a shared writable directory. This mechanism applies to another scenario: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. The given lab state instead requires the more specific cause in the correct choice.

C:

ext4 filesystem capacity has a separate resize operation from LVM block capacity. This mechanism applies to another scenario: An ext4 training LV was expanded but file capacity remains unchanged. The given lab state instead requires the more specific cause in the correct choice.

D:

Autofs mounts configured network resources on access instead of requiring an always-mounted tree. This mechanism applies to another scenario: A large remote home-directory NFS tree should mount on demand rather than all at login. The given lab state instead requires the more specific cause in the correct choice.

Question 464

After completing this practical task on a disposable RHEL10 training node: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. Which operational safeguard helps keep the result correct and safe?

  1. Validate map syntax and restart/enable autofs after controlled changes.
  2. Verify server export reachability and intended access controls before persistent NFS configuration.
  3. Perform filesystem-aware resize following every block extension and confirm available bytes.
  4. Verify resolved mount source during network filesystem migrations.

Explanation

Correct Answer

C:

Perform filesystem-aware resize following every block extension and confirm available bytes. This guards against recurrence of: Increasing block-device capacity does not automatically grow the filesystem metadata. Confirm the lab's final state by: `df -h /srv/archive` shows the extra space while `lvs` confirms the same already-expanded LV.

Incorrect Answers

A:

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: Increasing block-device capacity does not automatically grow the filesystem metadata.

B:

Verify server export reachability and intended access controls before persistent NFS configuration. That control is best suited to a separate scenario: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. It is not the best safeguard for the current mechanism: Increasing block-device capacity does not automatically grow the filesystem metadata.

D:

Verify resolved mount source during network filesystem migrations. That control is best suited to a separate scenario: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. It is not the best safeguard for the current mechanism: Increasing block-device capacity does not automatically grow the filesystem metadata.

Question 465

Lab exercise on an offline training clone: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.
  2. Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.
  3. Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.
  4. Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.

Explanation

Correct Answer

A:

Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement. This directly addresses the lab target: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. The underlying behavior is: Subscription entitlement and repository enablement both affect package availability. Verification: The target package's metadata resolves from an entitled supported repository.

Incorrect Answers

B:

Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`. This is an appropriate step for a DIFFERENT exercise, specifically: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. It does not address the required lab state, whose mechanism is: Subscription entitlement and repository enablement both affect package availability.

C:

Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account. This is an appropriate step for a DIFFERENT exercise, specifically: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. It does not address the required lab state, whose mechanism is: Subscription entitlement and repository enablement both affect package availability.

D:

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: Subscription entitlement and repository enablement both affect package availability.

Question 466

In a hands-on RHCSA practice VM, the assigned outcome was: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. What specific verification would demonstrate the target state?

  1. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.
  2. The target package's metadata resolves from an entitled supported repository.
  3. `systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path.
  4. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.

Explanation

Correct Answer

B:

The target package's metadata resolves from an entitled supported repository. This check confirms the expected effect of: Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement. It distinguishes the intended result from the original failure mechanism: Subscription entitlement and repository enablement both affect package availability.

Incorrect Answers

A:

`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: Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.

C:

`systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path. That verifies a separate lab task: A new custom service has an `ExecStart` path that no longer exists after the application was moved. It does not validate the implementation required here: Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.

D:

`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: Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.

Question 467

A trainee is diagnosing: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. Which root cause should they recognize before changing the system?

  1. Systemd service ordering and filesystem availability are separate dependencies.
  2. Service restart policy cannot repair an invalid executable or configuration on its own.
  3. Subscription entitlement and repository enablement both affect package availability.
  4. Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.

Explanation

Correct Answer

C:

Subscription entitlement and repository enablement both affect package availability. This explains the task's initial state: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. The supported lab action is: Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.

Incorrect Answers

A:

Systemd service ordering and filesystem availability are separate dependencies. This mechanism applies to another scenario: A service is enabled and active, but the actual application fails after boot because a required mount is not available in time. The given lab state instead requires the more specific cause in the correct choice.

B:

Service restart policy cannot repair an invalid executable or configuration on its own. This mechanism applies to another scenario: A service starts but restarts endlessly because `Restart=always` masks a broken configuration, filling logs. 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 468

For this Linux administration lab: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. Which safety and lifecycle check best prevents the same problem returning?

  1. Include exact instance names in approval and change audits.
  2. Review timer-to-service linkage and timer state after every deployment.
  3. Review executable paths and file ownership as part of service deployment testing.
  4. Review package source provenance before modifying repository trust policies.

Explanation

Correct Answer

D:

Review package source provenance before modifying repository trust policies. This guards against recurrence of: Subscription entitlement and repository enablement both affect package availability. Confirm the lab's final state by: The target package's metadata resolves from an entitled supported repository.

Incorrect Answers

A:

Include exact instance names in approval and change audits. That control is best suited to a separate scenario: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. It is not the best safeguard for the current mechanism: Subscription entitlement and repository enablement both affect package availability.

B:

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: Subscription entitlement and repository enablement both affect package availability.

C:

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: Subscription entitlement and repository enablement both affect package availability.

Question 469

A student working on a local virtualization classroom receives this assignment: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. Which answer gives the correct practical approach?

  1. Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.
  2. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.
  3. 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`.
  4. Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.

Explanation

Correct Answer

B:

Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. This directly addresses the lab target: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. The underlying behavior is: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default. Verification: An authorized client connects and the correct zone reports the service or port.

Incorrect Answers

A:

Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan. This is an appropriate step for a DIFFERENT exercise, specifically: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not address the required lab state, whose mechanism is: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

C:

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: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

D:

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: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

Question 470

You have attempted this task on a local virtualization classroom: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. Which command output or observation best confirms its success?

  1. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.
  2. The profile reflects changed settings and existing remote management remains recoverable.
  3. An authorized client connects and the correct zone reports the service or port.
  4. A test from the management subnet succeeds and an unauthorized source is denied.

Explanation

Correct Answer

C:

An authorized client connects and the correct zone reports the service or port. This check confirms the expected effect of: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. It distinguishes the intended result from the original failure mechanism: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

Incorrect Answers

A:

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: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

B:

The profile reflects changed settings and existing remote management remains recoverable. That verifies a separate lab task: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not validate the implementation required here: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

D:

A test from the management subnet succeeds and an unauthorized source is denied. That verifies a separate lab task: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It does not validate the implementation required here: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.