Red Hat System Administration I RH124 – RHEL10 — Lesson 2: Users, Groups, Permissions, Processes, Packages, and Services

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing account administration and permission models.
• Implement and validate process control, RPM and DNF, and systemd services using reviewable evidence.
• Evaluate the condition where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ and select a proportionate corrective response.

Detailed Topics

• account administration applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• permission models applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• process control applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• RPM and DNF applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• systemd services applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a new systems administrator preparing and operating a standardized RHEL workstation and server environment. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the RHEL foundational administration workbook, command evidence, configuration checklist, and support runbook. It also tests the exception where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ.

Hands-On Exercise

Complete a controlled Red Hat exercise covering Users, Groups, Permissions, Processes, Packages, and Services and preserve the verified result in the RHEL foundational administration workbook, command evidence, configuration checklist, and support runbook.

1. Confirm scope, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording commands, settings, outputs, events, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, rollback, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences account administration.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the RHEL foundational administration workbook, command evidence, configuration checklist, and support runbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check prerequisites, identity, configuration order, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ” as a hypothesis until commands, logs, settings, and retest outcomes confirm the cause.

Validation Checklist

• Required platform components, identities, permissions, settings, and dependencies are present.
• The RHEL foundational administration workbook, command evidence, configuration checklist, and support runbook connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Users, Groups, Permissions, Processes, Packages, and Services, explain the resulting platform behavior, and defend the outcome through the RHEL foundational administration workbook, command evidence, configuration checklist, and support runbook.