Lesson 19 · Senior IaC judgment

Mock senior IaC interview pack

A retrieval-first mock pack for turning the whole IaC course into clear, interview-grade answers you can say under pressure.

Your win: run a realistic senior IaC mock interview on yourself, score your answers honestly, and turn weak spots into a focused review plan.

In plain English Plain English: answer out loud before checking the answer points. Recognition is not recall.

What this mock is really training

This page is not only testing whether you remember facts. It is training whether you can speak clearly under pressure about Terraform ownership boundaries, state trust, abstraction trade-offs, identity paths, and infra-change safety.

That is why this mock works best when you treat it like a real interview. Answer first. Then check the points. Then answer again more cleanly. The second answer is where a lot of learning happens.

The answer checklist A strong answer should usually include: (1) the mechanism, (2) the main trade-off or limit, and (3) a repo-grounded consequence or example.

Round 1 · Terraform truthfulness and ownership boundaries

  1. What does Terraform really own in this repo?
  2. Why is “everything is IaC here” too vague?
  3. Why is the Thanos-bucket caveat a useful teaching point rather than trivia?
  4. What is the most honest one-paragraph summary of the repo’s Terraform posture?
  5. Why should strong IaC answers mention adjacent systems like Helm, Kubernetes, and Atlantis?
  6. How would you explain the difference between provisioned foundation and runtime behavior?
Round 1 · Strong answer points
  1. Ownership boundary. Terraform owns a large part of the cloud foundation and trust wiring.
  2. Truthfulness. That does not mean every important operational resource is in this tree.
  3. Exception literacy. Explicit exceptions prove the map is not the whole territory.
  4. Concise summary. Terraform is foundational here, but not synonymous with the whole platform.
  5. Adjacency. Neighboring systems still own runtime, delivery, and app-level behavior.
  6. Boundary clarity. Provisioning and operation are connected, but not identical.

Round 2 · State, modules, and trust-chain design

  1. Why is state a senior IaC topic?
  2. How does remote state change the collaboration model?
  3. What is the real value and cost of Terragrunt here?
  4. Why should modules and Terragrunt leaves be reviewed like APIs?
  5. What is the real cross-course payoff of Workload Identity and WIF?
  6. Why does KMS belong in the trust-chain conversation rather than as a standalone “crypto topic”?
Round 2 · Strong answer points
  1. State realism. State affects plan trust, drift handling, locking, and partial-failure recovery.
  2. Shared backend. Remote state turns Terraform into a team control surface, not a personal tool.
  3. Terragrunt trade-off. DRY and standardization help, but indirection can hurt discoverability.
  4. API lens. Inputs, outputs, dependencies, and hidden coupling matter as much as file organization.
  5. Trust path. Workload Identity and WIF explain how pods and CI stay keyless.
  6. KMS role. KMS underpins real decryption and signing paths, not just abstract encryption theory.

Round 3 · Atlantis, blast radius, and senior review judgment

  1. Why are Atlantis applies gated so heavily?
  2. Why is rollback language trickier in IaC than in app delivery?
  3. What makes a Terraform plan more or less trustworthy?
  4. What would you look for first in a risky infra PR?
  5. How would you summarize this repo’s operational IaC value honestly?
  6. What separates a senior IaC answer from a doc-only answer?
Round 3 · Strong answer points
  1. Blast radius. Reviewed plans, approvals, restricted apply rights, and locking are safety controls for destructive potential.
  2. Rollback realism. Infra recovery may require reconciliation, import, or careful re-apply, not a simple redeploy.
  3. Plan trust. State quality, drift, imports, and prior partial history all matter.
  4. Review lens. Start with ownership boundary, state assumptions, trust path, and blast radius.
  5. Honest value. Terraform gives repeatable foundations and trust wiring, but not the whole platform story.
  6. Judgment layer. Senior answers add truthfulness, trade-offs, and operational consequence.

Self-scoring rubric

ScoreMeaning
0I could not explain it without notes.
1I gave fragments, but the answer was incomplete or fuzzy.
2I explained the main idea, but missed the trade-off, limit, or repo consequence.
3I gave a strong, clear answer with mechanism + trade-off/limit + repo consequence.
Recovery map — where to go next Missed Terraform fundamentals? Revisit Lessons 1–4. Missed Terragrunt / env×org structure? Revisit Lessons 5–7 plus 15. Missed GKE / IAM / KMS / Cloud SQL foundations? Revisit Lessons 8–11 plus 16. Missed Atlantis / state / senior judgment? Revisit Lessons 12–18.

Q1. The main rule of this mock pack is…

Retrieval first is what turns recognition into interview recall.
What are the three ingredients of a strong senior IaC answer?
recall, then click to reveal
A clear mechanism, the important trade-off or limit, and a repo-grounded consequence or example.
If you want, I can now run this as a live mock senior IaC interview and grade you answer by answer. Ask me.

Sources. This pack synthesizes the whole course into retrieval practice.