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 8

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.

Question 71

Troubleshoot the following RHEL 10 lab situation: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. Identify the key Linux mechanism behind the issue.

  1. Firewalld rules are zone-specific and require persistence for reboot safety.
  2. Runtime hostname assignment may not update the persistent static hostname.
  3. NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands.
  4. `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

Explanation

Correct Answer

D:

`ip` runtime configuration alone does not update NetworkManager's stored connection profile. This explains the task's initial state: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. The supported lab action is: Use the correct persistent NetworkManager profile with `nmcli con mod lablan +ipv4.addresses 198.51.100.20/24` according to the approved addressing plan.

Incorrect Answers

A:

Firewalld rules are zone-specific and require persistence for reboot safety. This mechanism applies to another scenario: A service listens on port 8443 but clients are blocked by the active public firewalld zone. The given lab state instead requires the more specific cause in the correct choice.

B:

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.

C:

NetworkManager connection profiles hold persistent address settings, unlike transient `ip addr add` commands. This mechanism applies to another scenario: 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 given lab state instead requires the more specific cause in the correct choice.

Question 72

Following lab verification, document the preventive or persistence-oriented procedure for: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. Which practice is most suitable?

  1. Make durable host addressing changes in the managed profile and test persistence.
  2. Confirm unit enablement, listener, zone and end-to-end client response together.
  3. Limit firewall exposure to named service requirements and verify correct active zone.
  4. Test both allowed and denied source cases for management services.

Explanation

Correct Answer

A:

Make durable host addressing changes in the managed profile and test persistence. This guards against recurrence of: `ip` runtime configuration alone does not update NetworkManager's stored connection profile. Confirm the lab's final state by: After reconnect or reboot `nmcli con show` and `ip addr` still report the address.

Incorrect Answers

B:

Confirm unit enablement, listener, zone and end-to-end client response together. That control is best suited to a separate scenario: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. It is not the best safeguard for the current mechanism: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

C:

Limit firewall exposure to named service requirements and verify correct active zone. That control is best suited to a separate scenario: A service listens on port 8443 but clients are blocked by the active public firewalld zone. It is not the best safeguard for the current mechanism: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

D:

Test both allowed and denied source cases for management services. That control is best suited to a separate scenario: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It is not the best safeguard for the current mechanism: `ip` runtime configuration alone does not update NetworkManager's stored connection profile.

Question 73

On an isolated enterprise lab VM, perform the following practical task: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. Which action should be carried out after confirming the lab prerequisites?

  1. Use `chage -M 30 trainee1` after verifying the account and policy.
  2. Use the interactive `passwd trainee1` tool with a protected channel and appropriate permission.
  3. Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy.
  4. Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.

Explanation

Correct Answer

C:

Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy. This directly addresses the lab target: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. The underlying behavior is: Locking a local password is different from deleting the account and its data. Verification: `passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors.

Incorrect Answers

A:

Use `chage -M 30 trainee1` after verifying the account and policy. This is an appropriate step for a DIFFERENT exercise, specifically: A temporary user's password must expire after 30 days, but a student assumes changing it once enforces the rule. It does not address the required lab state, whose mechanism is: Locking a local password is different from deleting the account and its data.

B:

Use the interactive `passwd trainee1` tool with a protected channel and appropriate permission. This is an appropriate step for a DIFFERENT exercise, specifically: A training account needs its password reset by an authorized administrator without printing the new secret in a shell command. It does not address the required lab state, whose mechanism is: Locking a local password is different from deleting the account and its data.

D:

Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`. This is an appropriate step for a DIFFERENT exercise, specifically: A Unix access test fails because a group was added in `/etc/group`, but a long-running user session still reports an old group set. It does not address the required lab state, whose mechanism is: Locking a local password is different from deleting the account and its data.

Question 74

The lab examiner asks for evidence after this assignment: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. What is the decisive verification step?

  1. `getent group analysts` returns the new group record with a local GID.
  2. `chage -l contractor1` shows the intended account expiration date.
  3. `id trainee1` no longer includes `analysts`, while the primary GID remains unchanged.
  4. `passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors.

Explanation

Correct Answer

D:

`passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors. This check confirms the expected effect of: Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy. It distinguishes the intended result from the original failure mechanism: Locking a local password is different from deleting the account and its data.

Incorrect Answers

A:

`getent group analysts` returns the new group record with a local GID. That verifies a separate lab task: A project team needs a new local group `analysts` to own shared reports. It does not validate the implementation required here: Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy.

B:

`chage -l contractor1` shows the intended account expiration date. That verifies a separate lab task: A short-term external account must stop being usable on a specified end date while its password policy remains unchanged. It does not validate the implementation required here: Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy.

C:

`id trainee1` no longer includes `analysts`, while the primary GID remains unchanged. That verifies a separate lab task: A trainee is no longer authorized for the `analysts` supplemental group, but should retain their primary group. It does not validate the implementation required here: Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy.

Question 75

A training host has this situation: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. Which system behavior best explains the original failure or risk?

  1. Locking a local password is different from deleting the account and its data.
  2. Using `-G` without the append option can replace the user's supplementary group list.
  3. Account expiration is separate from password expiration or maximum password age.
  4. Password expiration policy is separate from the last time a password was changed.

Explanation

Correct Answer

A:

Locking a local password is different from deleting the account and its data. This explains the task's initial state: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. The supported lab action is: Use `usermod -L contractor1` and set an appropriate nonlogin shell or expiration according to the organization's access policy.

Incorrect Answers

B:

Using `-G` without the append option can replace the user's supplementary group list. This mechanism applies to another scenario: A user must join the `analysts` group without losing their existing supplementary groups. The given lab state instead requires the more specific cause in the correct choice.

C:

Account expiration is separate from password expiration or maximum password age. This mechanism applies to another scenario: A short-term external account must stop being usable on a specified end date while its password policy remains unchanged. The given lab state instead requires the more specific cause in the correct choice.

D:

Password expiration policy is separate from the last time a password was changed. This mechanism applies to another scenario: A temporary user's password must expire after 30 days, but a student assumes changing it once enforces the rule. The given lab state instead requires the more specific cause in the correct choice.

Question 76

A student has implemented the following configuration: A contractor account exists but should no longer permit interactive login after an engagement ends, while audit files must remain. What repeatable control best reduces regressions or unsafe changes?

  1. Audit membership before and after group changes and use `-aG` for additive grants.
  2. Use deprovisioning steps that also address SSH keys, sessions and privilege memberships.
  3. Review file ownership and service permissions after primary GID changes.
  4. Verify membership and filesystem permissions after defining access groups.

Explanation

Correct Answer

B:

Use deprovisioning steps that also address SSH keys, sessions and privilege memberships. This guards against recurrence of: Locking a local password is different from deleting the account and its data. Confirm the lab's final state by: `passwd -S contractor1` indicates locked credentials and preserved home files remain readable to authorized auditors.

Incorrect Answers

A:

Audit membership before and after group changes and use `-aG` for additive grants. That control is best suited to a separate scenario: A user must join the `analysts` group without losing their existing supplementary groups. It is not the best safeguard for the current mechanism: Locking a local password is different from deleting the account and its data.

C:

Review file ownership and service permissions after primary GID changes. That control is best suited to a separate scenario: A team requires a default primary group different from the user-private group created with the account. It is not the best safeguard for the current mechanism: Locking a local password is different from deleting the account and its data.

D:

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: Locking a local password is different from deleting the account and its data.

Question 77

You are responsible for a disposable RHEL10 training node. The required hands-on outcome is: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. Select the most appropriate implementation step.

  1. Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.
  2. Define the appropriate persistent fcontext mapping with `semanage fcontext` and reapply it using `restorecon`.
  3. Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload.
  4. Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot.

Explanation

Correct Answer

D:

Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot. This directly addresses the lab target: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. The underlying behavior is: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`. Verification: `getenforce` reports Enforcing after reboot and `sestatus` confirms the configured mode.

Incorrect Answers

A:

Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`. This is an appropriate step for a DIFFERENT exercise, specifically: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. It does not address the required lab state, whose mechanism is: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.

B:

Define the appropriate persistent fcontext mapping with `semanage fcontext` and reapply it using `restorecon`. This is an appropriate step for a DIFFERENT exercise, specifically: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. It does not address the required lab state, whose mechanism is: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.

C:

Inspect `firewall-cmd --get-active-zones`, add the approved port to the actual zone with a permanent rule and reload. This is an appropriate step for a DIFFERENT exercise, specifically: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. It does not address the required lab state, whose mechanism is: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.

Question 78

After a lab configuration change, verify: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. Which result most directly proves the desired system state?

  1. `getenforce` reports Enforcing after reboot and `sestatus` confirms the configured mode.
  2. SELinux context inspection shows read-only content separately from write-capable uploads and the application functions.
  3. `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.
  4. `ls -Z` shows suitable web content labels and Apache accesses the files under the approved mode.

Explanation

Correct Answer

A:

`getenforce` reports Enforcing after reboot and `sestatus` confirms the configured mode. This check confirms the expected effect of: Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot. It distinguishes the intended result from the original failure mechanism: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.

Incorrect Answers

B:

SELinux context inspection shows read-only content separately from write-capable uploads and the application functions. That verifies a separate lab task: A web application's content directory is assigned `httpd_sys_rw_content_t` everywhere even though only a small upload path requires writes. It does not validate the implementation required here: Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot.

C:

`stat` reports expected modes and the user's valid SSH connection works without insecure key exposure. That verifies a separate lab task: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. It does not validate the implementation required here: Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot.

D:

`ls -Z` shows suitable web content labels and Apache accesses the files under the approved mode. That verifies a separate lab task: A protected lab directory was copied from `/home` and now has inappropriate user-home SELinux contexts under `/var/www/html`. It does not validate the implementation required here: Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot.

Question 79

In an EX200-style practice lab, this condition exists: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. Which explanation correctly identifies the underlying issue?

  1. SSH private credentials require protected ownership and permissions distinct from public authorized keys.
  2. Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.
  3. SSH authentication methods are enforced by sshd configuration and authorized key material.
  4. `chcon` changes an inode label temporarily without updating the default file context database.

Explanation

Correct Answer

B:

Persistent SELinux policy mode comes from boot configuration, not just `setenforce`. This explains the task's initial state: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. The supported lab action is: Set `SELINUX=enforcing` in the reviewed configuration file and ensure the runtime mode is enforcing; perform a controlled reboot.

Incorrect Answers

A:

SSH private credentials require protected ownership and permissions distinct from public authorized keys. This mechanism applies to another scenario: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. The given lab state instead requires the more specific cause in the correct choice.

C:

SSH authentication methods are enforced by sshd configuration and authorized key material. This mechanism applies to another scenario: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. The given lab state instead requires the more specific cause in the correct choice.

D:

`chcon` changes an inode label temporarily without updating the default file context database. This mechanism applies to another scenario: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. The given lab state instead requires the more specific cause in the correct choice.

Question 80

After completing this practical task on a disposable RHEL10 training node: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. Which operational safeguard helps keep the result correct and safe?

  1. Record both fields in security posture checks and require a reboot verification for boot setting changes.
  2. Reapply default file contexts after moving service data into standard labeled directories.
  3. Check runtime and configured SELinux modes after policy changes.
  4. Check existing assignments before modifying SELinux port labels.

Explanation

Correct Answer

C:

Check runtime and configured SELinux modes after policy changes. This guards against recurrence of: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`. Confirm the lab's final state by: `getenforce` reports Enforcing after reboot and `sestatus` confirms the configured mode.

Incorrect Answers

A:

Record both fields in security posture checks and require a reboot verification for boot setting changes. That control is best suited to a separate scenario: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. It is not the best safeguard for the current mechanism: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.

B:

Reapply default file contexts after moving service data into standard labeled directories. That control is best suited to a separate scenario: A protected lab directory was copied from `/home` and now has inappropriate user-home SELinux contexts under `/var/www/html`. It is not the best safeguard for the current mechanism: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.

D:

Check existing assignments before modifying SELinux port labels. That control is best suited to a separate scenario: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. It is not the best safeguard for the current mechanism: Persistent SELinux policy mode comes from boot configuration, not just `setenforce`.