Set 10

Ubuntu L2-Corporal Industry Assignments

(Set 10 | Index 91–100) Root Working Directory: ~/kactii27


91. System Boot Performance & Timeline Review

Scenario: Ops needs insight into slow system startups.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named boot_analysis

  • Inspect system boot time and service startup durations

  • Identify slowest units

  • Save findings to boot_analysis.txt

Commands Expected: systemd-analyze, systemd-analyze blame, redirection


92. Journald Log Scope & Filtering Exercise

Scenario: Support must isolate relevant logs from noisy systems.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named journald_filter

  • Query logs for a specific unit or priority

  • Restrict output to a time window

  • Save filtered logs to journal_logs.txt

Commands Expected: journalctl, filtering flags, redirection


93. Service Failure Root-Cause Drill

Scenario: A system service fails to start.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named service_failure

  • Inspect service status and recent logs

  • Identify failure cause (read-only analysis)

  • Save findings to service_failure.txt

Commands Expected: systemctl status, journalctl -u, redirection


94. System Resource Pressure Snapshot

Scenario: System shows degraded performance.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named resource_pressure

  • Capture CPU, memory, and load snapshot

  • Identify pressure points

  • Save output to pressure.txt

Commands Expected: uptime, free -h, vmstat, redirection


95. Swap Usage & Memory Fallback Analysis

Scenario: Memory exhaustion triggers swap usage.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named swap_analysis

  • Inspect swap configuration and usage

  • Observe swap activity under load (controlled)

  • Save findings to swap.txt

Commands Expected: swapon --show, free -h, redirection


96. Service Restart Policy Inspection

Scenario: Services must recover automatically from failures.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named restart_policy

  • Inspect restart behavior of a service

  • Identify restart conditions and limits

  • Save output to restart_policy.txt

Commands Expected: systemctl show, grep, redirection


97. Kernel Message Stream Inspection

Scenario: Hardware or driver issues are suspected.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named kernel_messages

  • Inspect kernel message buffer

  • Filter warnings and errors

  • Save output to dmesg.txt

Commands Expected: dmesg, grep, redirection


98. Persistent vs Runtime Configuration Awareness

Scenario: Configuration changes disappear after reboot.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named config_scope

  • Identify runtime vs persistent settings

  • Inspect relevant config files (read-only)

  • Save findings to config_scope.txt

Commands Expected: sysctl, /etc, /proc, redirection


99. System Capability Boundary Review

Scenario: Security review checks system capability boundaries.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named capability_review

  • Inspect system-wide and binary capabilities

  • Document observed privilege boundaries

  • Save output to capabilities.txt

Commands Expected: capsh --print, getcap, redirection


100. End-to-End Incident Snapshot & Summary

Scenario: Capture a complete diagnostic snapshot during an incident.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named incident_snapshot

  • Collect system state: processes, memory, disk, network

  • Capture timestamps and context

  • Save outputs and write a short summary

Commands Expected: ps, top -b -n 1, df -h, ip a, date, redirection



Last updated