Gain insights into Infrastructure as Code with Terraform, sharpen your skills, and prepare for the HashiCorp Terraform Associate certification in a cloud-agnostic way.

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

On the public Terraform Registry with access control enabled


In a zip file that each team can download and use locally

On an internal website accessible to all teams that need to use it

In a custom provider plugin stored on an internal website

Suppose you’re developing a private module for networking that’ll be used by multiple teams across the organization. Where should the module code be stored?


Suppose you’re developing a private module for networking that’ll be used by multiple teams across the organization. Where should the module code be stored?

`variable “instance_size” {
  value = “medium”
}`

`variable “instance_size” {
  default = “medium”
}`

`variable {
  name = “instance_size”
  default = “medium”
}`

`variable “instance_size” {
  default = {
    value = “medium”
  }
}`

Suppose you’re defining input variables for your Terraform configuration, and you’d like to supply a default value for a variable named `instance_size`. Which code block would you use?

Suppose you’re defining input variables for your Terraform configuration, and you’d like to supply a default value for a variable named <code>instance_size</code>. Which code block would you use?

Run `terraform output` at the command line.

Open the state data and view the outputs.

Run a `terraform apply` at the command line.

Suppose you have values defined as outputs in your Terraform configuration. You’ve already applied the configuration, and you’d like to see the current values of the outputs. What’s the easiest way to retrieve those values?

Suppose you have values defined as outputs in your Terraform configuration. You’ve already applied the configuration, and you’d like to see the current values of the outputs. What’s the easiest way to retrieve those values?

Add the `parent` keyword to the attribute reference.

Add the `global` keyword to the attribute reference.

Add the `resource` attribute as an output in the parent module to make it accessible to the child module.

Add an input variable to the child module, and add an argument for the input variable to the `module` block in the parent module.

Suppose you’re writing a child module for your Terraform configuration. You try to refer to the value of a resource attribute from the parent module, but the value isn’t found. How should you update the configurations?

Suppose you’re writing a child module for your Terraform configuration. You try to refer to the value of a resource attribute from the parent module, but the value isn’t found. How should you update the configurations?

Recent activity on the GitHub repository for the module

Suppose you’ve been instructed to use modules from the Terraform Registry that’re actively maintained by HashiCorp or HashiCorp partners. What should you look for in such modules?

Suppose you’ve been instructed to use modules from the Terraform Registry that’re actively maintained by HashiCorp or HashiCorp partners. What should you look for in such modules?

Suppose you’re using version 2.0 of a networking module in your Terraform configuration, and you’re concerned that major version updates of the module could cause issues. How would you configure the module version argument to remain on major version 2.0 while still allowing minor version updates?

Suppose you’re using version 2.0 of a networking module in your Terraform configuration, and you’re concerned that major version updates of the module could cause issues. How would you configure the module version argument to remain on major version 2.0 while still allowing minor version updates?

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

Quiz on Terraform Modules