Fix it in the console and watch the fix disappear

short · 45 min · Objective 6.5

Task

Demonstrate the most practically important point in the objective: a console fix on a resource managed by code is temporary. Then do it properly, and establish the emergency exception that makes the rule usable.

Steps

  1. Apply a template containing a deliberate misconfiguration -- an over-permissive rule or a setting that should be restricted. Confirm a posture check flags it, and record the finding in lab/misconf.md.
  2. Fix it OUTSIDE the code, the way someone would at 2am. Re-run the posture check and confirm the finding is gone.
  3. Re-apply the template without changing it. Re-run the posture check and record that the finding has returned, along with what the plan output said it was about to do.
  4. Fix it properly in the template, apply, and confirm the finding stays gone across a further apply.
  5. Repeat the pattern one layer down: fix a setting inside a running container, then force a replacement and record that the fix is gone because the image was unchanged.

Verify

grep -Eci 'returned|came back|reappear' lab/misconf.md
grep -Eci 'template|code' lab/misconf.md
grep -Eci 'image' lab/misconf.md
grep -Eci 'stayed|persist|remained' lab/misconf.md

All four non-zero, recording both the disappearance and the persistence. The container case is the same lesson one layer down, and it is why patching an autoscaling fleet in place silently reverts.

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