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 3

Question 20

For this Linux administration lab: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. Which safety and lifecycle check best prevents the same problem returning?

  1. Audit swap entries and device UUIDs after storage migrations.
  2. Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot.
  3. Test swap capacity and persist the selected UUID in `/etc/fstab` for future boots.
  4. Require a signed disk-to-VM inventory and backup review before changing partition tables.

Explanation

Correct Answer

D:

Require a signed disk-to-VM inventory and backup review before changing partition tables. This guards against recurrence of: Device names can change and `lsblk` alone does not authorize destructive partition operations. Confirm the lab's final state by: The selected disk has no filesystem, partition or mount dependencies and matches the lab's disk ID.

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: Device names can change and `lsblk` alone does not authorize destructive partition operations.

B:

Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot. That control is best suited to a separate scenario: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It is not the best safeguard for the current mechanism: Device names can change and `lsblk` alone does not authorize destructive partition operations.

C:

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 names can change and `lsblk` alone does not authorize destructive partition operations.

Question 21

A student working on a test RHEL10 instance receives this assignment: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. Which answer gives the correct practical approach?

  1. Review `namei -l /srv/team/report`, set the directory traverse bit and appropriate file group read permission.
  2. Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.
  3. Set the group owner and setgid bit on the lab directory, e.g. `chgrp analysts /srv/team && chmod 2770 /srv/team`.
  4. Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.

Explanation

Correct Answer

B:

Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted. This directly addresses the lab target: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. The underlying behavior is: Formatting creates filesystem metadata and overwrites the previous block contents. Verification: `blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID.

Incorrect Answers

A:

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: Formatting creates filesystem metadata and overwrites the previous block contents.

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: Formatting creates filesystem metadata and overwrites the previous block contents.

D:

Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`. This is an appropriate step for a DIFFERENT exercise, specifically: An fstab entry for a newly created filesystem contains a typo and the lab VM hangs on the next reboot. It does not address the required lab state, whose mechanism is: Formatting creates filesystem metadata and overwrites the previous block contents.

Question 22

You have attempted this task on a test RHEL10 instance: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. Which command output or observation best confirms its success?

  1. A test member can traverse the path and read the file without permitting unrelated users.
  2. Two test users can create files but one cannot remove the other's file without applicable privilege.
  3. `blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID.
  4. A simulated server outage does not block the expected system boot and access after recovery mounts normally.

Explanation

Correct Answer

C:

`blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID. This check confirms the expected effect of: Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted. It distinguishes the intended result from the original failure mechanism: Formatting creates filesystem metadata and overwrites the previous block contents.

Incorrect Answers

A:

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: Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.

B:

Two test users can create files but one cannot remove the other's file without applicable privilege. That verifies a separate lab task: A sticky-bit public scratch directory must allow shared file creation while preventing users from deleting each other's files. It does not validate the implementation required here: Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.

D:

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: Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.

Question 23

Troubleshoot the following RHEL 10 lab situation: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. Identify the key Linux mechanism behind the issue.

  1. All parent directory traversal permissions and file modes affect effective access.
  2. Increasing block-device capacity does not automatically grow the filesystem metadata.
  3. NFS mounting uses a server export path and a compatible network client rather than local disk formatting.
  4. Formatting creates filesystem metadata and overwrites the previous block contents.

Explanation

Correct Answer

D:

Formatting creates filesystem metadata and overwrites the previous block contents. This explains the task's initial state: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. The supported lab action is: Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.

Incorrect Answers

A:

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.

B:

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.

C:

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.

Question 24

Following lab verification, document the preventive or persistence-oriented procedure for: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. Which practice is most suitable?

  1. Never format before confirming the exact blank lab device and backup status.
  2. Validate filesystem type and correct resizing utility before growing an LV-backed filesystem.
  3. Validate map syntax and restart/enable autofs after controlled changes.
  4. Configure an appropriate persistent mount separately after runtime testing.

Explanation

Correct Answer

A:

Never format before confirming the exact blank lab device and backup status. This guards against recurrence of: Formatting creates filesystem metadata and overwrites the previous block contents. Confirm the lab's final state by: `blkid /dev/vg_training/lv_data` reports `TYPE="xfs"` and a new filesystem UUID.

Incorrect Answers

B:

Validate filesystem type and correct resizing utility before growing an LV-backed filesystem. That control is best suited to a separate scenario: An ext4 training LV was expanded but file capacity remains unchanged. It is not the best safeguard for the current mechanism: Formatting creates filesystem metadata and overwrites the previous block contents.

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: Formatting creates filesystem metadata and overwrites the previous block contents.

D:

Configure an appropriate persistent mount separately after runtime testing. That control is best suited to a separate scenario: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. It is not the best safeguard for the current mechanism: Formatting creates filesystem metadata and overwrites the previous block contents.

Question 25

On an isolated enterprise lab VM, perform the following practical task: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. Which action should be carried out after confirming the lab prerequisites?

  1. Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources.
  2. Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate.
  3. Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.
  4. Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.

Explanation

Correct Answer

C:

Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized. This directly addresses the lab target: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. The underlying behavior is: An `at` job is one-shot, unlike a recurring cron schedule. Verification: `atq` lists the pending job and the fixture log records one run at the expected time.

Incorrect Answers

A:

Configure the approved `server ntp.lab iburst` entry in chrony configuration, restart the service, and check sources. This is an appropriate step for a DIFFERENT exercise, specifically: 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 address the required lab state, whose mechanism is: An `at` job is one-shot, unlike a recurring cron schedule.

B:

Configure a systemd calendar timer with `Persistent=true` where catch-up behavior is appropriate. This is an appropriate step for a DIFFERENT exercise, specifically: A scheduled housekeeping task should run once after a machine missed its overnight run while powered off. It does not address the required lab state, whose mechanism is: An `at` job is one-shot, unlike a recurring cron schedule.

D:

Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy. This is an appropriate step for a DIFFERENT exercise, specifically: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. It does not address the required lab state, whose mechanism is: An `at` job is one-shot, unlike a recurring cron schedule.

Question 26

The lab examiner asks for evidence after this assignment: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. What is the decisive verification step?

  1. `systemctl list-timers --all` shows the timer and journal records service invocations.
  2. The target package's metadata resolves from an entitled supported repository.
  3. Current time becomes accurate while the configured local timezone remains unchanged.
  4. `atq` lists the pending job and the fixture log records one run at the expected time.

Explanation

Correct Answer

D:

`atq` lists the pending job and the fixture log records one run at the expected time. This check confirms the expected effect of: Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized. It distinguishes the intended result from the original failure mechanism: An `at` job is one-shot, unlike a recurring cron schedule.

Incorrect Answers

A:

`systemctl list-timers --all` shows the timer and journal records service invocations. That verifies a separate lab task: A systemd timer unit is enabled but never starts the report job because its matching service name is wrong. It does not validate the implementation required here: Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.

B:

The target package's metadata resolves from an entitled supported repository. That verifies a separate lab task: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It does not validate the implementation required here: Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.

C:

Current time becomes accurate while the configured local timezone remains unchanged. That verifies a separate lab task: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. It does not validate the implementation required here: Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.

Question 27

A training host has this situation: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. Which system behavior best explains the original failure or risk?

  1. An `at` job is one-shot, unlike a recurring cron schedule.
  2. Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.
  3. DNF update resolves and records package lifecycle changes through configured repositories.
  4. Service restart policy cannot repair an invalid executable or configuration on its own.

Explanation

Correct Answer

A:

An `at` job is one-shot, unlike a recurring cron schedule. This explains the task's initial state: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. The supported lab action is: Schedule `echo '/usr/local/bin/lab-report' | at 19:15` after ensuring `atd` is active and the task is authorized.

Incorrect Answers

B:

Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS. This mechanism applies to another scenario: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. The given lab state instead requires the more specific cause in the correct choice.

C:

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.

D:

Service restart policy cannot repair an invalid executable or configuration on its own. This mechanism applies to another scenario: A service starts but restarts endlessly because `Restart=always` masks a broken configuration, filling logs. The given lab state instead requires the more specific cause in the correct choice.

Question 28

A student has implemented the following configuration: A disposable RHEL system must execute a one-time administrative script at 19:15 today rather than repeatedly. What repeatable control best reduces regressions or unsafe changes?

  1. Verify selected kernel and retain a known-good fallback after kernel maintenance.
  2. Verify the queue and remove obsolete tasks with `atrm` before the execution time.
  3. Review package source provenance before modifying repository trust policies.
  4. Include unit reload, activation and next-fire-time checks in release tasks.

Explanation

Correct Answer

B:

Verify the queue and remove obsolete tasks with `atrm` before the execution time. This guards against recurrence of: An `at` job is one-shot, unlike a recurring cron schedule. Confirm the lab's final state by: `atq` lists the pending job and the fixture log records one run at the expected time.

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: An `at` job is one-shot, unlike a recurring cron schedule.

C:

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: An `at` job is one-shot, unlike a recurring cron schedule.

D:

Include unit reload, activation and next-fire-time checks in release tasks. That control is best suited to a separate scenario: A timer has been created under `/etc/systemd/system`, but it shows inactive and the intended job never runs. It is not the best safeguard for the current mechanism: An `at` job is one-shot, unlike a recurring cron schedule.

Question 29

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: A training host has DHCP IPv4 but requires a fixed address `192.0.2.50/24` and gateway `192.0.2.1` for a private lab subnet. Select the most appropriate implementation step.

  1. Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.
  2. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.
  3. Review the `ipv6.method`, RA and gateway settings on the correct NetworkManager profile, and apply the approved configuration.
  4. Identify its NetworkManager profile, then `nmcli con mod lablan ipv4.method manual ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1` in the isolated lab.

Explanation

Correct Answer

D:

Identify its NetworkManager profile, then `nmcli con mod lablan ipv4.method manual ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1` in the isolated lab. This directly addresses the lab target: A training host has DHCP IPv4 but requires a fixed address `192.0.2.50/24` and gateway `192.0.2.1` for a private lab subnet. The underlying behavior is: NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands. Verification: `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.

Incorrect Answers

A:

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 is an appropriate step for a DIFFERENT exercise, specifically: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not address the required lab state, whose mechanism is: NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands.

B:

Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. It does not address the required lab state, whose mechanism is: NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands.

C:

Review the `ipv6.method`, RA and gateway settings on the correct NetworkManager profile, and apply the approved configuration. This is an appropriate step for a DIFFERENT exercise, specifically: An IPv6 connection receives a default route from router advertisements when policy requires the test host to use only a specified local IPv6 subnet. It does not address the required lab state, whose mechanism is: NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands.

Question 30

After a lab configuration change, verify: A training host has DHCP IPv4 but requires a fixed address `192.0.2.50/24` and gateway `192.0.2.1` for a private lab subnet. Which result most directly proves the desired system state?

  1. `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.
  2. The profile reflects changed settings and existing remote management remains recoverable.
  3. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.
  4. The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled.

Explanation

Correct Answer

A:

`nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway. This check confirms the expected effect of: Identify its NetworkManager profile, then `nmcli con mod lablan ipv4.method manual ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1` in the isolated lab. It distinguishes the intended result from the original failure mechanism: NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands.

Incorrect Answers

B:

The profile reflects changed settings and existing remote management remains recoverable. That verifies a separate lab task: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not validate the implementation required here: Identify its NetworkManager profile, then `nmcli con mod lablan ipv4.method manual ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1` in the isolated lab.

C:

After reconnect or reboot `nmcli con show` and `ip addr` still report the address. That verifies a separate lab task: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not validate the implementation required here: Identify its NetworkManager profile, then `nmcli con mod lablan ipv4.method manual ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1` in the isolated lab.

D:

The listener remains available after a controlled reboot and `systemctl is-enabled httpd` reports enabled. That verifies a separate lab task: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It does not validate the implementation required here: Identify its NetworkManager profile, then `nmcli con mod lablan ipv4.method manual ipv4.addresses 192.0.2.50/24 ipv4.gateway 192.0.2.1` in the isolated lab.