Module 1: Cloud Platform Fundamentals: Mistake Clinic

This clinic turns wrong moves into reusable judgment. Use it after each practice page and again before the quiz or checkpoint.

---

Module-Specific Mistake Radar

Start with these traps. Replace or extend them with real mistakes from your own work.

Mistake to look for	Where it shows up	Symptom	Repair evidence
Finishing Account and Networking Lab with only a final answer	Account and Networking Lab	The work has no failed case, trace, test, proof gap, or design stress point.	Add the smallest broken example and show the repair that changes the result.
Finishing Compute and Storage Workshop with only a final answer	Compute and Storage Workshop	The work has no failed case, trace, test, proof gap, or design stress point.	Add the smallest broken example and show the repair that changes the result.
Finishing IAM Least-Privilege Clinic with only a final answer	IAM Least-Privilege Clinic	The work has no failed case, trace, test, proof gap, or design stress point.	Add the smallest broken example and show the repair that changes the result.
Finishing Cloud Katas with only a final answer	Cloud Katas	The work has no failed case, trace, test, proof gap, or design stress point.	Add the smallest broken example and show the repair that changes the result.
Treating The Shared-Responsibility Model and What the Cloud Actually Rents You as vocabulary instead of a tool	The Shared-Responsibility Model and What the Cloud Actually Rents You	The explanation names the concept but cannot decide between two cases.	Write one example, one non-example, and the rule that separates them.
Treating Regions, Availability Zones, and Failure Domains as vocabulary instead of a tool	Regions, Availability Zones, and Failure Domains	The explanation names the concept but cannot decide between two cases.	Write one example, one non-example, and the rule that separates them.

---

Practice Mistake Checks

Pull any miss from these checks into your mistake log.

Account and Networking Lab

Source: practice/01-account-and-networking-lab.md

For each statement, identify the error:

1. "We have Multi-AZ RDS, so we are region-resilient."
2. "The subnet is labeled private, so the database in it is safe."
3. "One NAT Gateway is enough; we can put it in any AZ."
4. "Our ALB is in one AZ, but the app spans three, so we are covered."
5. "Private hosted zones mean the names are secret."

Compute and Storage Workshop

Source: practice/02-compute-and-storage-workshop.md

For each statement, identify the error:

1. "We chose a t3.small because it's cheap."
2. "Lambda scales infinitely, so we don't need a concurrency limit."
3. "Serverless is always the cheapest option."
4. "We keep millions of user uploads on an EBS volume so they stay close to the app."
5. "Aurora is just RDS Postgres with extra cost."

IAM Least-Privilege Clinic

Source: practice/03-iam-least-privilege-clinic.md

For each statement, identify the error or the missing detail:

1. { "Effect": "Allow", "Action": "*", "Resource": "*" }
2. An EC2 instance that authenticates to S3 using an IAM user's static access keys stored in /etc/aws/credentials.
3. A Lambda function role attached to 8 unrelated functions from 4 different teams.
4. A bucket policy with "Principal": "*" and no Condition.
5. "We are fine - our policy has Deny on s3:DeleteBucket; nobody can delete our bucket." (think: bucket policy vs SCP vs IAM)

---

Repair Protocol

For each real mistake:

1. Reproduce the failure on the smallest example, trace, proof, query, command, or design sketch.
2. Name the hidden assumption.
3. Repair the artifact.
4. Save evidence that changed: failing then passing test, corrected proof step, revised diagram, safer command, benchmark, or review note.
5. Add one retrieval card beginning with Check... before... or Do not use... when....

---

Mistake Log

Date	Mistake	Symptom	Root cause	Repair evidence	Retrieval card
Starter	Pick one radar row above	Explain how it would fail in this module	Name the assumption	Add a counterexample or corrected artifact	Write the card before closing the page

---

Completion Standard

• At least five real mistakes are logged.
• At least two mistakes include a counterexample or failing test.
• At least one mistake connects to an older semester skill.
• At least one correction changes code, a proof, a diagram, a command transcript, a query, or a design decision.