Provision and manage infrastructure as code, end to end.

What Infrastructure as Code actually solves, declarative vs imperative thinking, where Terraform fits next to CloudFormation/Pulumi/CDK, and how Terraform's provider plugin architecture works under the hood.

The init → plan → apply → destroy loop in depth, the CLI commands you'll actually use daily, how to read an execution plan safely, and how to use -target/-var/-var-file/-auto-approve without shooting yourself in the foot.

Blocks, arguments, and expressions from first principles, formatting and style conventions, the real difference between a resource and a data source, and how to design outputs that are actually reusable.

Input variable types and validation, every place a value can come from (tfvars, auto.tfvars, TF_VAR_ env vars), when to reach for locals instead of repeating an expression, and how to design outputs that hold up across environments.

Built-in functions across strings, collections, and encoding; conditional and splat expressions; count vs for_each for looping over resources; and dynamic blocks for generating repeated nested configuration.

Why terraform.tfstate is the single most critical file in any Terraform project, local vs remote backends (S3+DynamoDB, Azure Storage, GCS, Terraform Cloud), state locking, the full state subcommand toolkit, importing existing resources, and handling sensitive data in state.

Configuring cloud providers with version constraints, and the real authentication patterns for AWS, Azure, and GCP — IAM roles, service principals, workload identity, and OIDC for CI/CD — plus multi-account and multi-provider setups.

State, modules, workflows, and the IaC governance questions that separate users from owners.