Oracle Linux System Administration II — Lesson 4: Users, SELinux, Firewalls, Monitoring, Troubleshooting, and Runbook

Technical Scope

• users, groups, sudo, PAM awareness, limits, and access review
• SELinux contexts, booleans, policy troubleshooting, and restorecon
• firewalld zones, services, ports, rich rules, and exposure validation
• process, memory, CPU, disk, logs, incident diagnosis, and administration runbook

Instructor Demonstration

Demonstrate users, groups, sudo, PAM awareness, limits, and access review within a production Oracle Linux server prepared for application hosting with resilient storage, controlled services, secure access, observable performance, and documented recovery, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering SELinux contexts, booleans, policy troubleshooting, and restorecon and firewalld zones, services, ports, rich rules, and exposure validation, then test a failure, exception, or business-control scenario involving process, memory, CPU, disk, logs, incident diagnosis, and administration runbook.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The Users, SELinux, Firewalls, Monitoring, Troubleshooting, and Runbook result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in users, groups, sudo, PAM awareness, limits, and access review, SELinux contexts, booleans, policy troubleshooting, and restorecon, firewalld zones, services, ports, rich rules, and exposure validation, or process, memory, CPU, disk, logs, incident diagnosis, and administration runbook without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for Users, SELinux, Firewalls, Monitoring, Troubleshooting, and Runbook and defend the result with documented evidence.