The official HashiCorp Certified: Terraform Associate (004) syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
1a Explain what IaC is
Infrastructure as code (IaC) manages infrastructure with configuration files instead of a graphical interface, so it can be versioned, reused and shared. Terraform is declarative: you describe the end state and it works out the steps, it calls each platform's API through providers and uses the state file as the source of truth. It is not a configuration management tool.
What is Infrastructure as Code with Terraform? ↗What is Terraform? (Why Terraform) ↗
1b Describe the advantages of IaC patterns
IaC patterns let teams review changes in version control like code, reuse modules that codify standards, create and destroy disposable environments and inspect a plan before it runs. A remote backend such as HCP Terraform shares state without race conditions, and policies such as Sentinel replace ticket-based reviews.
Terraform Use Cases ↗What is Infrastructure as Code with Terraform? ↗
1c Explain how Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflows
Terraform uses the same language and workflow with any provider, so one configuration can combine several clouds, on-premises platforms with an API and SaaS services such as DNS or CDN, and it handles dependencies between them. Each provider brings its own resource types; there are no universal resources. Deploying across clouds increases fault tolerance.
Terraform Use Cases ↗Terraform versus CloudFormation, Heat, and other infrastructure as code tools ↗