nerdexam
HashiCorpHashiCorp

TERRAFORM-ASSOCIATE-004 · Question #48

TERRAFORM-ASSOCIATE-004 Question #48: Real Exam Question with Answer & Explanation

The correct answer is D: Tag a release in the associated repo. The public Terraform Module Registry uses Git tags to determine module versions. When you publish a module, the registry reads the semantic version tags (e.g., v1.0.0, v1.2.3) from the associated VCS repository (GitHub, GitLab, etc.) and exposes them as selectable versions. There

Submitted by tarun92· Apr 18, 2026Work with Terraform Modules

Question

How do you specify a module's version when publishing it to the public terraform Module Registry?

Options

  • AConfiguration it in the module's Terraform code
  • BMention it on the module's configuration page on the Terraform Module Registry
  • CThe Terraform Module Registry does not support versioning modules
  • DTag a release in the associated repo

Explanation

The public Terraform Module Registry uses Git tags to determine module versions. When you publish a module, the registry reads the semantic version tags (e.g., v1.0.0, v1.2.3) from the associated VCS repository (GitHub, GitLab, etc.) and exposes them as selectable versions. There is no version field in the Terraform module code itself for registry purposes, and there is no configuration page for setting the version manually. The registry fully supports versioning - option C is incorrect.

Topics

#Terraform Module Registry#Module Versioning#Git Tags#Module Publishing

Community Discussion

No community discussion yet for this question.

Full TERRAFORM-ASSOCIATE-004 PracticeBrowse All TERRAFORM-ASSOCIATE-004 Questions