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 24

Question 230

You have attempted this task on a local virtualization classroom: A NetworkManager profile is stored on disk but is not automatically activated after reboot. Which command output or observation best confirms its success?

  1. The port remains listed in permanent configuration and works after a controlled reboot.
  2. An authorized client connects and the correct zone reports the service or port.
  3. `nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot.
  4. `nmcli -g IP4.ADDRESS,IP4.GATEWAY con show --active lablan` and `ip -4 addr` show the intended address and gateway.

Explanation

Correct Answer

C:

`nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot. This check confirms the expected effect of: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe. It distinguishes the intended result from the original failure mechanism: Persisted connection configuration can remain inactive when autoconnect is disabled.

Incorrect Answers

A:

The port remains listed in permanent configuration and works after a controlled reboot. That verifies a separate lab task: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. It does not validate the implementation required here: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.

B:

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: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.

D:

`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: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.

Question 231

Troubleshoot the following RHEL 10 lab situation: A NetworkManager profile is stored on disk but is not automatically activated after reboot. Identify the key Linux mechanism behind the issue.

  1. Named firewalld services encode documented port/protocol mappings more precisely than broad ranges.
  2. `ip` runtime configuration alone does not update NetworkManager's stored connection profile.
  3. A valid local interface address does not automatically provide off-subnet routing.
  4. Persisted connection configuration can remain inactive when autoconnect is disabled.

Explanation

Correct Answer

D:

Persisted connection configuration can remain inactive when autoconnect is disabled. This explains the task's initial state: A NetworkManager profile is stored on disk but is not automatically activated after reboot. The supported lab action is: Set `nmcli connection modify lablan connection.autoconnect yes` and activate it when safe.

Incorrect Answers

A:

Named firewalld services encode documented port/protocol mappings more precisely than broad ranges. This mechanism applies to another scenario: A standard `http` service should be allowed through firewalld, but the operator adds a broad arbitrary port range. The given lab state instead requires the more specific cause in the correct choice.

B:

`ip` runtime configuration alone does not update NetworkManager's stored connection profile. This mechanism applies to another scenario: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. The given lab state instead requires the more specific cause in the correct choice.

C:

A valid local interface address does not automatically provide off-subnet routing. This mechanism applies to another scenario: The lab interface is assigned the right IP but the host cannot reach an off-subnet gateway due to an incorrect default route. The given lab state instead requires the more specific cause in the correct choice.

Question 232

Following lab verification, document the preventive or persistence-oriented procedure for: A NetworkManager profile is stored on disk but is not automatically activated after reboot. Which practice is most suitable?

  1. Check autoconnect and active link state on every server network profile.
  2. Verify route lookup for representative destinations during network acceptance.
  3. Audit both DNS source and search domains when moving between networks.
  4. Set the static hostname and confirm it is resolvable under the site's DNS plan.

Explanation

Correct Answer

A:

Check autoconnect and active link state on every server network profile. This guards against recurrence of: Persisted connection configuration can remain inactive when autoconnect is disabled. Confirm the lab's final state by: `nmcli -g connection.autoconnect connection show lablan` returns yes and `nmcli connection show --active` lists it after reboot.

Incorrect Answers

B:

Verify route lookup for representative destinations during network acceptance. That control is best suited to a separate scenario: The lab interface is assigned the right IP but the host cannot reach an off-subnet gateway due to an incorrect default route. It is not the best safeguard for the current mechanism: Persisted connection configuration can remain inactive when autoconnect is disabled.

C:

Audit both DNS source and search domains when moving between networks. That control is best suited to a separate scenario: A host resolves internal names through an obsolete DNS server even though its IPv4 address is correct. It is not the best safeguard for the current mechanism: Persisted connection configuration can remain inactive when autoconnect is disabled.

D:

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: Persisted connection configuration can remain inactive when autoconnect is disabled.

Question 233

On a nonproduction Linux administration sandbox, perform the following practical task: A project team needs a new local group `analysts` to own shared reports. Which action should be carried out after confirming the lab prerequisites?

  1. Start a new login session or use `newgrp analysts` under approved conditions and verify with `id`.
  2. Use appropriate `useradd -r -u <approved-uid> -s /sbin/nologin svc_labs` with validated numeric availability.
  3. Run `groupadd analysts` after checking the group name is not already in use.
  4. Use `gpasswd -d trainee1 analysts` after confirming group and account identity.

Explanation

Correct Answer

C:

Run `groupadd analysts` after checking the group name is not already in use. This directly addresses the lab target: A project team needs a new local group `analysts` to own shared reports. The underlying behavior is: Linux group creation establishes a named group but does not automatically add users or set file ownership. Verification: `getent group analysts` returns the new group record with a local GID.

Incorrect Answers

A:

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: Linux group creation establishes a named group but does not automatically add users or set file ownership.

B:

Use appropriate `useradd -r -u <approved-uid> -s /sbin/nologin svc_labs` with validated numeric availability. This is an appropriate step for a DIFFERENT exercise, specifically: A service account must have a fixed UID and noninteractive shell for an isolated application, not a general human login. It does not address the required lab state, whose mechanism is: Linux group creation establishes a named group but does not automatically add users or set file ownership.

D:

Use `gpasswd -d trainee1 analysts` after confirming group and account identity. This is an appropriate step for a DIFFERENT exercise, specifically: A trainee is no longer authorized for the `analysts` supplemental group, but should retain their primary group. It does not address the required lab state, whose mechanism is: Linux group creation establishes a named group but does not automatically add users or set file ownership.

Question 234

The lab examiner asks for evidence after this assignment: A project team needs a new local group `analysts` to own shared reports. What is the decisive verification step?

  1. `getent passwd trainee1` shows the expected shell and `/home/trainee1` exists.
  2. `id -gn svc_labs` reports `appops` and application file permissions remain appropriate.
  3. `chage -l contractor1` shows the intended account expiration date.
  4. `getent group analysts` returns the new group record with a local GID.

Explanation

Correct Answer

D:

`getent group analysts` returns the new group record with a local GID. This check confirms the expected effect of: Run `groupadd analysts` after checking the group name is not already in use. It distinguishes the intended result from the original failure mechanism: Linux group creation establishes a named group but does not automatically add users or set file ownership.

Incorrect Answers

A:

`getent passwd trainee1` shows the expected shell and `/home/trainee1` exists. That verifies a separate lab task: A new lab operator needs a local account with a home directory and normal login shell. It does not validate the implementation required here: Run `groupadd analysts` after checking the group name is not already in use.

B:

`id -gn svc_labs` reports `appops` and application file permissions remain appropriate. That verifies a separate lab task: A team requires a default primary group different from the user-private group created with the account. It does not validate the implementation required here: Run `groupadd analysts` after checking the group name is not already in use.

C:

`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: Run `groupadd analysts` after checking the group name is not already in use.

Question 235

A training host has this situation: A project team needs a new local group `analysts` to own shared reports. Which system behavior best explains the original failure or risk?

  1. Linux group creation establishes a named group but does not automatically add users or set file ownership.
  2. Deleting a local account and its home is destructive and distinct from locking it.
  3. Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.
  4. Renaming a login does not automatically guarantee home directory renaming in every workflow.

Explanation

Correct Answer

A:

Linux group creation establishes a named group but does not automatically add users or set file ownership. This explains the task's initial state: A project team needs a new local group `analysts` to own shared reports. The supported lab action is: Run `groupadd analysts` after checking the group name is not already in use.

Incorrect Answers

B:

Deleting a local account and its home is destructive and distinct from locking it. This mechanism applies to another scenario: An account remains in `/etc/passwd` after project completion and the lab task explicitly authorizes permanent removal with its home. The given lab state instead requires the more specific cause in the correct choice.

C:

Sudoers controls command-specific privilege escalation and its syntax is security-sensitive. This mechanism applies to another scenario: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. The given lab state instead requires the more specific cause in the correct choice.

D:

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.

Question 236

A student has implemented the following configuration: A project team needs a new local group `analysts` to own shared reports. What repeatable control best reduces regressions or unsafe changes?

  1. Use approved secret distribution and require rotation at initial login when appropriate.
  2. Verify membership and filesystem permissions after defining access groups.
  3. Review approved shells during interactive account provisioning.
  4. Apply secure home defaults and review them at account creation.

Explanation

Correct Answer

B:

Verify membership and filesystem permissions after defining access groups. This guards against recurrence of: Linux group creation establishes a named group but does not automatically add users or set file ownership. Confirm the lab's final state by: `getent group analysts` returns the new group record with a local GID.

Incorrect Answers

A:

Use approved secret distribution and require rotation at initial login when appropriate. That control is best suited to a separate scenario: A training account needs its password reset by an authorized administrator without printing the new secret in a shell command. It is not the best safeguard for the current mechanism: Linux group creation establishes a named group but does not automatically add users or set file ownership.

C:

Review approved shells during interactive account provisioning. That control is best suited to a separate scenario: A lab user was mistakenly assigned `/bin/false` as login shell and cannot open an authorized interactive session. It is not the best safeguard for the current mechanism: Linux group creation establishes a named group but does not automatically add users or set file ownership.

D:

Apply secure home defaults and review them at account creation. That control is best suited to a separate scenario: A new user must have a private home directory rather than inherited group-read access. It is not the best safeguard for the current mechanism: Linux group creation establishes a named group but does not automatically add users or set file ownership.

Question 237

You are responsible for a test RHEL10 instance. The required hands-on outcome is: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. Select the most appropriate implementation step.

  1. Use `firewall-cmd --zone=public --add-service=https --permanent` after review, followed by `firewall-cmd --reload`.
  2. Use `ls -Z`, `matchpathcon` and AVC logs to identify labeling, then correct the relevant persistent context mapping and run `restorecon`.
  3. Set `chmod 640 /etc/labapp.conf` with approved root ownership and a designated service group.
  4. After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping.

Explanation

Correct Answer

D:

After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping. This directly addresses the lab target: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. The underlying behavior is: Port type modifications and adding new mappings are different policy operations. Verification: `semanage port -l` shows the revised mapping without duplicate records.

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: Port type modifications and adding new mappings are different policy operations.

B:

Use `ls -Z`, `matchpathcon` and AVC logs to identify labeling, then correct the relevant persistent context mapping and run `restorecon`. This is an appropriate step for a DIFFERENT exercise, specifically: A custom service path is mislabeled and a technician repeatedly applies `chmod 777` without resolving access denials. It does not address the required lab state, whose mechanism is: Port type modifications and adding new mappings are different policy operations.

C:

Set `chmod 640 /etc/labapp.conf` with approved root ownership and a designated service group. This is an appropriate step for a DIFFERENT exercise, specifically: A user accidentally gives write permission to everyone on an application's configuration file. It does not address the required lab state, whose mechanism is: Port type modifications and adding new mappings are different policy operations.

Question 238

After a lab configuration change, verify: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. Which result most directly proves the desired system state?

  1. `semanage port -l` shows the revised mapping without duplicate records.
  2. SELinux context inspection shows read-only content separately from write-capable uploads and the application functions.
  3. A known private-key client logs in as the expected user while unauthorized keys fail.
  4. `semanage port -l` lists 8088 for `http_port_t` and the daemon binds without the denial.

Explanation

Correct Answer

A:

`semanage port -l` shows the revised mapping without duplicate records. This check confirms the expected effect of: After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping. It distinguishes the intended result from the original failure mechanism: Port type modifications and adding new mappings are different policy operations.

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: After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping.

C:

A known private-key client logs in as the expected user while unauthorized keys fail. That verifies a separate lab task: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. It does not validate the implementation required here: After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping.

D:

`semanage port -l` lists 8088 for `http_port_t` and the daemon binds without the denial. That verifies a separate lab task: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. It does not validate the implementation required here: After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping.

Question 239

In an EX200-style practice lab, this condition exists: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. Which explanation correctly identifies the underlying issue?

  1. SELinux mandatory access control cannot be fixed by making ordinary Unix permissions world writable.
  2. Port type modifications and adding new mappings are different policy operations.
  3. SSH authentication methods are enforced by sshd configuration and authorized key material.
  4. SELinux port types control service bind permission independently of firewalld.

Explanation

Correct Answer

B:

Port type modifications and adding new mappings are different policy operations. This explains the task's initial state: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. The supported lab action is: After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping.

Incorrect Answers

A:

SELinux mandatory access control cannot be fixed by making ordinary Unix permissions world writable. This mechanism applies to another scenario: A custom service path is mislabeled and a technician repeatedly applies `chmod 777` without resolving access denials. 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:

SELinux port types control service bind permission independently of firewalld. This mechanism applies to another scenario: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. The given lab state instead requires the more specific cause in the correct choice.

Question 240

After completing this practical task on a test RHEL10 instance: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. Which operational safeguard helps keep the result correct and safe?

  1. Verify port-label assignment and firewall exposure separately for nonstandard listener ports.
  2. Test positive and negative access after SSH authorization changes.
  3. Check existing assignments before modifying SELinux port labels.
  4. Check active zone, SELinux port permission and service listener together.

Explanation

Correct Answer

C:

Check existing assignments before modifying SELinux port labels. This guards against recurrence of: Port type modifications and adding new mappings are different policy operations. Confirm the lab's final state by: `semanage port -l` shows the revised mapping without duplicate records.

Incorrect Answers

A:

Verify port-label assignment and firewall exposure separately for nonstandard listener ports. That control is best suited to a separate scenario: A test web daemon is configured to listen on TCP 8088 but SELinux blocks binding despite a matching firewall rule. It is not the best safeguard for the current mechanism: Port type modifications and adding new mappings are different policy operations.

B:

Test positive and negative access after SSH authorization changes. That control is best suited to a separate scenario: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. It is not the best safeguard for the current mechanism: Port type modifications and adding new mappings are different policy operations.

D:

Check active zone, SELinux port permission and service listener together. That control is best suited to a separate scenario: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. It is not the best safeguard for the current mechanism: Port type modifications and adding new mappings are different policy operations.