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 35

Question 340

For this Linux administration lab: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. Which safety and lifecycle check best prevents the same problem returning?

  1. Confirm exact partition number, holders and backups before partition deletion.
  2. Plan LV resizing and compatible filesystem growth as separate verified steps.
  3. Make disk identification a mandatory gate; never run `mklabel` on a disk with live data.
  4. Track approved PV additions in capacity records and test before growing filesystems.

Explanation

Correct Answer

D:

Track approved PV additions in capacity records and test before growing filesystems. This guards against recurrence of: A volume group does not gain capacity just because a new disk is visible to Linux. Confirm the lab's final state by: `vgs vg_training` reports increased free space and `pvs` shows the new member assigned.

Incorrect Answers

A:

Confirm exact partition number, holders and backups before partition deletion. That control is best suited to a separate scenario: A trainee needs to delete one unused partition on a disposable GPT disk but proposes erasing the whole disk. It is not the best safeguard for the current mechanism: A volume group does not gain capacity just because a new disk is visible to Linux.

B:

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 volume group does not gain capacity just because a new disk is visible to Linux.

C:

Make disk identification a mandatory gate; never run `mklabel` on a disk with live data. That control is best suited to a separate scenario: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. It is not the best safeguard for the current mechanism: A volume group does not gain capacity just because a new disk is visible to Linux.

Question 341

A student working on a disposable RHEL10 training node receives this assignment: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. Which answer gives the correct practical approach?

  1. Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.
  2. Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.
  3. Use `mkfs.vfat /dev/vdd1` only on the confirmed empty removable lab partition with the appropriate utilities installed.
  4. Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV.

Explanation

Correct Answer

B:

Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements. This directly addresses the lab target: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. The underlying behavior is: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy. Verification: A simulated server outage does not block the expected system boot and access after recovery mounts normally.

Incorrect Answers

A:

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: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

C:

Use `mkfs.vfat /dev/vdd1` only on the confirmed empty removable lab partition with the appropriate utilities installed. This is an appropriate step for a DIFFERENT exercise, specifically: A USB-compatible training partition must use the VFAT filesystem, but the operator formats it as XFS instead. It does not address the required lab state, whose mechanism is: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

D:

Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV. This is an appropriate step for a DIFFERENT exercise, specifically: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. It does not address the required lab state, whose mechanism is: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

Question 342

You have attempted this task on a disposable RHEL10 training node: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. Which command output or observation best confirms its success?

  1. A request to the mapped directory resolves the updated server export without reusing the stale path.
  2. The verification returns no invalid-entry errors before the reboot and the mount becomes active.
  3. A simulated server outage does not block the expected system boot and access after recovery mounts normally.
  4. Two test users can create files but one cannot remove the other's file without applicable privilege.

Explanation

Correct Answer

C:

A simulated server outage does not block the expected system boot and access after recovery mounts normally. This check confirms the expected effect of: Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements. It distinguishes the intended result from the original failure mechanism: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

Incorrect Answers

A:

A request to the mapped directory resolves the updated server export without reusing the stale path. That verifies a separate lab task: A new autofs indirect map was edited but clients keep using the previous exported path. It does not validate the implementation required here: Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.

B:

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: Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.

D:

Two test users can create files but one cannot remove the other's file without applicable privilege. That verifies a separate lab task: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. It does not validate the implementation required here: Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.

Question 343

Troubleshoot the following RHEL 10 lab situation: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. Identify the key Linux mechanism behind the issue.

  1. ext4 filesystem capacity has a separate resize operation from LVM block capacity.
  2. Increasing block-device capacity does not automatically grow the filesystem metadata.
  3. Formatting creates filesystem metadata and overwrites the previous block contents.
  4. Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

Explanation

Correct Answer

D:

Remote filesystems depend on network availability and need an appropriate boot-time mount strategy. This explains the task's initial state: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. The supported lab action is: Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.

Incorrect Answers

A:

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.

B:

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.

C:

Formatting creates filesystem metadata and overwrites the previous block contents. This mechanism applies to another scenario: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. The given lab state instead requires the more specific cause in the correct choice.

Question 344

Following lab verification, document the preventive or persistence-oriented procedure for: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. Which practice is most suitable?

  1. Test boot and reconnect behavior with the NFS server intentionally offline in the lab.
  2. Verify resolved mount source during network filesystem migrations.
  3. Validate filesystem type and correct resizing utility before growing an LV-backed filesystem.
  4. Include filesystem shrink capability in capacity design decisions before provisioning.

Explanation

Correct Answer

A:

Test boot and reconnect behavior with the NFS server intentionally offline in the lab. This guards against recurrence of: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy. Confirm the lab's final state by: A simulated server outage does not block the expected system boot and access after recovery mounts normally.

Incorrect Answers

B:

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: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

C:

Validate filesystem type and correct resizing utility before growing an LV-backed filesystem. That control is best suited to a separate scenario: An ext4 training LV was expanded but file capacity remains unchanged. It is not the best safeguard for the current mechanism: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

D:

Include filesystem shrink capability in capacity design decisions before provisioning. That control is best suited to a separate scenario: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. It is not the best safeguard for the current mechanism: Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.

Question 345

On an offline training clone, perform the following practical task: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. Which action should be carried out after confirming the lab prerequisites?

  1. Inspect `grubby --info=ALL` and set the approved kernel default using the supported `grubby --set-default` method.
  2. Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`.
  3. Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.
  4. Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.

Explanation

Correct Answer

C:

Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources. This directly addresses the lab target: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. The underlying behavior is: A running time daemon without valid reachable sources cannot synchronize clocks. Verification: `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.

Incorrect Answers

A:

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: A running time daemon without valid reachable sources cannot synchronize clocks.

B:

Validate the corrected chrony configuration, reload or restart the service as supported, and check `chronyc sources`. This is an appropriate step for a DIFFERENT exercise, specifically: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It does not address the required lab state, whose mechanism is: A running time daemon without valid reachable sources cannot synchronize clocks.

D:

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 running time daemon without valid reachable sources cannot synchronize clocks.

Question 346

The lab examiner asks for evidence after this assignment: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. What is the decisive verification step?

  1. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.
  2. After a lab reboot, the boot menu uses the approved timeout and the system still starts normally.
  3. `systemctl is-enabled lab-cleanup.timer` and `systemctl list-timers` show the active scheduled unit.
  4. `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.

Explanation

Correct Answer

D:

`chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status. This check confirms the expected effect of: Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources. It distinguishes the intended result from the original failure mechanism: A running time daemon without valid reachable sources cannot synchronize clocks.

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: Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.

B:

After a lab reboot, the boot menu uses the approved timeout and the system still starts normally. That verifies a separate lab task: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It does not validate the implementation required here: Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.

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: Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.

Question 347

A training host has this situation: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. Which system behavior best explains the original failure or risk?

  1. A running time daemon without valid reachable sources cannot synchronize clocks.
  2. A timer schedules activation of a corresponding service unit rather than executing arbitrary shell code by itself.
  3. Template unit instance identifiers distinguish multiple managed services.
  4. Cron evaluates scheduled commands repeatedly according to its five time fields.

Explanation

Correct Answer

A:

A running time daemon without valid reachable sources cannot synchronize clocks. This explains the task's initial state: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. The supported lab action is: Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.

Incorrect Answers

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.

C:

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

D:

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.

Question 348

A student has implemented the following configuration: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. What repeatable control best reduces regressions or unsafe changes?

  1. Choose service accounts and privileges deliberately for each recurring job.
  2. Maintain approved time servers and monitor drift/offset after network changes.
  3. Verify the queue and remove obsolete tasks with `atrm` before the execution time.
  4. Use full paths and verify the account's crontab and log capture.

Explanation

Correct Answer

B:

Maintain approved time servers and monitor drift/offset after network changes. This guards against recurrence of: A running time daemon without valid reachable sources cannot synchronize clocks. Confirm the lab's final state by: `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.

Incorrect Answers

A:

Choose service accounts and privileges deliberately for each recurring job. That control is best suited to a separate 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. It is not the best safeguard for the current mechanism: A running time daemon without valid reachable sources cannot synchronize clocks.

C:

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: A running time daemon without valid reachable sources cannot synchronize clocks.

D:

Use full paths and verify the account's crontab and log capture. That control is best suited to a separate scenario: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. It is not the best safeguard for the current mechanism: A running time daemon without valid reachable sources cannot synchronize clocks.

Question 349

You are responsible for a local virtualization classroom. The required hands-on outcome is: A service listens on port 8443 but clients are blocked by the active public firewalld zone. Select the most appropriate implementation step.

  1. Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`.
  2. Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required.
  3. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.
  4. Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.

Explanation

Correct Answer

D:

Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall. This directly addresses the lab target: A service listens on port 8443 but clients are blocked by the active public firewalld zone. The underlying behavior is: Firewalld rules are zone-specific and require persistence for reboot safety. Verification: `firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects.

Incorrect Answers

A:

Configure the desired resolver addresses using `nmcli con mod lablan ipv4.dns '192.0.2.53 192.0.2.54'` and review `ipv4.ignore-auto-dns`. This is an appropriate step for a DIFFERENT exercise, specifically: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. It does not address the required lab state, whose mechanism is: Firewalld rules are zone-specific and require persistence for reboot safety.

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: Firewalld rules are zone-specific and require persistence for reboot safety.

C:

Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. It does not address the required lab state, whose mechanism is: Firewalld rules are zone-specific and require persistence for reboot safety.

Question 350

After a lab configuration change, verify: A service listens on port 8443 but clients are blocked by the active public firewalld zone. Which result most directly proves the desired system state?

  1. `firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects.
  2. `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.
  3. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.
  4. The port remains listed in permanent configuration and works after a controlled reboot.

Explanation

Correct Answer

A:

`firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects. This check confirms the expected effect of: Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall. It distinguishes the intended result from the original failure mechanism: Firewalld rules are zone-specific and require persistence for reboot safety.

Incorrect Answers

B:

`nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway. That verifies a separate lab task: A training host has DHCP IPv4 but requires a fixed address `192.0.2.50/24` and gateway `192.0.2.1` for a private lab subnet. It does not validate the implementation required here: Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.

C:

After reconnect or reboot `nmcli con show` and `ip addr` still report the address. That verifies a separate lab task: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not validate the implementation required here: Use `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.

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 `firewall-cmd --get-active-zones`, then `firewall-cmd --zone=public --add-port=8443/tcp --permanent` and reload the firewall.