# PLO — Session 5: Containers and the Nextcloud NAS

**CLO:** By the end of this session, the student can deploy a multi-container service on a mirrored NAS volume, publish it behind Cloudflare's proxy with only SSH and TLS exposed, back it up to object storage, and prove the data survives container replacement and a restore.

| PLO | Role | Research answer | Lab evidence | Points | Evidence | Rubric |
|---|---|---|---:|---:|---|---|
| PLO2 | primary | 4 | 3 | 7 | An 800–1,200-word portability argument with 5–8 sources; the Compose file, health JSON, mirrored-NAS detail, checksum before/after recreation, backup listing, restore hash, failure diagnosis, recovery and teardown | Research 4/3/2/1; Lab 3/2/1/0 |
| PLO1 | secondary | 0 | 0 | 0 | Lecture context only; not scored | — |
| **Total** | | **4** | **3** | **7** | | |

**Total: 7 points**

## Four-level descriptors

**Research (4/3/2/1).** 4 = a clear abstraction choice with a portability argument, a counterargument about managed operations, an exit path and evidence from the lab. 3 = a sensible choice with some comparison. 2 = describes the abstractions but does not choose one. 1 = a summary with fewer than five sources. 0 = nothing submitted or misconduct.

**Lab (3/2/1/0).** 3 = the mirrored NAS is mounted and clean, every service is healthy, the checksum survives container replacement, the backup listing is complete, the restore hash matches, the empty-instance failure is diagnosed from the mount, the instance id and data return, teardown and cost are respected. 2 = mostly complete, one proof thin. 1 = partial deployment, an unproven restore or incomplete teardown. 0 = nothing submitted, unsafe data, or no teardown.

The full course arithmetic is in `production/baseline.md`; this file is the weekly instance.
