Read the error before changing anything

short · 45 min · Objective 6.1

Task

Introduce five deployment faults one at a time and, for each, extract the four facts from the error before touching the template. The discipline is the lesson: reading properly is faster than guessing, and the instinct to change something first destroys the evidence.

Steps

  1. Start from a template that applies cleanly. Confirm it does, so you have a known-good baseline.
  2. Introduce fault one: a syntax error. Apply, and record in lab/tshoot/errors.md the four facts -- failing resource, error code, PHASE (validation or creation), and whether a rollback occurred.
  3. Repeat for: an invalid value the service will reject (a name breaking its rules), a reference to a resource that does not exist, a circular reference between two resources, and a permission the deploying identity lacks.
  4. For each, note whether the failure happened at validation or at creation, and record the rule that distinguishes them.
  5. For the permission fault, find the underlying platform audit record naming the denied action, and record how much more it told you than the tool's own message.

Verify

grep -Eci 'validation' lab/tshoot/errors.md
grep -Eci 'creation' lab/tshoot/errors.md
grep -Eci 'circular' lab/tshoot/errors.md
grep -Eci 'audit|activity log' lab/tshoot/errors.md
grep -Ec 'fault|error' lab/tshoot/errors.md

Five faults recorded, with both phases represented. A validation failure is a template problem and a creation failure is an environment problem, and telling them apart immediately halves the search space.

This is an independent study companion for CompTIA Cloud+ CV0-004 and is not produced by or endorsed by CompTIA.