A team is using a module from the public registry. They want to ensure that the module version they use is always the same across all environments (dev, staging, prod). They also want to be able to update the module version in a controlled way. Which approach best meets these requirements?

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

Do not specify a version and rely on the latest version.

Use a version constraint like version = "~> 1.2" in each environment.

Use a version constraint like version = ">= 1.0.0" in each environment.

A team is using a module that has a required input variable named environment. The module is used in two different configurations: one for production and one for development. The team wants to ensure that the production configuration cannot accidentally set the environment variable to 'dev'. What is the best approach?

Use a separate module for production that does not have the environment variable.

Hardcode the environment variable in the production configuration.

Use a terraform workspace to differentiate between environments.

Use a variable validation block in the module to restrict the allowed values.

A configuration uses the same module source twice to create two separate VPCs. What is the purpose of the local name given to each module instance?

It specifies the order in which the modules will be applied during terraform apply.

It determines the version of the module that will be downloaded from the registry.

It uniquely identifies each module instance so their resources can be managed and referenced independently.

It defines the cloud provider region where the module's resources will be created.

A configuration has two modules: module "network" and module "app". The app module references an output from the network module. The team wants to ensure that the network module is always created before the app module, even if the output reference is removed in the future. What is the best way to enforce this?

Rely on the implicit dependency created by the output reference.

Use a null_resource in the network module that the app module depends on.

Add an explicit depends_on block in the app module block that references the network module.

Create the network module resources in the root module and pass them to the app module.

A resource was previously at the address aws_subnet.main. After refactoring, it is now at module.network.aws_subnet.main. Which moved block correctly records this change?

moved { from = aws_subnet.main to = module.network.aws_subnet.main }

moved { from = module.network.aws_subnet.main to = aws_subnet.main }

moved { old = aws_subnet.main new = module.network.aws_subnet.main }

moved { source = aws_subnet.main target = module.network.aws_subnet.main }

HashiCorp Certified:Terraform Associate

Domain 5Objective 3

5c Use Modules in Configuration 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 16 practice questions to prepare you well beyond it. (estimate)

16questions here

4free pages

7concepts

Questions 11–15

11expert · hard
A team is using a module from the public registry. They want to ensure that the module version they use is always the same across all environments (dev, staging, prod). They also want to be able to update the module version in a controlled way. Which approach best meets these requirements?
Select an answer first
12expert · hard
A team is using a module that has a required input variable named environment. The module is used in two different configurations: one for production and one for development. The team wants to ensure that the production configuration cannot accidentally set the environment variable to 'dev'. What is the best approach?
Select an answer first
13foundation · easy
A configuration uses the same module source twice to create two separate VPCs. What is the purpose of the local name given to each module instance?
Select an answer first
14expert · hard
A configuration has two modules: module "network" and module "app". The app module references an output from the network module. The team wants to ensure that the network module is always created before the app module, even if the output reference is removed in the future. What is the best way to enforce this?
Select an answer first
15foundation · easy
A resource was previously at the address aws_subnet.main. After refactoring, it is now at module.network.aws_subnet.main. Which moved block correctly records this change?
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.

5c Use Modules in Configuration TERRAFORM-ASSOCIATE-004 Practice Questions (Page 3)

Questions 11–15

A team is using a module from the public registry. They want to ensure that the module version they use is always the same across all environments (dev, staging, prod). They also want to be able to update the module version in a controlled way. Which approach best meets these requirements?

A configuration uses the same module source twice to create two separate VPCs. What is the purpose of the local name given to each module instance?

A resource was previously at the address aws_subnet.main. After refactoring, it is now at module.network.aws_subnet.main. Which moved block correctly records this change?

Keep studying — Terraform modules