Set 2

11. Log Filtering – Extract Critical Errors

Scenario SRE team needs only critical error entries extracted from large application logs for incident review.

Instructions:

• Navigate to ~/kactii29

• Create a folder named critical_logs

• Assume app.log exists

• Filter lines containing the word ERROR

• Save results to errors_only.log

Commands Expected: grep, output redirection

---

12. Session Auditing – Identify Active User Sessions

Scenario Security team requests a snapshot of users currently logged into the system during a compliance audit.

Instructions:

• Navigate to ~/kactii29

• Create folder session_audit

• Capture all logged-in users

• Save output to active_users.txt

Commands Expected: who

---

13. Disk Hygiene – Identify Large Files

Scenario Platform engineering suspects oversized files are causing disk pressure.

Instructions:

• Navigate to ~/kactii29

• Create disk_hygiene folder

• Identify file sizes in your home directory

• Sort results by size

• Save output to file_sizes.txt

Commands Expected: du -h, sort

---

14. Command Discovery – Validate Tool Availability

Scenario Before running automation, DevOps must confirm required binaries exist on the server.

Instructions:

• Navigate to ~/kactii29

• Create tool_validation folder

• Locate paths for bash, systemctl, and grep

• Save results to tool_paths.txt

Commands Expected: which

---

15. Environment Verification – Inspect Runtime Variables

Scenario Application is behaving inconsistently; engineers want to verify environment variables.

Instructions:

• Navigate to ~/kactii29

• Create env_audit

• Display all environment variables

• Save output to env_snapshot.txt

Commands Expected: printenv

---

16. Service Investigation – Validate Multiple Services

Scenario Operations team wants confirmation that essential services are running.

Instructions:

• Navigate to ~/kactii29

• Create service_audit

• Check status of cron and ssh

• Save outputs to service_status.txt

Commands Expected: systemctl status

---

17. Scheduled Jobs – Verify Deferred Tasks

Scenario Compliance audit requires validation of all scheduled deferred jobs.

Instructions:

• Navigate to ~/kactii29

• Create job_audit

• List all scheduled at jobs

• Save output to scheduled_jobs.txt

Commands Expected: atq

---

18. Text Analysis – Count Unique Event Types

Scenario Analytics team needs a count of unique event names from raw event logs.

Instructions:

• Navigate to ~/kactii29

• Create event_analysis

• Assume events.log exists

• Extract unique lines

• Count total unique entries

• Save result to event_count.txt

Commands Expected: sort, uniq, wc -l

---

19. Network Snapshot – Capture Listening Services

Scenario Security operations requires a record of all listening ports before firewall changes.

Instructions:

• Navigate to ~/kactii29

• Create port_snapshot

• Capture all listening sockets

• Save output to listening_ports.txt

Commands Expected: ss -tuln

---

20. System Availability – Uptime & Load Evidence

Scenario Management requests proof of system stability during peak hours.

Instructions:

• Navigate to ~/kactii29

• Create availability_report

• Capture system uptime

• Append timestamp

• Save to availability.log

Commands Expected: uptime, date, output redirection