How do you specify version 1.0.0 for a module stored on the public Terraform Module Registry within a module block?

How do you specify version 1.0.0 for a module stored on the public Terraform Module Registry within a module block?

• A. Modules stored on the public Terraform Module Registry do not support versioning
• B. Append ?ref=v1.0.0 argument to the source path
• C. Add version = "1.0.0" attribute to module block
• D. Nothing — modules stored on the public Terraform Module Registry always default to version 1.0.0

Answer: (C)

Pinning a specific module version from the public registry is done by adding a version argument inside the module block. This tells Terraform to fetch exactly that version and use it for planning and applying, ensuring reproducible infrastructure. For example: module "my_module" { source = "registry.terraform.io/hashicorp/example" version = "1.0.0" } If you omit the version, Terraform will pull the latest available release (subject to any other constraints), so you wouldn’t be guaranteed to get 1.0.0. The other approaches—using a query parameter on the source URL or assuming a default version—aren’t how the registry versioning works, and they won’t reliably lock you to 1.0.0.

Pinning a specific module version from the public registry is done by adding a version argument inside the module block. This tells Terraform to fetch exactly that version and use it for planning and applying, ensuring reproducible infrastructure.

For example:

module "my_module" {

source = "registry.terraform.io/hashicorp/example"

version = "1.0.0"

}

If you omit the version, Terraform will pull the latest available release (subject to any other constraints), so you wouldn’t be guaranteed to get 1.0.0. The other approaches—using a query parameter on the source URL or assuming a default version—aren’t how the registry versioning works, and they won’t reliably lock you to 1.0.0.