# PLO — Session 4: Networking and delivery

**CLO:** By the end of this session, the student can explain where Cloudflare's edge shortens the path, measure a cache hit rate, deploy the catalogue Worker, and choose a delivery configuration against latency and egress cost.

| PLO | Role | Research answer | Lab evidence | Points | Evidence | Rubric |
|---|---|---|---:|---:|---|---|
| PLO2 | primary | 4 | 0 | 4 | An 800–1,200-word CDN choice with 5–8 sources and a priced comparison | Research 4/3/2/1 |
| PLO1 | secondary | 0 | 3 | 3 | The Cloudflare evidence bundle: the deployed Worker `/health`, the `cf-cache-status` before and after the Cache Rule, the purge, the versioned key and the expiring capability | Lab 3/2/1/0 |
| **Total** | | **4** | **3** | **7** | | |

**Total: 7 points**

## Four-level descriptors

**Research (4/3/2/1).** 4 = a clear CDN choice with hit-rate, latency and egress modelled, a counterargument about origin offload and a decision metric. 3 = a sensible choice with some pricing and one under-analysed dimension. 2 = describes CDNs but does not choose or price one. 1 = a summary with fewer than five sources. 0 = nothing submitted or misconduct.

**Lab (3/2/1/0).** 3 = the Worker answers `/health` and `/assets`, the Cache Rule produces MISS then HIT, the purge and versioned key are evidenced, the capability works then expires, teardown and cost respected. 2 = mostly complete, one check missing. 1 = partial evidence 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.
