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 31

Question 300

A student has implemented the following configuration: An LV should consume precisely 20% of remaining free extents for a training scratch workload. What repeatable control best reduces regressions or unsafe changes?

  1. Check `vgs` free extents before provisioning and keep names consistent with service inventory.
  2. Document whether requests are byte sizes or extents before provisioning LVM.
  3. Verify extent allocation and redundancy before any VG reduction.
  4. Treat unexpected signatures as a stop-and-investigate condition, never automatic wipe permission.

Explanation

Correct Answer

B:

Document whether requests are byte sizes or extents before provisioning LVM. This guards against recurrence of: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. Confirm the lab's final state by: `lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents.

Incorrect Answers

A:

Check `vgs` free extents before provisioning and keep names consistent with service inventory. That control is best suited to a separate scenario: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

C:

Verify extent allocation and redundancy before any VG reduction. That control is best suited to a separate scenario: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

D:

Treat unexpected signatures as a stop-and-investigate condition, never automatic wipe permission. That control is best suited to a separate scenario: A lab disk appears to contain an old filesystem signature after a supposedly blank virtual disk is attached. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.

Question 301

You are responsible for a local virtualization classroom. The required hands-on outcome is: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. Select the most appropriate implementation step.

  1. Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.
  2. Use `resize2fs /dev/vg_training/lv_ext4` after the block-device increase and confirm supported online/offline state.
  3. Use a reviewed appropriate systemd automount or `_netdev`/`nofail` policy for the authorized network mount, matching workload requirements.
  4. Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions.

Explanation

Correct Answer

D:

Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions. This directly addresses the lab target: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. The underlying behavior is: NFS mounting uses a server export path and a compatible network client rather than local disk formatting. Verification: `findmnt /mnt/team` reports an NFS mount and a permitted test file is readable.

Incorrect Answers

A:

Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts. This is an appropriate step for a DIFFERENT exercise, specifically: A junior admin proposes shrinking a mounted XFS filesystem to make room for another LV. It does not address the required lab state, whose mechanism is: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

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: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

C:

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: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

Question 302

After a lab configuration change, verify: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. Which result most directly proves the desired system state?

  1. `findmnt /mnt/team` reports an NFS mount and a permitted test file is readable.
  2. A permitted test user writes successfully without using insecure world-writable modes.
  3. Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map.
  4. New files created by team members inherit group `analysts` subject to application and umask settings.

Explanation

Correct Answer

A:

`findmnt /mnt/team` reports an NFS mount and a permitted test file is readable. This check confirms the expected effect of: Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions. It distinguishes the intended result from the original failure mechanism: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

Incorrect Answers

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: Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions.

C:

Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map. That verifies a separate lab task: A large remote home-directory NFS tree should mount on demand rather than all at login. It does not validate the implementation required here: Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions.

D:

New files created by team members inherit group `analysts` subject to application and umask settings. That verifies a separate lab task: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. It does not validate the implementation required here: Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions.

Question 303

In an EX200-style practice lab, this condition exists: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. Which explanation correctly identifies the underlying issue?

  1. Incorrect persistent mount definitions can delay boot or prevent expected units from activating.
  2. NFS mounting uses a server export path and a compatible network client rather than local disk formatting.
  3. Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.
  4. The sticky bit constrains unlink and rename in a shared writable directory.

Explanation

Correct Answer

B:

NFS mounting uses a server export path and a compatible network client rather than local disk formatting. This explains the task's initial state: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. The supported lab action is: Install the NFS client tools as required and run `mount -t nfs4 server.lab:/exports/team /mnt/team` after verifying hostname and export permissions.

Incorrect Answers

A:

Incorrect persistent mount definitions can delay boot or prevent expected units from activating. This mechanism applies to another scenario: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. The given lab state instead requires the more specific cause in the correct choice.

C:

Remote filesystems depend on network availability and need an appropriate boot-time mount strategy. This mechanism applies to another scenario: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 304

After completing this practical task on a local virtualization classroom: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. Which operational safeguard helps keep the result correct and safe?

  1. Verify resolved mount source during network filesystem migrations.
  2. Configure an appropriate persistent mount separately after runtime testing.
  3. Verify server export reachability and intended access controls before persistent NFS configuration.
  4. Test boot and reconnect behavior with the NFS server intentionally offline in the lab.

Explanation

Correct Answer

C:

Verify server export reachability and intended access controls before persistent NFS configuration. This guards against recurrence of: NFS mounting uses a server export path and a compatible network client rather than local disk formatting. Confirm the lab's final state by: `findmnt /mnt/team` reports an NFS mount and a permitted test file is readable.

Incorrect Answers

A:

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: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

B:

Configure an appropriate persistent mount separately after runtime testing. That control is best suited to a separate scenario: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It is not the best safeguard for the current mechanism: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

D:

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: NFS mounting uses a server export path and a compatible network client rather than local disk formatting.

Question 305

Lab exercise on a nonproduction Linux administration sandbox: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.
  2. Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.
  3. Run `systemctl daemon-reload` and then `systemctl enable --now lab-cleanup.timer` on the lab system.
  4. Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.

Explanation

Correct Answer

A:

Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`. This directly addresses the lab target: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. The underlying behavior is: Isolating an active target does not set the default target for future boots. Verification: A controlled reboot enters the specified default and `get-default` remains consistent.

Incorrect Answers

B:

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: Isolating an active target does not set the default target for future boots.

C:

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: Isolating an active target does not set the default target for future boots.

D:

Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions. This is an appropriate step for a DIFFERENT exercise, specifically: 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 does not address the required lab state, whose mechanism is: Isolating an active target does not set the default target for future boots.

Question 306

In a hands-on RHCSA practice VM, the assigned outcome was: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. 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. A controlled reboot enters the specified default and `get-default` remains consistent.
  3. `systemctl status labapp` reports a live service and `systemctl cat` shows the correct executable path.
  4. `rpm -q packagename` shows the intended version and services are functionally checked after any required restart.

Explanation

Correct Answer

B:

A controlled reboot enters the specified default and `get-default` remains consistent. This check confirms the expected effect of: Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`. It distinguishes the intended result from the original failure mechanism: Isolating an active target does not set the default target for future boots.

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: Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.

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: Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.

D:

`rpm -q packagename` shows the intended version and services are functionally checked after any required restart. That verifies a separate lab task: An RPM package on a training node is stale; the administrator needs to apply approved security updates without reinstalling everything. It does not validate the implementation required here: Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.

Question 307

A trainee is diagnosing: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. Which root cause should they recognize before changing the system?

  1. Runtime activation and boot-time activation are separate systemd states.
  2. Template unit instance identifiers distinguish multiple managed services.
  3. Isolating an active target does not set the default target for future boots.
  4. A scheduled job executes with the identity of the scheduler's configured user.

Explanation

Correct Answer

C:

Isolating an active target does not set the default target for future boots. This explains the task's initial state: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. The supported lab action is: Use `systemctl set-default multi-user.target` and test the new default with `systemctl get-default`.

Incorrect Answers

A:

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

B:

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:

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 308

For this Linux administration lab: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. Which safety and lifecycle check best prevents the same problem returning?

  1. Review package source provenance before modifying repository trust policies.
  2. Verify the queue and remove obsolete tasks with `atrm` before the execution time.
  3. Verify selected kernel and retain a known-good fallback after kernel maintenance.
  4. Document persistent default target configuration separately from runtime target switching.

Explanation

Correct Answer

D:

Document persistent default target configuration separately from runtime target switching. This guards against recurrence of: Isolating an active target does not set the default target for future boots. Confirm the lab's final state by: A controlled reboot enters the specified default and `get-default` remains consistent.

Incorrect Answers

A:

Review package source provenance before modifying repository trust policies. That control is best suited to a separate scenario: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It is not the best safeguard for the current mechanism: Isolating an active target does not set the default target for future boots.

B:

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: Isolating an active target does not set the default target for future boots.

C:

Verify selected kernel and retain a known-good fallback after kernel maintenance. That control is best suited to a separate scenario: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. It is not the best safeguard for the current mechanism: Isolating an active target does not set the default target for future boots.

Question 309

A student working on a test RHEL10 instance receives this assignment: A training host must resolve one intentionally private name without querying DNS while building a disconnected lab. 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. Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM.
  3. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.
  4. Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.

Explanation

Correct Answer

B:

Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM. This directly addresses the lab target: A training host must resolve one intentionally private name without querying DNS while building a disconnected lab. The underlying behavior is: The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`. Verification: `getent hosts db150.lab` resolves the intended IP with DNS disconnected.

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: The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`.

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: The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`.

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: The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`.

Question 310

You have attempted this task on a test RHEL10 instance: A training host must resolve one intentionally private name without querying DNS while building a disconnected lab. Which command output or observation best confirms its success?

  1. `ip -6 addr show` lists the address and a local IPv6 connectivity test succeeds.
  2. `firewall-cmd --zone=public --list-services` contains `http` and only the required service is exposed.
  3. `getent hosts db150.lab` resolves the intended IP with DNS disconnected.
  4. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.

Explanation

Correct Answer

C:

`getent hosts db150.lab` resolves the intended IP with DNS disconnected. This check confirms the expected effect of: Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM. It distinguishes the intended result from the original failure mechanism: The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`.

Incorrect Answers

A:

`ip -6 addr show` lists the address and a local IPv6 connectivity test succeeds. That verifies a separate lab task: An IPv6-only lab application cannot listen because the host connection has no configured static IPv6 address. It does not validate the implementation required here: Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM.

B:

`firewall-cmd --zone=public --list-services` contains `http` and only the required service is exposed. That verifies a separate lab task: A standard `http` service should be allowed through firewalld, but the operator adds a broad arbitrary port range. It does not validate the implementation required here: Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM.

D:

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: Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM.