HashiCorp Terraform Certified Associate Preparation Guide.png

Terraform_e.tar.gz

access_key_id

secret_access_key

init

validate

config

needed-copy

not-needed-copy

needed-copy-copy

This course is designed to help learners obtain the Terraform Associate certification from HashiCorp. 

You’ve likely picked up this course because you dabbled in Terraform as a hobbyist or in a
development environment, and you’re excited about the possibilities of deploying Infrastructure 
as Code (IaC). It will enable you to sharpen your skills and prove your knowledge with a certification from HashiCorp. Terraform is an amazing tool to deploy Infrastructure as Code in a cloud-agnostic way. We’re excited to share our accumulated knowledge with you through this course.

HashiCorp Terraform Certified Associate Preparation Guide

## Resource graph

When Terraform is analyzing a configuration, it creates a resource graph that lists out all the resources in the configuration and their dependencies. This allows Terraform to create the physical resources in the proper order, and when possible, create resources in parallel if they aren’t interdependent. Let’s consider an example configuration where we’ve defined the following resources:


* Virtual network
* Virtual machine
* Virtual NIC
* Database as a service
* DNS record

## Dependencies and resource creation order

The virtual NIC attaches to the virtual network. One argument in the configuration block of the virtual NIC references the virtual network, and thus Terraform knows that the virtual NIC is dependent on the virtual network. Following the same logic, the virtual machine (VM in the image below) references the virtual NIC. The DNS record references the public IP address of the virtual machine, creating a new dependency. Terraform evaluates this and determines that it must create resources in this order:



# Resource graph

When Terraform is analyzing a configuration, it creates a resource graph that lists out all the resources in the configuration and their dependencies. This allows Terraform to create the physical resources in the proper order, and when possible, create resources in parallel if they aren’t interdependent. Let’s consider an example configuration where we’ve defined the following resources:


* Virtual network
* Virtual machine
* Virtual NIC
* Database as a service
* DNS record

# Dependencies and resource creation order

The virtual NIC attaches to the virtual network. One argument in the configuration block of the virtual NIC references the virtual network, and thus Terraform knows that the virtual NIC is dependent on the virtual network. Following the same logic, the virtual machine (VM in the image below) references the virtual NIC. The DNS record references the public IP address of the virtual machine, creating a new dependency. Terraform evaluates this and determines that it must create resources in this order:



Learn how built-in dependencies are managed in Terraform.

Introduction to the Course

Introduction to Infrastructure as Code

Basics of Terraform

Outside the Workflow: Using the Terraform CLI

Terraform Modules

Navigate Terraform Workflow

Implement and Maintain State

Read, Generate, and Modify Configuration

Understand Terraform Enterprise Capabilities

Conclusion

Built-in Dependency Management

Resource graph

Dependencies and resource creation order