Skip to main content

Module 5: Cloud Security & Observability: Guided Labs

Labs turn reading into evidence. Complete these after the relevant concept pages and before the quiz. Local OpenTelemetry, logging, dashboard, secret-rotation, and threat-model exercises are first-class evidence; paid cloud services require budget alerts, retention limits, and teardown notes.

Lab 1: Trace or Model​

Goal: make the invisible state visible.

  • Choose one core mechanism from the module.
  • Trace it by hand on a small input, scenario, or design.
  • Record intermediate states, not only the final answer.
  • Explain where the trace would change under a different input or constraint.

Evidence: one diagram, table, trace log, or annotated walkthrough.

Lab 2: Build From Scratch​

Goal: implement or construct the smallest working version without copying a finished solution.

  • Start from a blank file or blank diagram.
  • Commit the first working slice.
  • Add one test, check, or review question that would catch a naive mistake.

Evidence: runnable code, proof artifact, query, command sequence, or design document.

Lab 3: Debug a Broken Version​

Goal: learn through failure.

  • Introduce or find one realistic bug, misconception, or bad design choice.
  • Write the symptom first.
  • Identify the root cause.
  • Fix it and record why the fix works.

Evidence: before/after note, failing then passing test, corrected proof, or revised diagram.

Lab 4: Compare Alternatives​

Goal: practice judgment.

Compare two approaches from the module using constraints such as time, memory, clarity, correctness risk, operational cost, or evolvability.

Evidence: short comparison table plus a decision sentence: I would choose X when...