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 39

Question 380

A student has implemented the following configuration: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. What repeatable control best reduces regressions or unsafe changes?

  1. Require unmount, backup and dependency review before LV retirement.
  2. Plan LV resizing and compatible filesystem growth as separate verified steps.
  3. Perform non-destructive detection before initializing any storage metadata.
  4. Monitor free-extents capacity and set thresholds before service expansion.

Explanation

Correct Answer

B:

Plan LV resizing and compatible filesystem growth as separate verified steps. This guards against recurrence of: Logical volume capacity and filesystem capacity are distinct layers. Confirm the lab's final state by: `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.

Incorrect Answers

A:

Require unmount, backup and dependency review before LV retirement. That control is best suited to a separate scenario: A test operator removed a block LV without first unmounting it, risking a busy-device error or data loss. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.

C:

Perform non-destructive detection before initializing any storage metadata. That control is best suited to a separate scenario: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.

D:

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: Logical volume capacity and filesystem capacity are distinct layers.

Question 381

You are responsible for a test RHEL10 instance. The required hands-on outcome is: A large remote home-directory NFS tree should mount on demand rather than all at login. Select the most appropriate implementation step.

  1. Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted.
  2. Check the server export permissions, UID/GID mapping and client ownership, then correct authorized permissions on the exporting server.
  3. Correct the test entry using the UUID from `blkid`, review the filesystem type and options, and run `findmnt --verify`.
  4. Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.

Explanation

Correct Answer

D:

Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports. This directly addresses the lab target: A large remote home-directory NFS tree should mount on demand rather than all at login. The underlying behavior is: Autofs mounts configured network resources on access instead of requiring an always-mounted tree. Verification: Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map.

Incorrect Answers

A:

Run `mkfs.xfs /dev/vg_training/lv_data` only after verifying that it is empty and unmounted. This is an appropriate step for a DIFFERENT exercise, specifically: A fresh disposable LV is unformatted and must hold an XFS file system for a lab data directory. It does not address the required lab state, whose mechanism is: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

B:

Check the server export permissions, UID/GID mapping and client ownership, then correct authorized permissions on the exporting server. This is an appropriate step for a DIFFERENT exercise, specifically: A team creates an NFS mount locally but cannot write files despite apparently open Unix mode bits. It does not address the required lab state, whose mechanism is: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

C:

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: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

Question 382

After a lab configuration change, verify: A large remote home-directory NFS tree should mount on demand rather than all at login. Which result most directly proves the desired system state?

  1. Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map.
  2. A request to the mapped directory resolves the updated server export without reusing the stale path.
  3. `findmnt /mnt/team` reports an NFS mount and a permitted test file is readable.
  4. After a controlled reboot `findmnt /srv/archive` resolves the correct UUID and type.

Explanation

Correct Answer

A:

Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map. This check confirms the expected effect of: Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports. It distinguishes the intended result from the original failure mechanism: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

Incorrect Answers

B:

A request to the mapped directory resolves the updated server export without reusing the stale path. That verifies a separate lab task: A new autofs indirect map was edited but clients keep using the previous exported path. It does not validate the implementation required here: Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.

C:

`findmnt /mnt/team` reports an NFS mount and a permitted test file is readable. That verifies a separate lab task: A lab NFS server exports `/exports/team` and a client needs it under `/mnt/team` during the current session. It does not validate the implementation required here: Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.

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: Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.

Question 383

In an EX200-style practice lab, this condition exists: A large remote home-directory NFS tree should mount on demand rather than all at login. Which explanation correctly identifies the underlying issue?

  1. XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration.
  2. Autofs mounts configured network resources on access instead of requiring an always-mounted tree.
  3. Filesystem presence alone does not attach it into the directory namespace.
  4. Increasing block-device capacity does not automatically grow the filesystem metadata.

Explanation

Correct Answer

B:

Autofs mounts configured network resources on access instead of requiring an always-mounted tree. This explains the task's initial state: A large remote home-directory NFS tree should mount on demand rather than all at login. The supported lab action is: Configure `/etc/auto.master.d/lab.autofs` to reference an approved indirect map and add entries for the lab home exports.

Incorrect Answers

A:

XFS and ext4 are different filesystem formats and cannot be interchanged after formatting without migration. This mechanism applies to another scenario: A disposable training volume is required to use ext4 so filesystem behavior can be compared with XFS. The given lab state instead requires the more specific cause in the correct choice.

C:

Filesystem presence alone does not attach it into the directory namespace. This mechanism applies to another scenario: An XFS LV exists but its content is unavailable because no mountpoint or active mount has been created. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 384

After completing this practical task on a test RHEL10 instance: A large remote home-directory NFS tree should mount on demand rather than all at login. Which operational safeguard helps keep the result correct and safe?

  1. Perform filesystem-aware resize following every block extension and confirm available bytes.
  2. Treat fstab modifications as high-impact and test mount behavior while a recovery console is available.
  3. Validate map syntax and restart/enable autofs after controlled changes.
  4. Configure an appropriate persistent mount separately after runtime testing.

Explanation

Correct Answer

C:

Validate map syntax and restart/enable autofs after controlled changes. This guards against recurrence of: Autofs mounts configured network resources on access instead of requiring an always-mounted tree. Confirm the lab's final state by: Accessing `/home/remote/student` triggers the expected mount and `automount -m` shows the map.

Incorrect Answers

A:

Perform filesystem-aware resize following every block extension and confirm available bytes. That control is best suited to a separate scenario: An XFS filesystem is nearly full even though its LV has been extended by 2 GiB. It is not the best safeguard for the current mechanism: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

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: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

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: Autofs mounts configured network resources on access instead of requiring an always-mounted tree.

Question 385

Lab exercise on an isolated enterprise lab VM: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.
  2. Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement.
  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. Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account.

Explanation

Correct Answer

A:

Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy. This directly addresses the lab target: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. The underlying behavior is: Timezone presentation and NTP clock synchronization are different configuration concerns. Verification: Current time becomes accurate while the configured local timezone remains unchanged.

Incorrect Answers

B:

Review `subscription-manager status` as applicable and `dnf repolist --all`, then correct approved repo enablement. This is an appropriate step for a DIFFERENT exercise, specifically: A host is subscribed to Red Hat content but its custom repo definition incorrectly overrides the needed package source. It does not address the required lab state, whose mechanism is: Timezone presentation and NTP clock synchronization are different configuration concerns.

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 is an appropriate step for a DIFFERENT exercise, specifically: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It does not address the required lab state, whose mechanism is: Timezone presentation and NTP clock synchronization are different configuration concerns.

D:

Install an approved crontab entry `30 2 * * * /usr/local/bin/lab-report` for the correct account. This is an appropriate step for a DIFFERENT exercise, specifically: An analyst needs a recurring report at 02:30 every day, but a manually started shell script runs only once. It does not address the required lab state, whose mechanism is: Timezone presentation and NTP clock synchronization are different configuration concerns.

Question 386

In a hands-on RHCSA practice VM, the assigned outcome was: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. What specific verification would demonstrate the target state?

  1. `systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot.
  2. Current time becomes accurate while the configured local timezone remains unchanged.
  3. After a controlled reboot, the mount is available when the service starts and the application reads its data.
  4. `rpm -q packagename` shows the intended version and services are functionally checked after any required restart.

Explanation

Correct Answer

B:

Current time becomes accurate while the configured local timezone remains unchanged. This check confirms the expected effect of: Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy. It distinguishes the intended result from the original failure mechanism: Timezone presentation and NTP clock synchronization are different configuration concerns.

Incorrect Answers

A:

`systemctl is-enabled chronyd` and `systemctl is-active chronyd` report enabled/active, also after reboot. That verifies a separate lab task: A daemon is started manually after package installation but must be reliably available after reboots. It does not validate the implementation required here: Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.

C:

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 `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.

D:

`rpm -q packagename` shows the intended version and services are functionally checked after any required restart. That verifies a separate lab task: An RPM package on a training node is stale; the administrator needs to apply approved security updates without reinstalling everything. It does not validate the implementation required here: Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.

Question 387

A trainee is diagnosing: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. Which root cause should they recognize before changing the system?

  1. Systemd cannot start a unit whose configured executable is absent.
  2. DNF update resolves and records package lifecycle changes through configured repositories.
  3. Timezone presentation and NTP clock synchronization are different configuration concerns.
  4. Systemd service ordering and filesystem availability are separate dependencies.

Explanation

Correct Answer

C:

Timezone presentation and NTP clock synchronization are different configuration concerns. This explains the task's initial state: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. The supported lab action is: Use `timedatectl status` to distinguish timezone from system clock synchronization; correct chrony sources for clock accuracy.

Incorrect Answers

A:

Systemd cannot start a unit whose configured executable is absent. This mechanism applies to another scenario: A new custom service has an `ExecStart` path that no longer exists after the application was moved. The given lab state instead requires the more specific cause in the correct choice.

B:

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:

Systemd service ordering and filesystem availability are separate dependencies. This mechanism applies to another scenario: A service is enabled and active, but the actual application fails after boot because a required mount is not available in time. The given lab state instead requires the more specific cause in the correct choice.

Question 388

For this Linux administration lab: The system clock is wrong but the troubleshooting script changes the timezone instead of fixing time synchronization. Which safety and lifecycle check best prevents the same problem returning?

  1. Verify selected kernel and retain a known-good fallback after kernel maintenance.
  2. Maintain approved time servers and monitor drift/offset after network changes.
  3. Record firmware mode and test recovery entry after bootloader configuration changes.
  4. Audit time source and timezone independently in host acceptance tests.

Explanation

Correct Answer

D:

Audit time source and timezone independently in host acceptance tests. This guards against recurrence of: Timezone presentation and NTP clock synchronization are different configuration concerns. Confirm the lab's final state by: Current time becomes accurate while the configured local timezone remains 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: Timezone presentation and NTP clock synchronization are different configuration concerns.

B:

Maintain approved time servers and monitor drift/offset after network changes. That control is best suited to a separate scenario: NTP clients show clock drift because the time service package is installed but not configured to use the training network's time source. It is not the best safeguard for the current mechanism: Timezone presentation and NTP clock synchronization are different configuration concerns.

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: Timezone presentation and NTP clock synchronization are different configuration concerns.

Question 389

A student working on a disposable RHEL10 training node receives this assignment: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. Which answer gives the correct practical approach?

  1. Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.
  2. After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.
  3. Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.
  4. Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

Explanation

Correct Answer

B:

After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule. This directly addresses the lab target: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. The underlying behavior is: Firewalld runtime rules and permanent rules are separate states. Verification: The port remains listed in permanent configuration and works after a controlled reboot.

Incorrect Answers

A:

Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It does not address the required lab state, whose mechanism is: Firewalld runtime rules and permanent rules are separate states.

C:

Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally. This is an appropriate step for a DIFFERENT exercise, specifically: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It does not address the required lab state, whose mechanism is: Firewalld runtime rules and permanent rules are separate states.

D:

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: Firewalld runtime rules and permanent rules are separate states.

Question 390

You have attempted this task on a disposable RHEL10 training node: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. Which command output or observation best confirms its success?

  1. An authorized client connects and the correct zone reports the service or port.
  2. The profile reflects changed settings and existing remote management remains recoverable.
  3. The port remains listed in permanent configuration and works after a controlled reboot.
  4. `hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot.

Explanation

Correct Answer

C:

The port remains listed in permanent configuration and works after a controlled reboot. This check confirms the expected effect of: After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule. It distinguishes the intended result from the original failure mechanism: Firewalld runtime rules and permanent rules are separate states.

Incorrect Answers

A:

An authorized client connects and the correct zone reports the service or port. That verifies a separate lab task: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. It does not validate the implementation required here: After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.

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: After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.

D:

`hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot. That verifies a separate lab task: A hostname change is applied only with the `hostname` runtime command and resets after restart. It does not validate the implementation required here: After testing, use `firewall-cmd --zone=public --add-port=8443/tcp --permanent && firewall-cmd --reload` to record the intended persistent rule.