Linux Systems Administration Bootcamp Certificate

Checkpoint 1: Provision a fresh Linux VM/server and document OS, kernel, boot path, package sources, filesystem layout and a reproducible baseline-hardening checklist.
Checkpoint 2: Create users/groups and least-privilege sudo access; apply ownership and permission rules to a shared service directory and prove both allowed and denied behaviors.
Checkpoint 3: Configure persistent networking, DNS and hostname settings; validate routes/listeners and troubleshoot an intentionally broken connectivity scenario from evidence.
Checkpoint 4: Create and mount storage, inspect capacity/inodes, configure a service under systemd and write a safe override/unit that survives reboot and handles restart failure.
Checkpoint 5: Configure OpenSSH with keys, host/client config and a reduced attack surface; demonstrate remote administration, transfer and recovery without relying on password login.
Checkpoint 6: Write a Bash maintenance script with arguments, exit codes, logging and scheduled execution; use journalctl and service logs to diagnose an injected failure and restore service.

Day 1: Define the server role, users, ports, storage, service dependencies, SLOs and threat boundary; provision a clean Linux VM and capture the baseline.
Day 2: Configure users/groups, sudo, permissions, packages and filesystem layout; create a rollback-safe change log and verify least privilege.
Day 3: Configure networking/DNS and remote SSH administration; prove key-based access, host verification and one connectivity troubleshooting workflow.
Day 4: Install a real service, create or override its systemd unit, configure persistent storage and verify startup, restart, dependency and reboot behavior.
Day 5: Build a Bash maintenance/backup/health script with arguments, error handling, logging and cron/systemd scheduling; make it idempotent where practical.
Day 6: Instrument logs and operational checks; inject disk, permission, process or network failure, diagnose with Linux tools/journalctl and document recovery
Day 7: Publish repo/runbook with configuration files, scripts, architecture, hardening note, before/after evidence, incident timeline, demo and lessons learned.