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 48

Question 470

You have attempted this task on a local virtualization classroom: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. Which command output or observation best confirms its success?

  1. After reconnect or reboot `nmcli con show` and `ip addr` still report the address.
  2. The profile reflects changed settings and existing remote management remains recoverable.
  3. An authorized client connects and the correct zone reports the service or port.
  4. A test from the management subnet succeeds and an unauthorized source is denied.

Explanation

Correct Answer

C:

An authorized client connects and the correct zone reports the service or port. This check confirms the expected effect of: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone. It distinguishes the intended result from the original failure mechanism: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

Incorrect Answers

A:

After reconnect or reboot `nmcli con show` and `ip addr` still report the address. That verifies a separate lab task: A technician adds an IPv4 address with `ip addr add`, but it disappears after reboot. It does not validate the implementation required here: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

B:

The profile reflects changed settings and existing remote management remains recoverable. That verifies a separate lab task: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. It does not validate the implementation required here: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

D:

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: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

Question 471

Troubleshoot the following RHEL 10 lab situation: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. Identify the key Linux mechanism behind the issue.

  1. Firewalld permissions do not start application daemons or guarantee boot persistence.
  2. NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary.
  3. Router advertisements can populate routes independently of static interface addresses.
  4. Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

Explanation

Correct Answer

D:

Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default. This explains the task's initial state: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. The supported lab action is: Identify interface zone with `firewall-cmd --get-active-zones`, then apply the approved rule to the interface's actual zone.

Incorrect Answers

A:

Firewalld permissions do not start application daemons or guarantee boot persistence. This mechanism applies to another scenario: A web service must start after every reboot, but `ss -tln` shows its listener only after manual execution. The given lab state instead requires the more specific cause in the correct choice.

B:

NetworkManager applies connection profile changes; restarting the entire stack is rarely necessary. This mechanism applies to another scenario: A new network connection profile was edited but the operator attempts an unsafe remote restart of all networking services. The given lab state instead requires the more specific cause in the correct choice.

C:

Router advertisements can populate routes independently of static interface addresses. This mechanism applies to another scenario: An IPv6 connection receives a default route from router advertisements when policy requires the test host to use only a specified local IPv6 subnet. The given lab state instead requires the more specific cause in the correct choice.

Question 472

Following lab verification, document the preventive or persistence-oriented procedure for: A firewall rule was added to the default zone, but the application's NIC is assigned to a different active zone. Which practice is most suitable?

  1. Capture zone-to-interface bindings when deploying network services.
  2. Confirm unit enablement, listener, zone and end-to-end client response together.
  3. Test both allowed and denied source cases for management services.
  4. Use minimum required allowed services while retaining firewalld enforcement.

Explanation

Correct Answer

A:

Capture zone-to-interface bindings when deploying network services. This guards against recurrence of: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default. Confirm the lab's final state by: An authorized client connects and the correct zone reports the service or port.

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: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

C:

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: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

D:

Use minimum required allowed services while retaining firewalld enforcement. That control is best suited to a separate scenario: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It is not the best safeguard for the current mechanism: Firewall policy is evaluated in the context of the active interface or source zone, not an assumed default.

Question 473

On a nonproduction Linux administration sandbox, perform the following practical task: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. Which action should be carried out after confirming the lab prerequisites?

  1. Use `usermod -g appops svc_labs` after ensuring the target group exists and reviewing owned files.
  2. Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.
  3. Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group.
  4. Use `usermod -l correctedname oldname` and separately migrate home path if required after ensuring no active sessions.

Explanation

Correct Answer

C:

Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group. This directly addresses the lab target: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. The underlying behavior is: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive. Verification: `sudo -l -U technician` shows the approved command only; unrelated root commands remain denied.

Incorrect Answers

A:

Use `usermod -g appops svc_labs` after ensuring the target group exists and reviewing owned files. This is an appropriate step for a DIFFERENT exercise, specifically: A team requires a default primary group different from the user-private group created with the account. It does not address the required lab state, whose mechanism is: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

B:

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: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

D:

Use `usermod -l correctedname oldname` and separately migrate home path if required after ensuring no active sessions. This is an appropriate step for a DIFFERENT exercise, specifically: A user account has a misspelled login name but should keep its existing UID and home ownership. It does not address the required lab state, whose mechanism is: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

Question 474

The lab examiner asks for evidence after this assignment: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. What is the decisive verification step?

  1. `id -gn svc_labs` reports `appops` and application file permissions remain appropriate.
  2. `chage -l contractor1` shows the intended account expiration date.
  3. `getent passwd trainee1` shows the expected shell and `/home/trainee1` exists.
  4. `sudo -l -U technician` shows the approved command only; unrelated root commands remain denied.

Explanation

Correct Answer

D:

`sudo -l -U technician` shows the approved command only; unrelated root commands remain denied. This check confirms the expected effect of: Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group. It distinguishes the intended result from the original failure mechanism: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

Incorrect Answers

A:

`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: Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group.

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: Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group.

C:

`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: Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group.

Question 475

A training host has this situation: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. Which system behavior best explains the original failure or risk?

  1. Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.
  2. Password expiration policy is separate from the last time a password was changed.
  3. Linux group creation establishes a named group but does not automatically add users or set file ownership.
  4. The shell field controls the program started at login and can intentionally block interactive access.

Explanation

Correct Answer

A:

Sudoers controls command-specific privilege escalation and its syntax is security-sensitive. This explains the task's initial state: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. The supported lab action is: Create a validated rule using `visudo -f /etc/sudoers.d/lab-restart` for the exact command and user/group.

Incorrect Answers

B:

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.

C:

Linux group creation establishes a named group but does not automatically add users or set file ownership. This mechanism applies to another scenario: A project team needs a new local group `analysts` to own shared reports. The given lab state instead requires the more specific cause in the correct choice.

D:

The shell field controls the program started at login and can intentionally block interactive access. This mechanism applies to another scenario: A lab user was mistakenly assigned `/bin/false` as login shell and cannot open an authorized interactive session. The given lab state instead requires the more specific cause in the correct choice.

Question 476

A student has implemented the following configuration: An admin must grant a named technician narrowly scoped restart rights for a lab service without adding them to full wheel privileges. What repeatable control best reduces regressions or unsafe changes?

  1. Plan login, home, file ownership and scheduled-task references as a single account migration.
  2. Use least-privilege rules, syntax checking and specific command paths.
  3. Follow approved account naming and home provisioning standards.
  4. Revalidate group grants during user role changes and offboarding.

Explanation

Correct Answer

B:

Use least-privilege rules, syntax checking and specific command paths. This guards against recurrence of: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive. Confirm the lab's final state by: `sudo -l -U technician` shows the approved command only; unrelated root commands remain denied.

Incorrect Answers

A:

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: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

C:

Follow approved account naming and home provisioning standards. That control is best suited to a separate scenario: A new lab operator needs a local account with a home directory and normal login shell. It is not the best safeguard for the current mechanism: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

D:

Revalidate group grants during user role changes and offboarding. That control is best suited to a separate scenario: A trainee is no longer authorized for the `analysts` supplemental group, but should retain their primary group. It is not the best safeguard for the current mechanism: Sudoers controls command-specific privilege escalation and its syntax is security-sensitive.

Question 477

You are responsible for a test RHEL10 instance. The required hands-on outcome is: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. Select the most appropriate implementation step.

  1. After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping.
  2. Set `umask 077` in the sensitive workflow before creating the secret fixture.
  3. Define the appropriate persistent fcontext mapping with `semanage fcontext` and reapply it using `restorecon`.
  4. Use `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner.

Explanation

Correct Answer

D:

Use `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner. This directly addresses the lab target: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. The underlying behavior is: SSH private credentials require protected ownership and permissions distinct from public authorized keys. Verification: `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.

Incorrect Answers

A:

After confirming it is safe and approved, use `semanage port -m -t http_port_t -p tcp 8088` for the existing mapping. This is an appropriate step for a DIFFERENT exercise, specifically: An existing TCP port is assigned to the wrong SELinux port type and `semanage port -a` fails because the port already exists. It does not address the required lab state, whose mechanism is: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

B:

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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

C:

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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

Question 478

After a lab configuration change, verify: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. Which result most directly proves the desired system state?

  1. `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.
  2. Current and configured SELinux modes converge to the intended approved state after reboot.
  3. The target zone contains the rule, the intended client connects and unrelated sources remain denied if separately restricted.
  4. The service accesses the file with restrictive DAC permissions and the correct SELinux label while enforcing remains active.

Explanation

Correct Answer

A:

`stat` reports expected modes and the user's valid SSH connection works without insecure key exposure. This check confirms the expected effect of: Use `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner. It distinguishes the intended result from the original failure mechanism: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

Incorrect Answers

B:

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 `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner.

C:

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 `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner.

D:

The service accesses the file with restrictive DAC permissions and the correct SELinux label while enforcing remains active. That verifies a separate lab task: A custom service path is mislabeled and a technician repeatedly applies `chmod 777` without resolving access denials. It does not validate the implementation required here: Use `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner.

Question 479

In an EX200-style practice lab, this condition exists: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. Which explanation correctly identifies the underlying issue?

  1. SELinux port types control service bind permission independently of firewalld.
  2. SSH private credentials require protected ownership and permissions distinct from public authorized keys.
  3. SELinux Booleans can authorize specific service behavior without disabling the entire MAC policy.
  4. `setenforce` changes runtime state while SELinux's configured boot mode is separate.

Explanation

Correct Answer

B:

SSH private credentials require protected ownership and permissions distinct from public authorized keys. This explains the task's initial state: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. The supported lab action is: Use `chmod 600 /home/trainee1/.ssh/id_ed25519` and `chmod 700 /home/trainee1/.ssh` under the account owner.

Incorrect Answers

A:

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.

C:

SELinux Booleans can authorize specific service behavior without disabling the entire MAC policy. This mechanism applies to another scenario: An application hosted by Apache needs outbound database connections but SELinux policy denies them even with network routing functional. The given lab state instead requires the more specific cause in the correct choice.

D:

`setenforce` changes runtime state while SELinux's configured boot mode is separate. This mechanism applies to another scenario: An administrator temporarily changes SELinux to permissive mode for diagnostics and believes it will remain so after reboot. The given lab state instead requires the more specific cause in the correct choice.

Question 480

After completing this practical task on a test RHEL10 instance: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. Which operational safeguard helps keep the result correct and safe?

  1. Check active zone, SELinux port permission and service listener together.
  2. Reapply default file contexts after moving service data into standard labeled directories.
  3. Provision and rotate private keys under managed mode and ownership controls.
  4. Check runtime and configured SELinux modes after policy changes.

Explanation

Correct Answer

C:

Provision and rotate private keys under managed mode and ownership controls. This guards against recurrence of: SSH private credentials require protected ownership and permissions distinct from public authorized keys. Confirm the lab's final state by: `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.

Incorrect Answers

A:

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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.

D:

Check runtime and configured SELinux modes after policy changes. That control is best suited to a separate scenario: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. It is not the best safeguard for the current mechanism: SSH private credentials require protected ownership and permissions distinct from public authorized keys.