Set 3

21. Log Investigation – Extract Warning Messages

Scenario Operations team needs all warning-level messages isolated from system logs for trend analysis.

Instructions:

• Navigate to ~/kactii29

• Create folder warning_logs

• Assume system.log exists

• Extract lines containing WARN

• Save results to warnings.log

Commands Expected: grep, output redirection

---

22. Resource Analysis – Identify Top Disk Consumers

Scenario Infra team needs a quick breakdown of disk usage to identify growth hotspots.

Instructions:

• Navigate to ~/kactii29

• Create disk_consumers

• Measure disk usage of directories

• Sort results in human-readable order

• Save to disk_usage.txt

Commands Expected: du -h, sort -h

---

23. User Presence Audit – Capture Login Snapshot

Scenario Security wants evidence of user presence during a specific time window.

Instructions:

• Navigate to ~/kactii29

• Create login_snapshot

• Capture logged-in users

• Append timestamp

• Save to logins.txt

Commands Expected: who, date, output redirection

---

24. Command Verification – Ensure Admin Tools Exist

Scenario Before a maintenance window, engineers must confirm administrative tools are installed.

Instructions:

• Navigate to ~/kactii29

• Create admin_tools_check

• Locate paths for uptime, ss, and systemctl

• Save output to admin_tools.txt

Commands Expected: which

---

25. Service Recovery – Restart Critical Service

Scenario Monitoring detected instability in the scheduling service.

Instructions:

• Navigate to ~/kactii29

• Create service_recovery

• Check cron service status

• Restart service

• Verify status after restart

Commands Expected: systemctl status, systemctl restart

---

26. Deferred Execution – Schedule One-Time Cleanup

Scenario Platform team wants a one-time cleanup job to run later without cron persistence.

Instructions:

• Navigate to ~/kactii29

• Create one_time_job

• Schedule a cleanup script using at

• Verify job is scheduled

Commands Expected: at, atq

---

27. Environment Inspection – Validate PATH Integrity

Scenario Application binaries are not resolving correctly; engineers must inspect environment paths.

Instructions:

• Navigate to ~/kactii29

• Create path_validation

• Display environment variables

• Extract PATH variable

• Save to path.txt

Commands Expected: printenv, grep

---

28. Network Audit – Capture Active Listeners

Scenario Security requires a pre-deployment snapshot of active listening ports.

Instructions:

• Navigate to ~/kactii29

• Create listener_audit

• Capture TCP/UDP listening sockets

• Save output to listeners.txt

Commands Expected: ss -tuln

---

29. Text Normalization – Unique Sorted Hostnames

Scenario Infrastructure team needs a clean list of unique hostnames from collected data.

Instructions:

• Navigate to ~/kactii29

• Create hostname_cleanup

• Assume hosts.txt exists

• Sort and remove duplicates

• Save to unique_hosts.txt

Commands Expected: sort, uniq

---

30. System Stability – Capture Uptime Evidence

Scenario Management requests proof of uninterrupted system availability.

Instructions:

• Navigate to ~/kactii29

• Create stability_evidence

• Capture uptime

• Append timestamp

• Save to stability.log

Commands Expected: uptime, date, output redirection

---