Module versioning in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is module versioning in Terraform?

Module versioning in Terraform means keeping track of different versions of a module so you can use a specific, stable version in your infrastructure code.

beginner

Why should you use versioned modules in Terraform?

Using versioned modules helps avoid unexpected changes by locking your infrastructure to a tested module version, making your deployments more reliable.

beginner

How do you specify a module version in Terraform?

You specify a module version by adding a version argument in the module block, like: <br>module "example" {<br> source = "registry.terraform.io/hashicorp/example"<br> version = "1.2.0"<br>}

intermediate

What happens if you don’t specify a module version?

If you don’t specify a version, Terraform uses the latest available module version, which might cause unexpected changes if the module updates.

intermediate

How can you update a module to a newer version safely?

To update safely, change the version number in your module block, run terraform init -upgrade to download the new version, then test your infrastructure.

What is the purpose of specifying a module version in Terraform?

A To lock the module to a specific stable version

B To automatically upgrade to the latest module version

C To delete old versions of the module

D To run the module faster

Specifying a module version locks your infrastructure to a known stable version, preventing unexpected changes.

Which command updates Terraform modules to the latest allowed version?

A terraform destroy

B terraform apply

C terraform plan

D terraform init -upgrade

terraform init -upgrade downloads the latest module versions allowed by your version constraints.

What happens if you omit the version argument in a Terraform module source?

A Terraform uses the latest module version

B Terraform throws an error

C Terraform uses a random module version

D Terraform disables the module

Without a version, Terraform defaults to the latest available module version.

Why is it risky to always use the latest module version without specifying a version?

A It disables module caching

B It makes Terraform run slower

C It can cause unexpected infrastructure changes

D It deletes your state file

Using the latest version can introduce changes you did not test, risking your infrastructure stability.

How do you specify a module version in Terraform code?

A source_version = "1.0.0" inside the provider block

B version = "1.0.0" inside the module block

C module_version = "1.0.0" outside the module block

D version = "latest" inside the resource block

You specify the version inside the module block with the argument version = "1.0.0".

Explain what module versioning is in Terraform and why it is important.

Think about how using a fixed version helps keep your infrastructure predictable.

Describe the steps to safely update a Terraform module to a newer version.

Consider how you control the version and apply the update carefully.