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 62

Question 610

In a hands-on RHCSA practice VM, the assigned outcome was: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. What specific verification would demonstrate the target state?

  1. The volume group reports sufficient free extents before the successful resize.
  2. The expected device appears under the lab inventory ID and no device is formatted during discovery.
  3. `lvs /dev/vg_training/lv_db` reports the requested LV and does not show a filesystem automatically.
  4. The selected disk has no filesystem, partition or mount dependencies and matches the lab's disk ID.

Explanation

Correct Answer

B:

The expected device appears under the lab inventory ID and no device is formatted during discovery. This check confirms the expected effect of: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation. It distinguishes the intended result from the original failure mechanism: Device discovery and actual filesystem or LVM creation are separate operations.

Incorrect Answers

A:

The volume group reports sufficient free extents before the successful resize. That verifies a separate lab task: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. It does not validate the implementation required here: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.

C:

`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: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.

D:

The selected disk has no filesystem, partition or mount dependencies and matches the lab's disk ID. That verifies a separate lab task: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. It does not validate the implementation required here: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.

Question 611

A trainee is diagnosing: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. Which root cause should they recognize before changing the system?

  1. LVM physical volumes carry metadata that lets volume groups manage underlying extents.
  2. LVM `-r` invokes filesystem resize handling, unlike block-only extension.
  3. Device discovery and actual filesystem or LVM creation are separate operations.
  4. LVM volume names hide physical extent mapping that matters during disk replacement.

Explanation

Correct Answer

C:

Device discovery and actual filesystem or LVM creation are separate operations. This explains the task's initial state: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. The supported lab action is: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.

Incorrect Answers

A:

LVM physical volumes carry metadata that lets volume groups manage underlying extents. This mechanism applies to another scenario: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. The given lab state instead requires the more specific cause in the correct choice.

B:

LVM `-r` invokes filesystem resize handling, unlike block-only extension. This mechanism applies to another scenario: An administrator wants to grow a logical volume and its XFS filesystem together for a disposable data directory. 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 612

For this Linux administration lab: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. Which safety and lifecycle check best prevents the same problem returning?

  1. Test swap capacity and persist the selected UUID in `/etc/fstab` for future boots.
  2. Check `vgs` free extents before provisioning and keep names consistent with service inventory.
  3. Inspect device signatures and mount holders before PV creation.
  4. Perform non-destructive detection before initializing any storage metadata.

Explanation

Correct Answer

D:

Perform non-destructive detection before initializing any storage metadata. This guards against recurrence of: Device discovery and actual filesystem or LVM creation are separate operations. Confirm the lab's final state by: The expected device appears under the lab inventory ID and no device is formatted during discovery.

Incorrect Answers

A:

Test swap capacity and persist the selected UUID in `/etc/fstab` for future boots. That control is best suited to a separate scenario: A VM needs a dedicated 1 GiB swap partition on an explicitly empty GPT training disk instead of an LVM swap LV. It is not the best safeguard for the current mechanism: Device discovery and actual filesystem or LVM creation are separate operations.

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: Device discovery and actual filesystem or LVM creation are separate operations.

C:

Inspect device signatures and mount holders before PV creation. That control is best suited to a separate scenario: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. It is not the best safeguard for the current mechanism: Device discovery and actual filesystem or LVM creation are separate operations.

Question 613

A student working on a local virtualization classroom receives this assignment: 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. Which answer gives the correct practical approach?

  1. Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported.
  2. Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.
  3. Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.
  4. Do not shrink the XFS filesystem; instead plan a supported backup, create a smaller replacement filesystem, restore and switch mounts.

Explanation

Correct Answer

B:

Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission. This directly addresses the lab target: 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 underlying behavior is: All parent directory traversal permissions and file modes affect effective access. Verification: A test member can traverse the path and read the file without permitting unrelated users.

Incorrect Answers

A:

Inspect `findmnt -no OPTIONS /srv/archive`, correct the reviewed mount options and remount safely when supported. This is an appropriate step for a DIFFERENT exercise, specifically: A filesystem was mounted read-only because its fstab options accidentally included `ro`, preventing service writes. It does not address the required lab state, whose mechanism is: All parent directory traversal permissions and file modes affect effective access.

C:

Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`. This is an appropriate step for a DIFFERENT exercise, specifically: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. It does not address the required lab state, whose mechanism is: All parent directory traversal permissions and file modes affect effective access.

D:

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: All parent directory traversal permissions and file modes affect effective access.

Question 614

You have attempted this task on a local virtualization classroom: 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. Which command output or observation best confirms its success?

  1. `blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata.
  2. A simulated server outage does not block the expected system boot and access after recovery mounts normally.
  3. A test member can traverse the path and read the file without permitting unrelated users.
  4. After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.

Explanation

Correct Answer

C:

A test member can traverse the path and read the file without permitting unrelated users. This check confirms the expected effect of: Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission. It distinguishes the intended result from the original failure mechanism: All parent directory traversal permissions and file modes affect effective access.

Incorrect Answers

A:

`blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata. That verifies a separate lab task: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. It does not validate the implementation required here: Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.

B:

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: Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.

D:

After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type. That verifies a separate lab task: A static XFS mount works when issued manually but vanishes after every reboot. It does not validate the implementation required here: Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.

Question 615

Troubleshoot the following RHEL 10 lab situation: 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. Identify the key Linux mechanism behind the issue.

  1. A directory's setgid bit can cause files and subdirectories to inherit its group.
  2. NFS mounting uses a server export path and a compatible network client rather than local disk formatting.
  3. A mountpoint name does not prove which remote host/export currently backs it.
  4. All parent directory traversal permissions and file modes affect effective access.

Explanation

Correct Answer

D:

All parent directory traversal permissions and file modes affect effective access. This explains the task's initial state: 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 supported lab action is: Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.

Incorrect Answers

A:

A directory's setgid bit can cause files and subdirectories to inherit its group. This mechanism applies to another scenario: A directory used for temporary team uploads must grant group access to new files through inherited group ownership. The given lab state instead requires the more specific cause in the correct choice.

B:

NFS mounting uses a server export path and a compatible network client rather than local disk formatting. This mechanism applies to another scenario: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. The given lab state instead requires the more specific cause in the correct choice.

C:

A mountpoint name does not prove which remote host/export currently backs it. This mechanism applies to another scenario: An NFS path is visible under `/mnt/team` but the mount unexpectedly uses an old server export after a migration. The given lab state instead requires the more specific cause in the correct choice.

Question 616

Following lab verification, document the preventive or persistence-oriented procedure for: 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. Which practice is most suitable?

  1. Inspect the entire path before changing only the final file's mode.
  2. Validate map syntax and restart/enable autofs after controlled changes.
  3. Never format before confirming the exact blank lab device and backup status.
  4. Match filesystem selection to task requirements and verify before mounting.

Explanation

Correct Answer

A:

Inspect the entire path before changing only the final file's mode. This guards against recurrence of: All parent directory traversal permissions and file modes affect effective access. Confirm the lab's final state by: A test member can traverse the path and read the file without permitting unrelated users.

Incorrect Answers

B:

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: All parent directory traversal permissions and file modes affect effective access.

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: All parent directory traversal permissions and file modes affect effective access.

D:

Match filesystem selection to task requirements and verify before mounting. That control is best suited to a separate scenario: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. It is not the best safeguard for the current mechanism: All parent directory traversal permissions and file modes affect effective access.

Question 617

On a nonproduction Linux administration sandbox, perform the following practical task: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. 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. Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed.
  3. Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance.
  4. Review systemd `RequiresMountsFor=` or appropriate mount dependencies in the service unit and confirm the filesystem's persistent mount.

Explanation

Correct Answer

C:

Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance. This directly addresses the lab target: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. The underlying behavior is: Template unit instance identifiers distinguish multiple managed services. Verification: `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.

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: Template unit instance identifiers distinguish multiple managed services.

B:

Configure `systemctl enable --now chronyd.service` after checking the service is intended and installed. This is an appropriate step for a DIFFERENT exercise, specifically: A daemon is started manually after package installation but must be reliably available after reboots. It does not address the required lab state, whose mechanism is: Template unit instance identifiers distinguish multiple managed services.

D:

Review systemd `RequiresMountsFor=` or appropriate mount dependencies in the service unit and confirm the filesystem's persistent mount. This is an appropriate step for a DIFFERENT exercise, specifically: 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 address the required lab state, whose mechanism is: Template unit instance identifiers distinguish multiple managed services.

Question 618

The lab examiner asks for evidence after this assignment: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. What is the decisive verification step?

  1. `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.
  2. After a lab reboot, the boot menu uses the approved timeout and the system still starts normally.
  3. The source list displays the replacement server and offset converges within the intended test tolerance.
  4. `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.

Explanation

Correct Answer

D:

`systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged. This check confirms the expected effect of: Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance. It distinguishes the intended result from the original failure mechanism: Template unit instance identifiers distinguish multiple managed services.

Incorrect Answers

A:

`chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status. That verifies a separate lab task: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. It does not validate the implementation required here: Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance.

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: Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance.

C:

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: Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance.

Question 619

A training host has this situation: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. Which system behavior best explains the original failure or risk?

  1. Template unit instance identifiers distinguish multiple managed services.
  2. Writing unit files alone does not start or enable a new timer.
  3. Cron evaluates scheduled commands repeatedly according to its five time fields.
  4. DNF update resolves and records package lifecycle changes through configured repositories.

Explanation

Correct Answer

A:

Template unit instance identifiers distinguish multiple managed services. This explains the task's initial state: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. The supported lab action is: Check `systemctl list-unit-files 'worker@*'` and enable only the intended `worker@blue.service` instance.

Incorrect Answers

B:

Writing unit files alone does not start or enable a new timer. This mechanism applies to another scenario: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. The given lab state instead requires the more specific cause in the correct choice.

C:

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.

D:

DNF update resolves and records package lifecycle changes through configured repositories. This mechanism applies to another scenario: An RPM package on a training node is stale; the administrator needs to apply approved security updates without reinstalling everything. The given lab state instead requires the more specific cause in the correct choice.

Question 620

A student has implemented the following configuration: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. What repeatable control best reduces regressions or unsafe changes?

  1. Verify selected kernel and retain a known-good fallback after kernel maintenance.
  2. Include exact instance names in approval and change audits.
  3. Record firmware mode and test recovery entry after bootloader configuration changes.
  4. Choose service accounts and privileges deliberately for each recurring job.

Explanation

Correct Answer

B:

Include exact instance names in approval and change audits. This guards against recurrence of: Template unit instance identifiers distinguish multiple managed services. Confirm the lab's final state by: `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.

Incorrect Answers

A:

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: Template unit instance identifiers distinguish multiple managed services.

C:

Record firmware mode and test recovery entry after bootloader configuration changes. That control is best suited to a separate scenario: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It is not the best safeguard for the current mechanism: Template unit instance identifiers distinguish multiple managed services.

D:

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: Template unit instance identifiers distinguish multiple managed services.