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 52

Question 510

After a lab configuration change, verify: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. Which result most directly proves the desired system state?

  1. A test from the management subnet succeeds and an unauthorized source is denied.
  2. `firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled.
  3. The port remains listed in permanent configuration and works after a controlled reboot.
  4. `firewall-cmd --zone=public --list-ports` contains 8443/tcp and a tested authorized client connects.

Explanation

Correct Answer

A:

A test from the management subnet succeeds and an unauthorized source is denied. This check confirms the expected effect of: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally. It distinguishes the intended result from the original failure mechanism: Global zone-wide service allowances are broader than a source-limited access requirement.

Incorrect Answers

B:

`firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled. That verifies a separate lab task: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It does not validate the implementation required here: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

C:

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: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

D:

`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 an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

Question 511

In an EX200-style practice lab, this condition exists: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. Which explanation correctly identifies the underlying issue?

  1. Named firewalld services encode documented port/protocol mappings more precisely than broad ranges.
  2. Global zone-wide service allowances are broader than a source-limited access requirement.
  3. Firewalld permissions do not start application daemons or guarantee boot persistence.
  4. The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`.

Explanation

Correct Answer

B:

Global zone-wide service allowances are broader than a source-limited access requirement. This explains the task's initial state: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. The supported lab action is: Use an appropriate reviewed rich rule or dedicated restricted zone for the approved `192.0.2.0/24` source, rather than opening HTTPS globally.

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.

C:

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.

D:

The local hosts database is consulted by the name-service switch based on `/etc/nsswitch.conf`. This mechanism applies to another scenario: A training host must resolve one intentionally private name without querying DNS while building a disconnected lab. The given lab state instead requires the more specific cause in the correct choice.

Question 512

After completing this practical task on a disposable RHEL10 training node: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. Which operational safeguard helps keep the result correct and safe?

  1. Confirm exact profile/interface names and console recovery before editing remote IP settings.
  2. Verify both address families and DNS behavior after connection changes.
  3. Test both allowed and denied source cases for management services.
  4. Review both runtime and permanent zone rules before closing firewall changes.

Explanation

Correct Answer

C:

Test both allowed and denied source cases for management services. This guards against recurrence of: Global zone-wide service allowances are broader than a source-limited access requirement. Confirm the lab's final state by: A test from the management subnet succeeds and an unauthorized source is denied.

Incorrect Answers

A:

Confirm exact profile/interface names and console recovery before editing remote IP settings. That control is best suited to a separate 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. It is not the best safeguard for the current mechanism: Global zone-wide service allowances are broader than a source-limited access requirement.

B:

Verify both address families and DNS behavior after connection changes. That control is best suited to a separate scenario: An IPv6-only lab application cannot listen because the host connection has no configured static IPv6 address. It is not the best safeguard for the current mechanism: Global zone-wide service allowances are broader than a source-limited access requirement.

D:

Review both runtime and permanent zone rules before closing firewall changes. That control is best suited to a separate scenario: An operator opens an authorized lab TCP port using only the runtime firewalld command, so access disappears after reboot. It is not the best safeguard for the current mechanism: Global zone-wide service allowances are broader than a source-limited access requirement.

Question 513

Lab exercise on an offline training clone: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. Which proposed RHEL 10 command or configuration action most directly achieves the required lab state?

  1. Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access.
  2. Use appropriate `useradd -r -u <approved-uid> -s /sbin/nologin svc_labs` with validated numeric availability.
  3. Ensure `/home/trainee1` ownership is `trainee1:trainee1` and set an approved restrictive mode such as `chmod 700 /home/trainee1`.
  4. Run `groupadd analysts` after checking the group name is not already in use.

Explanation

Correct Answer

A:

Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access. This directly addresses the lab target: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. The underlying behavior is: Group membership may authorize privileged sudo actions through existing policy. Verification: `id contractor1` excludes `wheel` and the account does not gain broad sudo rights.

Incorrect Answers

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: Group membership may authorize privileged sudo actions through existing policy.

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: Group membership may authorize privileged sudo actions through existing policy.

D:

Run `groupadd analysts` after checking the group name is not already in use. This is an appropriate step for a DIFFERENT exercise, specifically: A project team needs a new local group `analysts` to own shared reports. It does not address the required lab state, whose mechanism is: Group membership may authorize privileged sudo actions through existing policy.

Question 514

In a hands-on RHCSA practice VM, the assigned outcome was: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. What specific verification would demonstrate the target state?

  1. The password-change status succeeds and the user can authenticate with the approved new secret.
  2. `id contractor1` excludes `wheel` and the account does not gain broad sudo rights.
  3. `getent group analysts` returns the new group record with a local GID.
  4. `id trainee1` no longer includes `analysts`, while the primary GID remains unchanged.

Explanation

Correct Answer

B:

`id contractor1` excludes `wheel` and the account does not gain broad sudo rights. This check confirms the expected effect of: Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access. It distinguishes the intended result from the original failure mechanism: Group membership may authorize privileged sudo actions through existing policy.

Incorrect Answers

A:

The password-change status succeeds and the user can authenticate with the approved new secret. That verifies a separate lab task: A training account needs its password reset by an authorized administrator without printing the new secret in a shell command. It does not validate the implementation required here: Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access.

C:

`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: Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access.

D:

`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: Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access.

Question 515

A trainee is diagnosing: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. Which root cause should they recognize before changing the system?

  1. Account expiration is separate from password expiration or maximum password age.
  2. Primary group and supplementary group settings have different semantics.
  3. Group membership may authorize privileged sudo actions through existing policy.
  4. A process inherits its group credentials when its session begins and may not pick up group changes dynamically.

Explanation

Correct Answer

C:

Group membership may authorize privileged sudo actions through existing policy. This explains the task's initial state: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. The supported lab action is: Remove the unintended supplementary `wheel` membership with `gpasswd -d contractor1 wheel` after verifying access.

Incorrect Answers

A:

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.

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:

A process inherits its group credentials when its session begins and may not pick up group changes dynamically. This mechanism applies to another scenario: 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. The given lab state instead requires the more specific cause in the correct choice.

Question 516

For this Linux administration lab: A contractor has been added to `wheel` by mistake and can run arbitrary privileged commands. Which safety and lifecycle check best prevents the same problem returning?

  1. Use approved secret distribution and require rotation at initial login when appropriate.
  2. Always validate sudoers changes with `visudo -c` before ending the recovery session.
  3. Plan login, home, file ownership and scheduled-task references as a single account migration.
  4. Review administrative group memberships on every role transfer.

Explanation

Correct Answer

D:

Review administrative group memberships on every role transfer. This guards against recurrence of: Group membership may authorize privileged sudo actions through existing policy. Confirm the lab's final state by: `id contractor1` excludes `wheel` and the account does not gain broad sudo rights.

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: Group membership may authorize privileged sudo actions through existing policy.

B:

Always validate sudoers changes with `visudo -c` before ending the recovery session. That control is best suited to a separate scenario: An operator edits `/etc/sudoers` using an ordinary editor and introduces invalid syntax, breaking privilege escalation. It is not the best safeguard for the current mechanism: Group membership may authorize privileged sudo actions through existing policy.

C:

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: Group membership may authorize privileged sudo actions through existing policy.

Question 517

A student working on a local virtualization classroom receives this assignment: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. Which answer gives the correct practical approach?

  1. Inspect `ausearch -m AVC -ts recent` and `ls -Z` or `journalctl` before changing SELinux mode.
  2. Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population.
  3. Define the appropriate persistent fcontext mapping with `semanage fcontext` and reapply it using `restorecon`.
  4. Use `setenforce 0` only as a time-bounded authorized lab diagnostic, inspect `getenforce`, and restore enforcing with `setenforce 1`.

Explanation

Correct Answer

B:

Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population. This directly addresses the lab target: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. The underlying behavior is: SSH authentication methods are enforced by sshd configuration and authorized key material. Verification: Key-based login succeeds while a controlled password-only attempt fails without locking out the authorized admin.

Incorrect Answers

A:

Inspect `ausearch -m AVC -ts recent` and `ls -Z` or `journalctl` before changing SELinux mode. This is an appropriate step for a DIFFERENT exercise, specifically: A lab administrator disables SELinux to stop web errors without checking whether a label denial caused them. It does not address the required lab state, whose mechanism is: SSH authentication methods are enforced by sshd configuration and authorized key material.

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 authentication methods are enforced by sshd configuration and authorized key material.

D:

Use `setenforce 0` only as a time-bounded authorized lab diagnostic, inspect `getenforce`, and restore enforcing with `setenforce 1`. This is an appropriate step for a DIFFERENT exercise, specifically: An administrator temporarily changes SELinux to permissive mode for diagnostics and believes it will remain so after reboot. It does not address the required lab state, whose mechanism is: SSH authentication methods are enforced by sshd configuration and authorized key material.

Question 518

You have attempted this task on a local virtualization classroom: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. Which command output or observation best confirms its success?

  1. The Boolean remains on after reboot and `getsebool` confirms the value.
  2. `firewall-cmd --permanent --zone=public --list-services` includes HTTPS and the state survives reboot.
  3. Key-based login succeeds while a controlled password-only attempt fails without locking out the authorized admin.
  4. `getenforce` shows permissive during the test, then enforcing after restoration without assuming persistence.

Explanation

Correct Answer

C:

Key-based login succeeds while a controlled password-only attempt fails without locking out the authorized admin. This check confirms the expected effect of: Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population. It distinguishes the intended result from the original failure mechanism: SSH authentication methods are enforced by sshd configuration and authorized key material.

Incorrect Answers

A:

The Boolean remains on after reboot and `getsebool` confirms the value. That verifies a separate lab task: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. It does not validate the implementation required here: Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population.

B:

`firewall-cmd --permanent --zone=public --list-services` includes HTTPS and the state survives reboot. That verifies a separate lab task: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. It does not validate the implementation required here: Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population.

D:

`getenforce` shows permissive during the test, then enforcing after restoration without assuming persistence. That verifies a separate lab task: An administrator temporarily changes SELinux to permissive mode for diagnostics and believes it will remain so after reboot. It does not validate the implementation required here: Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population.

Question 519

Troubleshoot the following RHEL 10 lab situation: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. Identify the key Linux mechanism behind the issue.

  1. SELinux access denials have specific type or policy causes that global disablement obscures.
  2. DAC mode bits can allow unauthorized modification even if service function appears correct.
  3. SELinux mandatory access control cannot be fixed by making ordinary Unix permissions world writable.
  4. SSH authentication methods are enforced by sshd configuration and authorized key material.

Explanation

Correct Answer

D:

SSH authentication methods are enforced by sshd configuration and authorized key material. This explains the task's initial state: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. The supported lab action is: Install an approved public key in `authorized_keys`, test batch SSH, then adjust the reviewed `sshd_config` policy to disable passwords for the intended population.

Incorrect Answers

A:

SELinux access denials have specific type or policy causes that global disablement obscures. This mechanism applies to another scenario: A lab administrator disables SELinux to stop web errors without checking whether a label denial caused them. The given lab state instead requires the more specific cause in the correct choice.

B:

DAC mode bits can allow unauthorized modification even if service function appears correct. This mechanism applies to another scenario: A user accidentally gives write permission to everyone on an application's configuration file. The given lab state instead requires the more specific cause in the correct choice.

C:

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.

Question 520

Following lab verification, document the preventive or persistence-oriented procedure for: A lab SSH account still accepts password-only access while the approved policy requires authorized public-key authentication. Which practice is most suitable?

  1. Keep a verified break-glass console path before tightening authentication methods.
  2. Test positive and negative access after SSH authorization changes.
  3. Use policy-backed fcontext mappings for nonstandard service directories.
  4. Verify persistence and remove temporary diagnostic firewall permits.

Explanation

Correct Answer

A:

Keep a verified break-glass console path before tightening authentication methods. This guards against recurrence of: SSH authentication methods are enforced by sshd configuration and authorized key material. Confirm the lab's final state by: Key-based login succeeds while a controlled password-only attempt fails without locking out the authorized admin.

Incorrect Answers

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: SSH authentication methods are enforced by sshd configuration and authorized key material.

C:

Use policy-backed fcontext mappings for nonstandard service directories. That control is best suited to a separate scenario: A temporary `chcon` label change makes a lab web file work, but `restorecon` later reverts it and the outage returns. It is not the best safeguard for the current mechanism: SSH authentication methods are enforced by sshd configuration and authorized key material.

D:

Verify persistence and remove temporary diagnostic firewall permits. That control is best suited to a separate scenario: A firewall change is tested using only a runtime rule, but an administrator assumes it will be present after restart. It is not the best safeguard for the current mechanism: SSH authentication methods are enforced by sshd configuration and authorized key material.