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 68

Question 670

After a lab configuration change, verify: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. Which result most directly proves the desired system state?

  1. The host restarts cleanly, and journal boot IDs show the new boot.
  2. The VM reaches its powered-off state rather than returning to login after restart.
  3. After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries.
  4. `systemctl get-default` reports `multi-user.target`, including after reboot.

Explanation

Correct Answer

A:

The host restarts cleanly, and journal boot IDs show the new boot. This check confirms the expected effect of: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes. It distinguishes the intended result from the original failure mechanism: An orderly reboot coordinates service shutdown and filesystem synchronization.

Incorrect Answers

B:

The VM reaches its powered-off state rather than returning to login after restart. That verifies a separate lab task: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. It does not validate the implementation required here: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.

C:

After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries. That verifies a separate lab task: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. It does not validate the implementation required here: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.

D:

`systemctl get-default` reports `multi-user.target`, including after reboot. That verifies a separate lab task: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. It does not validate the implementation required here: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.

Question 671

In an EX200-style practice lab, this condition exists: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. Which explanation correctly identifies the underlying issue?

  1. Boot interruption changes early startup context and password recovery may require filesystem relabeling.
  2. An orderly reboot coordinates service shutdown and filesystem synchronization.
  3. Journal filters separate source, boot and priority, whereas unfiltered logs mix unrelated events.
  4. Service enablement controls boot dependencies; it does not establish successful execution.

Explanation

Correct Answer

B:

An orderly reboot coordinates service shutdown and filesystem synchronization. This explains the task's initial state: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. The supported lab action is: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.

Incorrect Answers

A:

Boot interruption changes early startup context and password recovery may require filesystem relabeling. This mechanism applies to another scenario: An administrator forgot an isolated training VM's root password and is asked to restore authorized console access. The given lab state instead requires the more specific cause in the correct choice.

C:

Journal filters separate source, boot and priority, whereas unfiltered logs mix unrelated events. This mechanism applies to another scenario: A system journal contains many warnings and the student must isolate kernel-related messages for the current boot. The given lab state instead requires the more specific cause in the correct choice.

D:

Service enablement controls boot dependencies; it does not establish successful execution. This mechanism applies to another scenario: An application service fails to start but an administrator looks only at its unit's enabled state. The given lab state instead requires the more specific cause in the correct choice.

Question 672

After completing this practical task on a test RHEL10 instance: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. Which operational safeguard helps keep the result correct and safe?

  1. Collect evidence and identify process ownership before choosing a corrective signal.
  2. Use precise filters in incident collection to retain reproducible evidence.
  3. Document reboot windows and verify core services after startup.
  4. Perform a manager reload for unit-file changes, separate from daemon application reloads.

Explanation

Correct Answer

C:

Document reboot windows and verify core services after startup. This guards against recurrence of: An orderly reboot coordinates service shutdown and filesystem synchronization. Confirm the lab's final state by: The host restarts cleanly, and journal boot IDs show the new boot.

Incorrect Answers

A:

Collect evidence and identify process ownership before choosing a corrective signal. That control is best suited to a separate scenario: The training server is slow, and a student wants to identify the CPU-intensive process before killing anything. It is not the best safeguard for the current mechanism: An orderly reboot coordinates service shutdown and filesystem synchronization.

B:

Use precise filters in incident collection to retain reproducible evidence. That control is best suited to a separate scenario: A system journal contains many warnings and the student must isolate kernel-related messages for the current boot. It is not the best safeguard for the current mechanism: An orderly reboot coordinates service shutdown and filesystem synchronization.

D:

Perform a manager reload for unit-file changes, separate from daemon application reloads. That control is best suited to a separate scenario: A unit file for a custom service is edited directly under `/etc/systemd/system`, but systemd continues using the old unit definition. It is not the best safeguard for the current mechanism: An orderly reboot coordinates service shutdown and filesystem synchronization.

Question 673

Lab exercise on an isolated enterprise lab VM: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again.
  2. Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG.
  3. Run `pvmove` only if extents need migration, then `vgreduce vg_training /dev/vdd1` after verifying PV free status.
  4. Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`.

Explanation

Correct Answer

A:

Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again. This directly addresses the lab target: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. The underlying behavior is: An LV can grow only from free physical extents available in its volume group. Verification: The volume group reports sufficient free extents before the successful resize.

Incorrect Answers

B:

Use `lvcreate -l 20%FREE -n lv_scratch vg_training` only in the disposable VG. This is an appropriate step for a DIFFERENT exercise, specifically: An LV should consume precisely 20% of remaining free extents for a training scratch workload. It does not address the required lab state, whose mechanism is: An LV can grow only from free physical extents available in its volume group.

C:

Run `pvmove` only if extents need migration, then `vgreduce vg_training /dev/vdd1` after verifying PV free status. This is an appropriate step for a DIFFERENT exercise, specifically: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. It does not address the required lab state, whose mechanism is: An LV can grow only from free physical extents available in its volume group.

D:

Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`. This is an appropriate step for a DIFFERENT exercise, specifically: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. It does not address the required lab state, whose mechanism is: An LV can grow only from free physical extents available in its volume group.

Question 674

In a hands-on RHCSA practice VM, the assigned outcome was: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. What specific verification would demonstrate the target state?

  1. `lvs /dev/vg_training/lv_db` reports the requested LV and does not show a filesystem automatically.
  2. The volume group reports sufficient free extents before the successful resize.
  3. `pvs /dev/vdb1` shows a physical volume and no other disk was initialized.
  4. `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.

Explanation

Correct Answer

B:

The volume group reports sufficient free extents before the successful resize. This check confirms the expected effect of: Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again. It distinguishes the intended result from the original failure mechanism: An LV can grow only from free physical extents available in its volume group.

Incorrect Answers

A:

`lvs /dev/vg_training/lv_db` reports the requested LV and does not show a filesystem automatically. That verifies a separate lab task: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It does not validate the implementation required here: Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again.

C:

`pvs /dev/vdb1` shows a physical volume and no other disk was initialized. That verifies a separate lab task: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. It does not validate the implementation required here: Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again.

D:

`lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth. That verifies a separate lab task: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. It does not validate the implementation required here: Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again.

Question 675

A trainee is diagnosing: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. Which root cause should they recognize before changing the system?

  1. Kernel-assigned block device names may shift, whereas filesystem UUIDs identify the intended volume.
  2. `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.
  3. An LV can grow only from free physical extents available in its volume group.
  4. LVM volume names hide physical extent mapping that matters during disk replacement.

Explanation

Correct Answer

C:

An LV can grow only from free physical extents available in its volume group. This explains the task's initial state: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. The supported lab action is: Check `vgs -o vg_name,vg_free` and add approved PV capacity before attempting the growth again.

Incorrect Answers

A:

Kernel-assigned block device names may shift, whereas filesystem UUIDs identify the intended volume. This mechanism applies to another scenario: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. The given lab state instead requires the more specific cause in the correct choice.

B:

`-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. This mechanism applies to another scenario: An LV should consume precisely 20% of remaining free extents for a training scratch workload. The given lab state instead requires the more specific cause in the correct choice.

D:

LVM volume names hide physical extent mapping that matters during disk replacement. This mechanism applies to another scenario: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. The given lab state instead requires the more specific cause in the correct choice.

Question 676

For this Linux administration lab: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. Which safety and lifecycle check best prevents the same problem returning?

  1. Require a signed disk-to-VM inventory and backup review before changing partition tables.
  2. Document whether requests are byte sizes or extents before provisioning LVM.
  3. Plan allocations with PV placement requirements as well as aggregate capacity.
  4. Monitor free-extents capacity and set thresholds before service expansion.

Explanation

Correct Answer

D:

Monitor free-extents capacity and set thresholds before service expansion. This guards against recurrence of: An LV can grow only from free physical extents available in its volume group. Confirm the lab's final state by: The volume group reports sufficient free extents before the successful resize.

Incorrect Answers

A:

Require a signed disk-to-VM inventory and backup review before changing partition tables. That control is best suited to a separate scenario: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. It is not the best safeguard for the current mechanism: An LV can grow only from free physical extents available in its volume group.

B:

Document whether requests are byte sizes or extents before provisioning LVM. That control is best suited to a separate scenario: An LV should consume precisely 20% of remaining free extents for a training scratch workload. It is not the best safeguard for the current mechanism: An LV can grow only from free physical extents available in its volume group.

C:

Plan allocations with PV placement requirements as well as aggregate capacity. That control is best suited to a separate scenario: A training PV reports little free space while its VG appears to have ample total capacity across a second PV. It is not the best safeguard for the current mechanism: An LV can grow only from free physical extents available in its volume group.

Question 677

A student working on a disposable RHEL10 training node receives this assignment: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. Which answer gives the correct practical approach?

  1. After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online.
  2. Use an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory.
  3. Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.
  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

B:

Use an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory. This directly addresses the lab target: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. The underlying behavior is: The sticky bit constrains unlink and rename in a shared writable directory. Verification: Two test users can create files but one cannot remove the other's file without applicable privilege.

Incorrect Answers

A:

After checking the mounted filesystem, run `xfs_growfs /srv/archive` to grow the XFS filesystem online. This is an appropriate step for a DIFFERENT exercise, specifically: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. It does not address the required lab state, whose mechanism is: The sticky bit constrains unlink and rename in a shared writable directory.

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: The sticky bit constrains unlink and rename in a shared writable directory.

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 is an appropriate step for a DIFFERENT exercise, specifically: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. It does not address the required lab state, whose mechanism is: The sticky bit constrains unlink and rename in a shared writable directory.

Question 678

You have attempted this task on a disposable RHEL10 training node: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. Which command output or observation best confirms its success?

  1. The mount options show `rw` and a controlled authorized file creation succeeds.
  2. A request to the mapped directory resolves the updated server export without reusing the stale path.
  3. Two test users can create files but one cannot remove the other's file without applicable privilege.
  4. `blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID.

Explanation

Correct Answer

C:

Two test users can create files but one cannot remove the other's file without applicable privilege. This check confirms the expected effect of: Use an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory. It distinguishes the intended result from the original failure mechanism: The sticky bit constrains unlink and rename in a shared writable directory.

Incorrect Answers

A:

The mount options show `rw` and a controlled authorized file creation succeeds. That verifies a separate lab task: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. It does not validate the implementation required here: Use an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory.

B:

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 an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory.

D:

`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: Use an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory.

Question 679

Troubleshoot the following RHEL 10 lab situation: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. Identify the key Linux mechanism behind the issue.

  1. ext4 filesystem capacity has a separate resize operation from LVM block capacity.
  2. All parent directory traversal permissions and file modes affect effective access.
  3. Formatting creates filesystem metadata and overwrites the previous block contents.
  4. The sticky bit constrains unlink and rename in a shared writable directory.

Explanation

Correct Answer

D:

The sticky bit constrains unlink and rename in a shared writable directory. This explains the task's initial state: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. The supported lab action is: Use an appropriate `chmod 1777 /srv/lab-tmp` only for the approved disposable shared scratch directory.

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:

All parent directory traversal permissions and file modes affect effective access. This mechanism applies to another scenario: 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. 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 680

Following lab verification, document the preventive or persistence-oriented procedure for: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. Which practice is most suitable?

  1. Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area.
  2. Use consistent UID/GID mapping and least-privilege export settings.
  3. Validate map syntax and restart/enable autofs after controlled changes.
  4. Include filesystem shrink capability in capacity design decisions before provisioning.

Explanation

Correct Answer

A:

Use a sticky bit and cleanup policy on any intentionally shared writeable scratch area. This guards against recurrence of: The sticky bit constrains unlink and rename in a shared writable directory. Confirm the lab's final state by: Two test users can create files but one cannot remove the other's file without applicable privilege.

Incorrect Answers

B:

Use consistent UID/GID mapping and least-privilege export settings. That control is best suited to a separate scenario: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. It is not the best safeguard for the current mechanism: The sticky bit constrains unlink and rename in a shared writable directory.

C:

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: The sticky bit constrains unlink and rename in a shared writable directory.

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: The sticky bit constrains unlink and rename in a shared writable directory.