Terraform Professional case studies
Terraform Professional · Put your knowledge to work in context.
Terraform Professional is HashiCorp's advanced certification for practitioners who already write Terraform fluently and now need to prove they can run it at scale. It sits above the Associate level and assumes comfort with HCL, the CLI workflow, and core provider concepts. The exam tests the work that shows up in real platform teams: refactoring configurations with expressions, functions, dynamic blocks, validation and lifecycle rules; operating state safely across backends, imports, moves and drift; designing versioned modules that other teams consume; collaborating through HCP Terraform or Terraform Enterprise workspaces, VCS-driven runs, variables and run triggers; pinning providers and Terraform versions with dependency lock files; and securing and testing configurations with sensitive-data handling, policy as code and the native test framework. Preparation should be hands-on rather than reading-first: build a multi-environment repository, publish a private module registry entry, deliberately corrupt and recover state, and write both terraform test cases and policy checks. The Terraform Professional case studies are 5 cases and about 4,184 words.
1The Subnet Refactor That Wants to Destroy 120 Resources
A platform team manages 4 AWS accounts from one root module. Network subnets are declared as count = length(var.subnets) over a list of 40 objects (name, cidr, az).
845 words, about 4 min2Splitting Prod State Out of a Shared Workspace After a Bad Unlock
One S3 bucket acme-tfstate plus a DynamoDB lock table backs all environments, separated only by terraform workspace (dev, staging, prod). Prod holds 190 of the 340 total resources and is now under audit: prod state must live in a different bucket, written by a different IAM role, with no human CLI credentials.
841 words, about 4 min3The 46-Boolean Service Module
The platform team publishes a service registry module (v4.2.0) bundling VPC, ALB, ECS service, and RDS. 22 application teams consume it.
799 words, about 4 min4Stale Outputs, Duplicated Credentials, and an 11-Minute Queue
An HCP Terraform org ( acme ) runs net-prod and app-prod VCS-driven on the same repo. app-prod reads net-prod outputs through terraform remote state against the HCP-hosted state.
858 words, about 4 min5Lock File Churn, an Accidental Upgrade, and Tests That Need Real VPCs
Repo infra-live : required version = " = 0.13" and provider hashicorp/aws constrained ~ 4.0 . .terraform.lock.hcl was committed from a linux/amd64 CI runner only, with no platform entries for macOS.
841 words, about 4 min