Set 7

Ubuntu L2-Corporal Industry Assignments

(Set 7 | Index 61–70) Root Working Directory: ~/kactii27

---

61. Process State Transition Analysis

Scenario: Ops needs to understand how processes change states during execution.

Instructions:

• Navigate to ~/kactii27

• Create a folder named process_states

• Start a long-running process

• Observe process states over time

• Capture state transitions

• Save findings to states.txt

Commands Expected: ps -o pid,stat,cmd, top, grep, redirection

---

62. Orphan Process Detection Drill

Scenario: A parent process crash may leave orphaned children.

Instructions:

• Navigate to ~/kactii27

• Create a folder named orphan_processes

• Start a parent/child process scenario

• Identify orphaned processes

• Document PID and PPID changes

• Save output to orphans.txt

Commands Expected: ps -ef, pstree, grep, redirection

---

63. Disk Space Reservation Awareness Test

Scenario: Disk appears full earlier than expected.

Instructions:

• Navigate to ~/kactii27

• Create a folder named disk_reservation

• Inspect filesystem usage

• Compare available vs usable space

• Identify reserved space behavior

• Save findings to disk_reservation.txt

Commands Expected: df -h, df -i, tune2fs -l (read-only if permitted), redirection

---

64. Directory Traversal Failure Simulation

Scenario: Applications fail due to traversal permission issues.

Instructions:

• Navigate to ~/kactii27

• Create a folder named traversal_failure

• Remove execute permission from a directory

• Attempt access to files inside

• Restore permissions

• Save observations to traversal_failure.txt

Commands Expected: chmod, ls -ld, access attempts, redirection

---

65. File Hard Link Behavior Investigation

Scenario: Storage optimization uses hard links.

Instructions:

• Navigate to ~/kactii27

• Create a folder named hard_links

• Create a file and multiple hard links

• Modify file content

• Observe link count and behavior

• Save output to hard_links.txt

Commands Expected: ln, ls -li, stat, redirection

---

66. Socket & Connection State Monitoring

Scenario: Unexpected network connections are suspected.

Instructions:

• Navigate to ~/kactii27

• Create a folder named socket_states

• Inspect active connections

• Classify connection states

• Capture listening vs established sockets

• Save output to sockets.txt

Commands Expected: ss -tanp, netstat -an, redirection

---

67. File Deletion Recovery Awareness (No Restore)

Scenario: Accidental deletion occurred; understand recovery limits.

Instructions:

• Navigate to ~/kactii27

• Create a folder named deletion_awareness

• Create and delete files

• Observe inode reuse behavior

• Document limitations of recovery

• Save notes to deletion_notes.txt

Commands Expected: rm, ls -i, df, redirection

---

68. System Call Visibility Exploration (Read-Only)

Scenario: Engineers need awareness of syscall activity.

Instructions:

• Navigate to ~/kactii27

• Create a folder named syscall_visibility

• Attach syscall tracing to a simple command

• Observe system calls

• Save sample output

Commands Expected: strace (read-only observation), redirection

---

69. Time Synchronization Status Check

Scenario: Time drift affects distributed systems.

Instructions:

• Navigate to ~/kactii27

• Create a folder named time_sync

• Inspect system time and sync status

• Identify time source

• Save output to time_sync.txt

Commands Expected: timedatectl, date, redirection

---

70. Environment Isolation Verification

Scenario: Ensure shell environments are isolated correctly.

Instructions:

• Navigate to ~/kactii27

• Create a folder named env_isolation

• Set environment variables in one shell

• Verify isolation in a new shell

• Document behavior in env_isolation.txt

Commands Expected: export, env, subshell usage, redirection

---