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 63

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.

Question 621

You are responsible for a test RHEL10 instance. The required hands-on outcome is: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. Select the most appropriate implementation step.

  1. Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM.
  2. Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured.
  3. Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.
  4. Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.

Explanation

Correct Answer

D:

Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment. This directly addresses the lab target: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. The underlying behavior is: Disabling the firewall replaces one narrow authorization issue with broad exposure. Verification: `firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled.

Incorrect Answers

A:

Add a reviewed entry such as `192.0.2.11 db150.lab` to `/etc/hosts` on the test VM. This is an appropriate step for a DIFFERENT exercise, specifically: A training host must resolve one intentionally private name without querying DNS while building a disconnected lab. It does not address the required lab state, whose mechanism is: Disabling the firewall replaces one narrow authorization issue with broad exposure.

B:

Run `systemctl enable --now httpd` after ensuring the approved web service is installed and configured. This is an appropriate step for a DIFFERENT exercise, specifically: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It does not address the required lab state, whose mechanism is: Disabling the firewall replaces one narrow authorization issue with broad exposure.

C:

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: Disabling the firewall replaces one narrow authorization issue with broad exposure.

Question 622

After a lab configuration change, verify: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. Which result most directly proves the desired system state?

  1. `firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled.
  2. A test from the management subnet succeeds and an unauthorized source is denied.
  3. `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.
  4. `hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot.

Explanation

Correct Answer

A:

`firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled. This check confirms the expected effect of: Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment. It distinguishes the intended result from the original failure mechanism: Disabling the firewall replaces one narrow authorization issue with broad exposure.

Incorrect Answers

B:

A test from the management subnet succeeds and an unauthorized source is denied. That verifies a separate lab task: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It does not validate the implementation required here: Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.

C:

`nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway. That verifies a separate lab task: 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. It does not validate the implementation required here: Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.

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: Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.

Question 623

In an EX200-style practice lab, this condition exists: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. Which explanation correctly identifies the underlying issue?

  1. Global zone-wide service allowances are broader than a source-limited access requirement.
  2. Disabling the firewall replaces one narrow authorization issue with broad exposure.
  3. ICMP reachability to a gateway does not prove DNS or TCP application availability.
  4. Runtime hostname assignment may not update the persistent static hostname.

Explanation

Correct Answer

B:

Disabling the firewall replaces one narrow authorization issue with broad exposure. This explains the task's initial state: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. The supported lab action is: Restore only the approved missing service with `firewall-cmd --zone=public --add-service=ssh --permanent` and reload in the isolated test environment.

Incorrect Answers

A:

Global zone-wide service allowances are broader than a source-limited access requirement. This mechanism applies to another scenario: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. The given lab state instead requires the more specific cause in the correct choice.

C:

ICMP reachability to a gateway does not prove DNS or TCP application availability. This mechanism applies to another scenario: The host can ping its gateway but an HTTPS connection fails; the operator wants to blame DNS without checking name resolution. The given lab state instead requires the more specific cause in the correct choice.

D:

Runtime hostname assignment may not update the persistent static hostname. This mechanism applies to another scenario: A hostname change is applied only with the `hostname` runtime command and resets after restart. The given lab state instead requires the more specific cause in the correct choice.

Question 624

After completing this practical task on a test RHEL10 instance: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. Which operational safeguard helps keep the result correct and safe?

  1. Set the static hostname and confirm it is resolvable under the site's DNS plan.
  2. Make durable host addressing changes in the managed profile and test persistence.
  3. Use minimum required allowed services while retaining firewalld enforcement.
  4. Prefer narrowly scoped service definitions and remove unused rules.

Explanation

Correct Answer

C:

Use minimum required allowed services while retaining firewalld enforcement. This guards against recurrence of: Disabling the firewall replaces one narrow authorization issue with broad exposure. Confirm the lab's final state by: `firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled.

Incorrect Answers

A:

Set the static hostname and confirm it is resolvable under the site's DNS plan. That control is best suited to a separate scenario: A hostname change is applied only with the `hostname` runtime command and resets after restart. It is not the best safeguard for the current mechanism: Disabling the firewall replaces one narrow authorization issue with broad exposure.

B:

Make durable host addressing changes in the managed profile and test persistence. That control is best suited to a separate scenario: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It is not the best safeguard for the current mechanism: Disabling the firewall replaces one narrow authorization issue with broad exposure.

D:

Prefer narrowly scoped service definitions and remove unused rules. That control is best suited to a separate scenario: A standard `http` service should be allowed through firewalld, but the operator adds a broad arbitrary port range. It is not the best safeguard for the current mechanism: Disabling the firewall replaces one narrow authorization issue with broad exposure.

Question 625

Lab exercise on an isolated enterprise lab VM: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data.
  2. Run `useradd -m -s /bin/bash trainee1` on the authorized disposable VM, then provision credentials securely.
  3. Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.
  4. Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group.

Explanation

Correct Answer

A:

After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data. This directly addresses the lab target: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. The underlying behavior is: Deleting a local account and its home is destructive and distinct from locking it. Verification: `getent passwd trainee_retired` finds no account and its disposable home is removed.

Incorrect Answers

B:

Run `useradd -m -s /bin/bash trainee1` on the authorized disposable VM, then provision credentials securely. This is an appropriate step for a DIFFERENT exercise, specifically: A new lab operator needs a local account with a home directory and normal login shell. It does not address the required lab state, whose mechanism is: Deleting a local account and its home is destructive and distinct from locking it.

C:

Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`. This is an appropriate step for a DIFFERENT exercise, specifically: A new user must have a private home directory rather than inherited group-read access. It does not address the required lab state, whose mechanism is: Deleting a local account and its home is destructive and distinct from locking it.

D:

Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group. This is an appropriate step for a DIFFERENT exercise, specifically: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. It does not address the required lab state, whose mechanism is: Deleting a local account and its home is destructive and distinct from locking it.

Question 626

In a hands-on RHCSA practice VM, the assigned outcome was: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. What specific verification would demonstrate the target state?

  1. `id trainee1` includes `analysts` and the prior supplementary groups remain.
  2. `getent passwd trainee_retired` finds no account and its disposable home is removed.
  3. `stat -c '%a %U:%G'` reports the expected properties and a different test user cannot traverse the home.
  4. `id correctedname` shows the original UID and the intended home location is valid.

Explanation

Correct Answer

B:

`getent passwd trainee_retired` finds no account and its disposable home is removed. This check confirms the expected effect of: After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data. It distinguishes the intended result from the original failure mechanism: Deleting a local account and its home is destructive and distinct from locking it.

Incorrect Answers

A:

`id trainee1` includes `analysts` and the prior supplementary groups remain. That verifies a separate lab task: A user must join the `analysts` group without losing their existing supplementary groups. It does not validate the implementation required here: After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data.

C:

`stat -c '%a %U:%G'` reports the expected properties and a different test user cannot traverse the home. That verifies a separate lab task: A new user must have a private home directory rather than inherited group-read access. It does not validate the implementation required here: After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data.

D:

`id correctedname` shows the original UID and the intended home location is valid. That verifies a separate lab task: A user account has a misspelled login name but should keep its existing UID and home ownership. It does not validate the implementation required here: After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data.

Question 627

A trainee is diagnosing: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. Which root cause should they recognize before changing the system?

  1. Renaming a login does not automatically guarantee home directory renaming in every workflow.
  2. Primary group and supplementary group settings have different semantics.
  3. Deleting a local account and its home is destructive and distinct from locking it.
  4. Directory traversal and ownership control privacy of files below the home directory.

Explanation

Correct Answer

C:

Deleting a local account and its home is destructive and distinct from locking it. This explains the task's initial state: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. The supported lab action is: After archival and confirmation of the disposable identity, use `userdel -r trainee_retired` while preserving any required external data.

Incorrect Answers

A:

Renaming a login does not automatically guarantee home directory renaming in every workflow. This mechanism applies to another scenario: A user account has a misspelled login name but should keep its existing UID and home ownership. The given lab state instead requires the more specific cause in the correct choice.

B:

Primary group and supplementary group settings have different semantics. This mechanism applies to another scenario: A team requires a default primary group different from the user-private group created with the account. The given lab state instead requires the more specific cause in the correct choice.

D:

Directory traversal and ownership control privacy of files below the home directory. This mechanism applies to another scenario: A new user must have a private home directory rather than inherited group-read access. The given lab state instead requires the more specific cause in the correct choice.

Question 628

For this Linux administration lab: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. Which safety and lifecycle check best prevents the same problem returning?

  1. Verify membership and filesystem permissions after defining access groups.
  2. Plan login, home, file ownership and scheduled-task references as a single account migration.
  3. Include end dates in contractor onboarding and remove access at offboarding.
  4. Require archived data and explicit authorization before user removal.

Explanation

Correct Answer

D:

Require archived data and explicit authorization before user removal. This guards against recurrence of: Deleting a local account and its home is destructive and distinct from locking it. Confirm the lab's final state by: `getent passwd trainee_retired` finds no account and its disposable home is removed.

Incorrect Answers

A:

Verify membership and filesystem permissions after defining access groups. That control is best suited to a separate scenario: A project team needs a new local group `analysts` to own shared reports. It is not the best safeguard for the current mechanism: Deleting a local account and its home is destructive and distinct from locking it.

B:

Plan login, home, file ownership and scheduled-task references as a single account migration. That control is best suited to a separate scenario: A user account has a misspelled login name but should keep its existing UID and home ownership. It is not the best safeguard for the current mechanism: Deleting a local account and its home is destructive and distinct from locking it.

C:

Include end dates in contractor onboarding and remove access at offboarding. That control is best suited to a separate scenario: A short-term external account must stop being usable on a specified end date while its password policy remains unchanged. It is not the best safeguard for the current mechanism: Deleting a local account and its home is destructive and distinct from locking it.

Question 629

A student working on a disposable RHEL10 training node receives this assignment: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. Which answer gives the correct practical approach?

  1. Set `umask 077` in the sensitive workflow before creating the secret fixture.
  2. Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.
  3. Use `getsebool httpd_can_network_connect_db`; after verifying policy, set `setsebool -P httpd_can_network_connect_db on` where supported.
  4. Use `semanage fcontext -a -t httpd_sys_content_t '/srv/custom-web(/.*)?'` then `restorecon -Rv /srv/custom-web` after verifying appropriate policy.

Explanation

Correct Answer

B:

Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`. This directly addresses the lab target: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. The underlying behavior is: Runtime and permanent firewalld configurations are separate. Verification: `firewall-cmd --permanent --zone=public --list-services` includes HTTPS and the state survives reboot.

Incorrect Answers

A:

Set `umask 077` in the sensitive workflow before creating the secret fixture. This is an appropriate step for a DIFFERENT exercise, specifically: A shell session creates files with default modes exposing group-readable secrets to unrelated users. It does not address the required lab state, whose mechanism is: Runtime and permanent firewalld configurations are separate.

C:

Use `getsebool httpd_can_network_connect_db`; after verifying policy, set `setsebool -P httpd_can_network_connect_db on` where supported. This is an appropriate step for a DIFFERENT exercise, specifically: An application hosted by Apache needs outbound database connections but SELinux policy denies them even with network routing functional. It does not address the required lab state, whose mechanism is: Runtime and permanent firewalld configurations are separate.

D:

Use `semanage fcontext -a -t httpd_sys_content_t '/srv/custom-web(/.*)?'` then `restorecon -Rv /srv/custom-web` after verifying appropriate policy. This is an appropriate step for a DIFFERENT exercise, specifically: A web service moved to `/srv/custom-web` encounters SELinux denials because content copied from a home directory carries the wrong label. It does not address the required lab state, whose mechanism is: Runtime and permanent firewalld configurations are separate.

Question 630

You have attempted this task on a disposable RHEL10 training node: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. Which command output or observation best confirms its success?

  1. Current and configured SELinux modes converge to the intended approved state after reboot.
  2. The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted.
  3. `firewall-cmd --permanent --zone=public --list-services` includes HTTPS and the state survives reboot.
  4. A normal new file is mode `600` or more restrictive and a new directory is mode `700` or more restrictive.

Explanation

Correct Answer

C:

`firewall-cmd --permanent --zone=public --list-services` includes HTTPS and the state survives reboot. This check confirms the expected effect of: Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`. It distinguishes the intended result from the original failure mechanism: Runtime and permanent firewalld configurations are separate.

Incorrect Answers

A:

Current and configured SELinux modes converge to the intended approved state after reboot. That verifies a separate lab task: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. It does not validate the implementation required here: Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.

B:

The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted. That verifies a separate lab task: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. It does not validate the implementation required here: Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.

D:

A normal new file is mode `600` or more restrictive and a new directory is mode `700` or more restrictive. That verifies a separate lab task: A shell session creates files with default modes exposing group-readable secrets to unrelated users. It does not validate the implementation required here: Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.