Drawing cold paths before you touch the console

Many learners open the console first. That habit works for daily work, yet exams reward concise explanations before implementation detail. Start with a cold path diagram: ingress, compute, data, and egress on one plane. Name trust boundaries with a highlighter color instead of extra boxes.

Second, annotate two failure modes only—latency spikes and credential loss. The exam rarely needs more than paired risks if you explain them cleanly. Keep verbs operational: "retry with backoff" beats long vendor names.

Finally, translate the sketch into six sentences maximum before you allow yourself a bullet list. This sequence mirrors how graders read answers. It also prevents the Architecture Scenarios — Resilient Web Stack cohort from drifting into stack dumps that earn partial credit at best.