Certified Linux Foundations (PECB) — Lesson 2: Files, Directories, Permissions, Users, Groups, Processes, and Packages

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping files, directories, permissions, users, groups, processes, and packages.
• Apply a practical workflow and create a reviewable permissions and process administration checklist.
• Evaluate the exception where a package update disrupts a dependent service and determine proportionate follow-up.

Detailed Topics

• Files applied to the course scenario and expected evidence.
• Directories applied to the course scenario and expected evidence.
• Permissions applied to the course scenario and expected evidence.
• Users applied to the course scenario and expected evidence.
• Groups applied to the course scenario and expected evidence.
• Processes applied to the course scenario and expected evidence.
• and Packages applied to the course scenario and expected evidence.

Instructor Demonstration

The instructor traces a case involving a junior operations team supporting Linux servers used for web, database, automation, and internal services. The demonstration links decisions to objective evidence, records the result in permissions and process administration checklist, and tests the condition where a package update disrupts a dependent service.

Hands-On Exercise

Complete a controlled exercise covering Files, Directories, Permissions, Users, Groups, Processes, and Packages. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in permissions and process administration checklist.

1. Define the objective, boundaries, stakeholders, criteria, and expected work product.
2. Perform the activity while recording assumptions, observations, evidence, and decisions.
3. Test normal operation, the exception, and an escalation or follow-up condition.
4. Document conclusions, owners, deadlines, verification methods, and review triggers.

Scenario Analysis

• Identify the requirement or control with the strongest influence on the scenario outcome.
• Compare two defensible responses and explain their risk, operational, and evidence trade-offs.
• Decide how the permissions and process administration checklist should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Start where expected practice and observed evidence first diverge. Separate a missing record from an ineffective process, distinguish unclear ownership from a control failure, and treat “a package update disrupts a dependent service” as a hypothesis until tested against the applicable criteria and intended outcome.

Validation Checklist

• Scope, roles, criteria, stakeholders, dependencies, and intended outcomes are explicit.
• The permissions and process administration checklist connects conclusions to objective, reviewable support.
• Normal operation, the stated exception, escalation, and follow-up were evaluated.
• Owners, due dates, verification methods, review triggers, and improvement actions are clear.

Lesson Outcome

Learners can apply Files, Directories, Permissions, Users, Groups, Processes, and Packages, explain the reasoning used, and defend the result through permissions and process administration checklist.