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 65

Question 640

After completing this practical task on a local virtualization classroom: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. Which operational safeguard helps keep the result correct and safe?

  1. Trend memory and paging activity together under representative workload.
  2. Use precise filters in incident collection to retain reproducible evidence.
  3. Include explicit action and target hostname in approved shutdown runbooks.
  4. Include validation, supported reload or restart, and functional checks in deployment procedures.

Explanation

Correct Answer

C:

Include explicit action and target hostname in approved shutdown runbooks. This guards against recurrence of: Poweroff and reboot invoke different system state transitions. Confirm the lab's final state by: The VM reaches its powered-off state rather than returning to login after restart.

Incorrect Answers

A:

Trend memory and paging activity together under representative workload. That control is best suited to a separate scenario: A running VM has adequate memory by `free -h` but swap usage spikes and the team assumes the application is leaking. It is not the best safeguard for the current mechanism: Poweroff and reboot invoke different system state transitions.

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: Poweroff and reboot invoke different system state transitions.

D:

Include validation, supported reload or restart, and functional checks in deployment procedures. That control is best suited to a separate scenario: An application configuration was changed on disk, but the running daemon still uses the previous settings. It is not the best safeguard for the current mechanism: Poweroff and reboot invoke different system state transitions.

Question 641

Lab exercise on a nonproduction Linux administration sandbox: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`.
  2. Use `lsblk -f` plus `lvs` and `findmnt` to resolve which block layer currently backs `/srv/db`.
  3. Unmount the disposable LV's filesystem, verify `findmnt` and active holders, then use `lvremove /dev/vg_training/lv_tmp` with review.
  4. Use `lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS`, `blkid`, and the lab inventory to identify the designated empty `/dev/vdb`.

Explanation

Correct Answer

A:

Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`. This directly addresses the lab target: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. The underlying behavior is: LVM volume names hide physical extent mapping that matters during disk replacement. Verification: The report lists the actual PV paths and their group membership for the target LV.

Incorrect Answers

B:

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: LVM volume names hide physical extent mapping that matters during disk replacement.

C:

Unmount the disposable LV's filesystem, verify `findmnt` and active holders, then use `lvremove /dev/vg_training/lv_tmp` with review. This is an appropriate step for a DIFFERENT exercise, specifically: A test operator removed a block LV without first unmounting it, risking a busy-device error or data loss. It does not address the required lab state, whose mechanism is: LVM volume names hide physical extent mapping that matters during disk replacement.

D:

Use `lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS`, `blkid`, and the lab inventory to identify the designated empty `/dev/vdb`. This is an appropriate step for a DIFFERENT exercise, specifically: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. It does not address the required lab state, whose mechanism is: LVM volume names hide physical extent mapping that matters during disk replacement.

Question 642

In a hands-on RHCSA practice VM, the assigned outcome was: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. What specific verification would demonstrate the target state?

  1. The resulting mapping identifies filesystem to LV to VG to PV without changing data.
  2. The report lists the actual PV paths and their group membership for the target LV.
  3. The expected device appears under the lab inventory ID and no device is formatted during discovery.
  4. `vgs vg_training` displays the total size and `pvs` maps both PVs to the group.

Explanation

Correct Answer

B:

The report lists the actual PV paths and their group membership for the target LV. This check confirms the expected effect of: Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`. It distinguishes the intended result from the original failure mechanism: LVM volume names hide physical extent mapping that matters during disk replacement.

Incorrect Answers

A:

The resulting mapping identifies filesystem to LV to VG to PV without changing data. That verifies a separate lab task: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. It does not validate the implementation required here: Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`.

C:

The expected device appears under the lab inventory ID and no device is formatted during discovery. That verifies a separate lab task: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. It does not validate the implementation required here: Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`.

D:

`vgs vg_training` displays the total size and `pvs` maps both PVs to the group. That verifies a separate lab task: Two fresh disposable LVM partitions must become one storage pool for a new application. It does not validate the implementation required here: Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`.

Question 643

A trainee is diagnosing: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. Which root cause should they recognize before changing the system?

  1. LVM deletion removes logical block storage and must not occur while live mounts depend on it.
  2. GPT initialization replaces the chosen disk's partition metadata.
  3. LVM volume names hide physical extent mapping that matters during disk replacement.
  4. An LVM logical volume is a block device until it is formatted and mounted separately.

Explanation

Correct Answer

C:

LVM volume names hide physical extent mapping that matters during disk replacement. This explains the task's initial state: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. The supported lab action is: Run `lvs -o lv_name,vg_name,devices` and `pvs -o pv_name,vg_name,pv_size,pv_free`.

Incorrect Answers

A:

LVM deletion removes logical block storage and must not occur while live mounts depend on it. This mechanism applies to another scenario: A test operator removed a block LV without first unmounting it, risking a busy-device error or data loss. The given lab state instead requires the more specific cause in the correct choice.

B:

GPT initialization replaces the chosen disk's partition metadata. This mechanism applies to another scenario: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. The given lab state instead requires the more specific cause in the correct choice.

D:

An LVM logical volume is a block device until it is formatted and mounted separately. This mechanism applies to another scenario: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. The given lab state instead requires the more specific cause in the correct choice.

Question 644

For this Linux administration lab: An administrator needs to identify the data-bearing PVs behind an LV without relying on its friendly name. Which safety and lifecycle check best prevents the same problem returning?

  1. Verify final filesystem size and document that XFS supports growth but not shrink.
  2. Check `vgs` free extents before provisioning and keep names consistent with service inventory.
  3. Monitor free-extents capacity and set thresholds before service expansion.
  4. Record PV mapping before hardware maintenance and always verify device identification.

Explanation

Correct Answer

D:

Record PV mapping before hardware maintenance and always verify device identification. This guards against recurrence of: LVM volume names hide physical extent mapping that matters during disk replacement. Confirm the lab's final state by: The report lists the actual PV paths and their group membership for the target LV.

Incorrect Answers

A:

Verify final filesystem size and document that XFS supports growth but not shrink. That control is best suited to a separate scenario: An administrator wants to grow a logical volume and its XFS filesystem together for a disposable data directory. It is not the best safeguard for the current mechanism: LVM volume names hide physical extent mapping that matters during disk replacement.

B:

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: LVM volume names hide physical extent mapping that matters during disk replacement.

C:

Monitor free-extents capacity and set thresholds before service expansion. That control is best suited to a separate scenario: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. It is not the best safeguard for the current mechanism: LVM volume names hide physical extent mapping that matters during disk replacement.

Question 645

A student working on a test RHEL10 instance receives this assignment: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. Which answer gives the correct practical approach?

  1. Use `mkfs.vfat /dev/vdd1` only on the confirmed empty removable lab partition with the appropriate utilities installed.
  2. Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.
  3. Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.
  4. Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration.

Explanation

Correct Answer

B:

Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`. This directly addresses the lab target: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. The underlying behavior is: A directory's setgid bit can cause files and subdirectories to inherit its group. Verification: New files created by team members inherit group `analysts` subject to application and umask settings.

Incorrect Answers

A:

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: A directory's setgid bit can cause files and subdirectories to inherit its group.

C:

Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`. This is an appropriate step for a DIFFERENT exercise, specifically: A student tries to unmount an NFS training mount while another process has its current directory inside it. It does not address the required lab state, whose mechanism is: A directory's setgid bit can cause files and subdirectories to inherit its group.

D:

Inspect `findmnt -T /mnt/team` and correct the NFS source in the authorized mount/automount configuration. This is an appropriate step for a DIFFERENT exercise, specifically: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. It does not address the required lab state, whose mechanism is: A directory's setgid bit can cause files and subdirectories to inherit its group.

Question 646

You have attempted this task on a test RHEL10 instance: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. Which command output or observation best confirms its success?

  1. A simulated server outage does not block the expected system boot and access after recovery mounts normally.
  2. `findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works.
  3. New files created by team members inherit group `analysts` subject to application and umask settings.
  4. A request to the mapped directory resolves the updated server export without reusing the stale path.

Explanation

Correct Answer

C:

New files created by team members inherit group `analysts` subject to application and umask settings. This check confirms the expected effect of: Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`. It distinguishes the intended result from the original failure mechanism: A directory's setgid bit can cause files and subdirectories to inherit its group.

Incorrect Answers

A:

A simulated server outage does not block the expected system boot and access after recovery mounts normally. That verifies a separate lab task: A network share configured in fstab causes a lab host to stall when its NFS server is unavailable during boot. It does not validate the implementation required here: Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.

B:

`findmnt /srv/archive` shows the intended source and `touch /srv/archive/test` works. That verifies a separate lab task: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It does not validate the implementation required here: Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.

D:

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: Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.

Question 647

Troubleshoot the following RHEL 10 lab situation: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. Identify the key Linux mechanism behind the issue.

  1. Autofs configuration changes may need the map service to reload before affecting new mounts.
  2. Autofs mounts configured network resources on access instead of requiring an always-mounted tree.
  3. NFS access depends on remote export policy and identity mapping in addition to client-side mode bits.
  4. A directory's setgid bit can cause files and subdirectories to inherit its group.

Explanation

Correct Answer

D:

A directory's setgid bit can cause files and subdirectories to inherit its group. This explains the task's initial state: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. The supported lab action is: Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.

Incorrect Answers

A:

Autofs configuration changes may need the map service to reload before affecting new mounts. This mechanism applies to another scenario: A new autofs indirect map was edited but clients keep using the previous exported path. The given lab state instead requires the more specific cause in the correct choice.

B:

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.

C:

NFS access depends on remote export policy and identity mapping in addition to client-side mode bits. This mechanism applies to another scenario: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. The given lab state instead requires the more specific cause in the correct choice.

Question 648

Following lab verification, document the preventive or persistence-oriented procedure for: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. Which practice is most suitable?

  1. Verify inherited group and effective permissions in a new-user file creation test.
  2. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.
  3. Never format before confirming the exact blank lab device and backup status.
  4. Include map checks and a fresh access test after changing network home directories.

Explanation

Correct Answer

A:

Verify inherited group and effective permissions in a new-user file creation test. This guards against recurrence of: A directory's setgid bit can cause files and subdirectories to inherit its group. Confirm the lab's final state by: New files created by team members inherit group `analysts` subject to application and umask settings.

Incorrect Answers

B:

Treat fstab modifications as high-impact and test mount behavior while a recovery console is available. That control is best suited to a separate scenario: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It is not the best safeguard for the current mechanism: A directory's setgid bit can cause files and subdirectories to inherit its group.

C:

Never format before confirming the exact blank lab device and backup status. That control is best suited to a separate scenario: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. It is not the best safeguard for the current mechanism: A directory's setgid bit can cause files and subdirectories to inherit its group.

D:

Include map checks and a fresh access test after changing network home directories. That control is best suited to a separate scenario: A new autofs indirect map was edited but clients keep using the previous exported path. It is not the best safeguard for the current mechanism: A directory's setgid bit can cause files and subdirectories to inherit its group.

Question 649

On an isolated enterprise lab VM, perform the following practical task: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. Which action should be carried out after confirming the lab prerequisites?

  1. Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely.
  2. Move the entry into the correct user's crontab using `crontab -u reporter -e` with reviewed file permissions.
  3. Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.
  4. Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.

Explanation

Correct Answer

C:

Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly. This directly addresses the lab target: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. The underlying behavior is: Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS. Verification: After a lab reboot, the boot menu uses the approved timeout and the system still starts normally.

Incorrect Answers

A:

Correct `ExecStart=` in the authorized systemd unit, run `systemctl daemon-reload`, and restart safely. This is an appropriate step for a DIFFERENT exercise, specifically: A new custom service has an `ExecStart` path that no longer exists after the application was moved. It does not address the required lab state, whose mechanism is: Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.

B:

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: Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.

D:

Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized. This is an appropriate step for a DIFFERENT exercise, specifically: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. It does not address the required lab state, whose mechanism is: Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.

Question 650

The lab examiner asks for evidence after this assignment: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. What is the decisive verification step?

  1. After a controlled reboot, the mount is available when the service starts and the application reads its data.
  2. The source list displays the replacement server and offset converges within the intended test tolerance.
  3. `grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`.
  4. After a lab reboot, the boot menu uses the approved timeout and the system still starts normally.

Explanation

Correct Answer

D:

After a lab reboot, the boot menu uses the approved timeout and the system still starts normally. This check confirms the expected effect of: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly. It distinguishes the intended result from the original failure mechanism: Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.

Incorrect Answers

A:

After a controlled reboot, the mount is available when the service starts and the application reads its data. That verifies a separate lab task: A service is enabled and active, but the actual application fails after boot because a required mount is not available in time. It does not validate the implementation required here: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.

B:

The source list displays the replacement server and offset converges within the intended test tolerance. That verifies a separate lab task: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It does not validate the implementation required here: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.

C:

`grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`. That verifies a separate lab task: 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 validate the implementation required here: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.