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 7

Question 60

A student has implemented the following configuration: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. What repeatable control best reduces regressions or unsafe changes?

  1. Audit swap entries and device UUIDs after storage migrations.
  2. Make disk identification a mandatory gate; never run `mklabel` on a disk with live data.
  3. Plan LV resizing and compatible filesystem growth as separate verified steps.
  4. Verify final filesystem size and document that XFS supports growth but not shrink.

Explanation

Correct Answer

B:

Make disk identification a mandatory gate; never run `mklabel` on a disk with live data. This guards against recurrence of: GPT initialization replaces the chosen disk's partition metadata. Confirm the lab's final state by: `parted -s /dev/vdb print` reports `Partition Table: gpt` and existing production disks are unchanged.

Incorrect Answers

A:

Audit swap entries and device UUIDs after storage migrations. That control is best suited to a separate scenario: A previously working swap LV disappears after restart because no persistent swap entry was configured. It is not the best safeguard for the current mechanism: GPT initialization replaces the chosen disk's partition metadata.

C:

Plan LV resizing and compatible filesystem growth as separate verified steps. That control is best suited to a separate scenario: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. It is not the best safeguard for the current mechanism: GPT initialization replaces the chosen disk's partition metadata.

D:

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: GPT initialization replaces the chosen disk's partition metadata.

Question 61

You are responsible for a local virtualization classroom. The required hands-on outcome is: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. Select the most appropriate implementation step.

  1. Use `fuser -vm /mnt/labnfs` or `lsof`, stop the responsible lab process, then `umount /mnt/labnfs`.
  2. Run `automount -m` to inspect effective maps and restart `autofs` safely after correcting `/etc/auto.*` entries.
  3. Use `mkfs.vfat /dev/vdd1` only on the confirmed empty removable lab partition with the appropriate utilities installed.
  4. Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV.

Explanation

Correct Answer

D:

Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV. This directly addresses the lab target: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. The underlying behavior is: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration. Verification: `blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata.

Incorrect Answers

A:

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: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

B:

Run `automount -m` to inspect effective maps and restart `autofs` safely after correcting `/etc/auto.*` entries. This is an appropriate step for a DIFFERENT exercise, specifically: A new autofs indirect map was edited but clients keep using the previous exported path. It does not address the required lab state, whose mechanism is: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

C:

Use `mkfs.vfat /dev/vdd1` only on the confirmed empty removable lab partition with the appropriate utilities installed. This is an appropriate step for a DIFFERENT exercise, specifically: A USB-compatible training partition must use the VFAT filesystem, but the operator formats it as XFS instead. It does not address the required lab state, whose mechanism is: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

Question 62

After a lab configuration change, verify: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. Which result most directly proves the desired system state?

  1. `blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata.
  2. A test member can traverse the path and read the file without permitting unrelated users.
  3. `df -h /srv/archive` shows the extra space while `lvs` confirms the same already-expanded LV.
  4. `df -h /mnt/ext4lab` reflects the newly available capacity.

Explanation

Correct Answer

A:

`blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata. This check confirms the expected effect of: Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV. It distinguishes the intended result from the original failure mechanism: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

Incorrect Answers

B:

A test member can traverse the path and read the file without permitting unrelated users. That verifies a separate lab task: 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 validate the implementation required here: Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV.

C:

`df -h /srv/archive` shows the extra space while `lvs` confirms the same already-expanded LV. That verifies a separate lab task: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. It does not validate the implementation required here: Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV.

D:

`df -h /mnt/ext4lab` reflects the newly available capacity. That verifies a separate lab task: An ext4 training LV was expanded but file capacity remains unchanged. It does not validate the implementation required here: Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV.

Question 63

In an EX200-style practice lab, this condition exists: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. Which explanation correctly identifies the underlying issue?

  1. Remote filesystems depend on network availability and need an appropriate boot-time mount strategy.
  2. XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.
  3. Increasing block-device capacity does not automatically grow the filesystem metadata.
  4. Incorrect persistent mount definitions can delay boot or prevent expected units from activating.

Explanation

Correct Answer

B:

XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration. This explains the task's initial state: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. The supported lab action is: Use `mkfs.ext4 /dev/vg_training/lv_ext4` on the verified empty training LV.

Incorrect Answers

A:

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.

C:

Increasing block-device capacity does not automatically grow the filesystem metadata. This mechanism applies to another scenario: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 64

After completing this practical task on a local virtualization classroom: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. Which operational safeguard helps keep the result correct and safe?

  1. Use consistent UID/GID mapping and least-privilege export settings.
  2. Inspect the entire path before changing only the final file's mode.
  3. Match filesystem selection to task requirements and verify before mounting.
  4. Validate map syntax and restart/enable autofs after controlled changes.

Explanation

Correct Answer

C:

Match filesystem selection to task requirements and verify before mounting. This guards against recurrence of: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration. Confirm the lab's final state by: `blkid` reports `TYPE="ext4"` and `dumpe2fs -h` can inspect ext4 metadata.

Incorrect Answers

A:

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: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

B:

Inspect the entire path before changing only the final file's mode. That control is best suited to a separate 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. It is not the best safeguard for the current mechanism: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

D:

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: XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.

Question 65

Lab exercise on a nonproduction Linux administration sandbox: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.
  2. Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference.
  3. Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.
  4. Review systemd `RequiresMountsFor=` or appropriate mount dependencies in the service unit and confirm the filesystem's persistent mount.

Explanation

Correct Answer

A:

Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account. This directly addresses the lab target: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. The underlying behavior is: Cron evaluates scheduled commands repeatedly according to its five time fields. Verification: `crontab -l` shows the entry and lab logs confirm recurring executions with controlled environment.

Incorrect Answers

B:

Define matching `lab-report.timer` and `lab-report.service` units with an appropriate `OnCalendar` expression and correct `Unit=` reference. This is an appropriate step for a DIFFERENT exercise, specifically: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. It does not address the required lab state, whose mechanism is: Cron evaluates scheduled commands repeatedly according to its five time fields.

C:

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: Cron evaluates scheduled commands repeatedly according to its five time fields.

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: Cron evaluates scheduled commands repeatedly according to its five time fields.

Question 66

In a hands-on RHCSA practice VM, the assigned outcome was: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. What specific verification would demonstrate the target state?

  1. `atq` lists the pending job and the fixture log records one run at the expected time.
  2. `crontab -l` shows the entry and lab logs confirm recurring executions with controlled environment.
  3. `chronyc sources -v` selects the intended time peer and `timedatectl` shows synchronization status.
  4. After a controlled reboot, the mount is available when the service starts and the application reads its data.

Explanation

Correct Answer

B:

`crontab -l` shows the entry and lab logs confirm recurring executions with controlled environment. This check confirms the expected effect of: Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account. It distinguishes the intended result from the original failure mechanism: Cron evaluates scheduled commands repeatedly according to its five time fields.

Incorrect Answers

A:

`atq` lists the pending job and the fixture log records one run at the expected time. That verifies a separate lab task: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. It does not validate the implementation required here: Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.

C:

`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: Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.

D:

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: Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.

Question 67

A trainee is diagnosing: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. Which root cause should they recognize before changing the system?

  1. Template unit instance identifiers distinguish multiple managed services.
  2. The Persistent option handles missed calendar timer events differently from regular cron execution.
  3. Cron evaluates scheduled commands repeatedly according to its five time fields.
  4. Isolating an active target does not set the default target for future boots.

Explanation

Correct Answer

C:

Cron evaluates scheduled commands repeatedly according to its five time fields. This explains the task's initial state: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. The supported lab action is: Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.

Incorrect Answers

A:

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.

B:

The Persistent option handles missed calendar timer events differently from regular cron execution. This mechanism applies to another scenario: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. The given lab state instead requires the more specific cause in the correct choice.

D:

Isolating an active target does not set the default target for future boots. This mechanism applies to another scenario: A lab machine must boot into `multi-user.target` but an operator only isolates that target for the current session. The given lab state instead requires the more specific cause in the correct choice.

Question 68

For this Linux administration lab: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. Which safety and lifecycle check best prevents the same problem returning?

  1. Review package source provenance before modifying repository trust policies.
  2. Document catch-up side effects before enabling persistent timers for state-changing tasks.
  3. Use update logs, change windows and service verification rather than unreviewed broad upgrades.
  4. Use full paths and verify the account's crontab and log capture.

Explanation

Correct Answer

D:

Use full paths and verify the account's crontab and log capture. This guards against recurrence of: Cron evaluates scheduled commands repeatedly according to its five time fields. Confirm the lab's final state by: `crontab -l` shows the entry and lab logs confirm recurring executions with controlled environment.

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: Cron evaluates scheduled commands repeatedly according to its five time fields.

B:

Document catch-up side effects before enabling persistent timers for state-changing tasks. That control is best suited to a separate scenario: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. It is not the best safeguard for the current mechanism: Cron evaluates scheduled commands repeatedly according to its five time fields.

C:

Use update logs, change windows and service verification rather than unreviewed broad upgrades. That control is best suited to a separate scenario: An RPM package on a training node is stale; the administrator needs to apply approved security updates without reinstalling everything. It is not the best safeguard for the current mechanism: Cron evaluates scheduled commands repeatedly according to its five time fields.

Question 69

A student working on a test RHEL10 instance receives this assignment: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. Which answer gives the correct practical approach?

  1. Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.
  2. Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.
  3. Use `firewall-cmd --zone=public --add-service=http --permanent` and reload after verifying intended interface zone.
  4. Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope.

Explanation

Correct Answer

B:

Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan. This directly addresses the lab target: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. The underlying behavior is: `ip` runtime configuration alone does not update NetworkManager's stored connection profile. Verification: After reconnect or reboot `nmcli con show` and `ip addr` still report the address.

Incorrect Answers

A:

Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe. This is an appropriate step for a DIFFERENT exercise, specifically: A NetworkManager profile is stored on disk but is not automatically activated after reboot. It does not address the required lab state, whose mechanism is: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

C:

Use `firewall-cmd --zone=public --add-service=http --permanent` and reload after verifying intended interface zone. This is an appropriate step for a DIFFERENT exercise, specifically: A standard `http` service should be allowed through firewalld, but the operator adds a broad arbitrary port range. It does not address the required lab state, whose mechanism is: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

D:

Use a supported `nmcli connection up lablan` or `nmcli device reapply <interface>` procedure after confirming console access and change scope. This is an appropriate step for a DIFFERENT exercise, specifically: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not address the required lab state, whose mechanism is: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

Question 70

You have attempted this task on a test RHEL10 instance: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. Which command output or observation best confirms its success?

  1. `ip route get 203.0.113.10` selects the correct gateway and the intended test connection succeeds.
  2. `firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects.
  3. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.
  4. `ip -6 addr show` lists the address and a local IPv6 connectivity test succeeds.

Explanation

Correct Answer

C:

After reconnect or reboot `nmcli con show` and `ip addr` still report the address. This check confirms the expected effect of: Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan. It distinguishes the intended result from the original failure mechanism: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

Incorrect Answers

A:

`ip route get 203.0.113.10` selects the correct gateway and the intended test connection succeeds. That verifies a separate lab task: The lab interface is assigned the right IP but the host cannot reach an off-subnet gateway due to an incorrect default route. It does not validate the implementation required here: Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.

B:

`firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects. That verifies a separate lab task: A service listens on port 8443 but clients are blocked by the active public firewalld zone. It does not validate the implementation required here: Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.

D:

`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: Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.