Set 5

41. Incident Analysis – Extract Timeout Errors

Scenario During a service slowdown, engineers need to isolate timeout-related log entries.

Instructions:

• Navigate to ~/kactii29

• Create folder timeout_analysis

• Assume service.log exists

• Extract lines containing TIMEOUT

• Save output to timeouts.log

Commands Expected: grep, output redirection

---

42. Storage Audit – Identify Directory Growth

Scenario Capacity planning team wants to identify which directories are growing rapidly.

Instructions:

• Navigate to ~/kactii29

• Create growth_audit

• Measure disk usage of directories

• Display results in human-readable format

• Save to growth_report.txt

Commands Expected: du -h

---

43. Access Verification – Logged-In User Evidence

Scenario Security incident requires proof of who was logged in at a given time.

Instructions:

• Navigate to ~/kactii29

• Create access_verification

• Capture logged-in users

• Append current date and time

• Save to access.log

Commands Expected: who, date, output redirection

---

44. Command Path Audit – Validate System Utilities

Scenario Before running scripts, engineers must confirm command paths are correct.

Instructions:

• Navigate to ~/kactii29

• Create command_audit

• Locate paths for grep, sort, and uniq

• Save results to command_paths.txt

Commands Expected: which

---

45. Service Continuity – Verify Cron Scheduler

Scenario Automated jobs are not executing; cron service must be validated.

Instructions:

• Navigate to ~/kactii29

• Create cron_validation

• Check cron service status

• Start service if stopped

• Save status output to cron_status.txt

Commands Expected: systemctl status, systemctl start

---

46. Deferred Cleanup – Schedule One-Time Job

Scenario Operations wants a one-time cleanup job executed later without persistence.

Instructions:

• Navigate to ~/kactii29

• Create cleanup_schedule

• Schedule a cleanup script using at

• Verify the job is queued

Commands Expected: at, atq

---

47. Runtime Debugging – Capture Environment Snapshot

Scenario Application misbehavior requires capturing the runtime environment.

Instructions:

• Navigate to ~/kactii29

• Create env_debug

• Display all environment variables

• Save output to env_debug.txt

Commands Expected: printenv

---

48. Network Baseline – Listening Port Capture

Scenario Before firewall updates, network team needs a baseline of listening ports.

Instructions:

• Navigate to ~/kactii29

• Create network_baseline

• Capture all listening TCP/UDP sockets

• Save output to baseline_ports.txt

Commands Expected: ss -tuln

---

49. Data Cleanup – Unique Sorted Error Codes

Scenario Support team needs a clean list of unique error codes for reporting.

Instructions:

• Navigate to ~/kactii29

• Create error_code_cleanup

• Assume errors.log exists

• Sort and remove duplicate entries

• Save to unique_errors.txt

Commands Expected: sort, uniq

---

50. Post-Incident Proof – System Uptime Record

Scenario Leadership requests final confirmation that the system remained available.

Instructions:

• Navigate to ~/kactii29

• Create final_uptime_proof

• Capture system uptime

• Append timestamp

• Save to uptime_final.log

Commands Expected: uptime, date, output redirection

---