Module 6 self-check

Module 6 self-check.

  • Coverage: 6a (lesson 6.1, Lab 6A step 1, Q1), 6b (lesson 6.2, Lab 6A step 5, Q2–Q3), 6c (lessons 6.3 and 6.5, Lab 6A steps 2–7, Q4–Q6, Q10), and 6d (lesson 6.4, Lab 6B, Q7–Q9).
  • HCL: backend "pg" {} with PG_CONN_STR, terraform_remote_state with backend, workspace, and config, the moved block, and the removed block with lifecycle { destroy = false } all follow documented syntax for 1.7+ and 1.12. Alignment matches fmt.
  • Flagged uncertainty:
    • Lab 6A notes that pg advisory locks release when the session ends, so force-unlock isn't demonstrated live rather than faked.
    • Lesson 6.4 tells learners to set destroy explicitly in removed blocks instead of relying on a default.
    • The states table name in the pg backend is the documented default schema layout. If your provider version differs, \dt terraform_remote_state.* in psql shows the actual table.
  • Answers: rechecked against documented locking, migration, refresh-only, and workspace behavior.