In a Terraform configuration, how do you specify that a module should use version 1.2.0 from the Terraform Registry?

Use `source = "registry.terraform.io/hashicorp/example/1.2.0"`.

Append `?version=1.2.0` to the source URL.

Set the `version` attribute in the `terraform` block.

Add a `version = "1.2.0"` argument inside the module block.

A team publishes a module to the public Terraform Registry. They release version 1.0.0, then later release 1.0.1 and 1.1.0. A consumer's configuration uses version = "~> 1.0". When the consumer runs terraform init, which version will be selected?

The latest version available in the registry.

How does the Terraform Registry handle module versioning?

It stores only the latest version of each module and discards older ones.

It requires module authors to tag releases with semantic version numbers, and Terraform can then reference those tags.

It automatically creates a new version for every commit to the module's source repository.

It assigns version numbers based on the date of publication.

A company manages multiple environments (dev, staging, prod) using the same root module but different Terraform configurations. They want to ensure that the exact same module version is used across all environments to avoid configuration drift. What is the best practice to achieve this?

Use a constraint like "~> 1.2" in all environments.

Use a version constraint like ">= 1.0.0" in all environments so they always get the latest.

Pin the exact module version in each environment's configuration, e.g., version = "1.2.3".

Copy the module code into each environment's repository.

A company has a policy that all module versions must be explicitly pinned to a specific version in production, but development environments may use a range. They use the same Terraform configuration for both environments, parameterized by a variable. What is the best way to implement this policy?

Use a pinned version in the configuration and override it in development with a CLI flag.

Use a variable for the version constraint and set different values per environment.

Use a range constraint in the configuration and rely on the lock file to pin versions in production.

Maintain two separate Terraform configurations, one for production and one for development.

HashiCorp Certified:Terraform Associate

Domain 5Objective 4

5d Manage Module Versions TERRAFORM-ASSOCIATE-004 Practice Questions (Page 3)

Part of the Terraform modules domain, which makes up ~8% of our current practice bank. HashiCorp does not publish an official question count, but from its 60-minute exam (~25–40 total, ~2–3 in this domain), expect 1–1 from this objective — we provide 17 practice questions to prepare you well beyond it. (estimate)

17questions here

4free pages

5concepts

Questions 11–15

11foundation · easy
In a Terraform configuration, how do you specify that a module should use version 1.2.0 from the Terraform Registry?
Select an answer first
12application · medium
A team publishes a module to the public Terraform Registry. They release version 1.0.0, then later release 1.0.1 and 1.1.0. A consumer's configuration uses version = "~> 1.0". When the consumer runs terraform init, which version will be selected?
Select an answer first
13foundation · easy
How does the Terraform Registry handle module versioning?
Select an answer first
14application · medium
A company manages multiple environments (dev, staging, prod) using the same root module but different Terraform configurations. They want to ensure that the exact same module version is used across all environments to avoid configuration drift. What is the best practice to achieve this?
Select an answer first
15expert · hard
A company has a policy that all module versions must be explicitly pinned to a specific version in production, but development environments may use a range. They use the same Terraform configuration for both environments, parameterized by a variable. What is the best way to implement this policy?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to TERRAFORM-ASSOCIATE-004

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “TERRAFORM-ASSOCIATE-004” is a trademark of its owner, used for identification only.