# PLO — Session 3: Storage, RAID and ZFS

**CLO:** By the end of this session, the student can choose a block layout for a media workload, measure its throughput and capacity, and prove its failure path.

| PLO | Role | Research answer | Lab evidence | Points | Evidence | Rubric |
|---|---|---|---:|---:|---|---|
| PLO2 | primary | 4 | 3 | 7 | An 800–1,200-word block-and-object tiering policy with 5–8 sources; the mdadm and ZFS layouts, the fio results, the capacity table and the rebuild or resilver log | 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 costed policy that compares block and object storage, sets a restore objective and tier thresholds, and weighs the counterargument about retrieval cost. 3 = a sensible policy with some costing and a restore test. 2 = describes the tiers but does not choose a policy or price it. 1 = a summary with fewer than five sources or no decision. 0 = nothing submitted or misconduct.

**Lab (3/2/1/0).** 3 = the mdadm RAID5/6/10 and ZFS raidz1/2 arrays are built, the fio results and capacity table are complete, a rebuild and a resilver finish clean, teardown and cost respected. 2 = mostly complete, one check missing. 1 = partial 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.
