A team uses Terraform with a provider constraint of `version = "~> 2.0"`. They run `terraform init` and the lock file records version 2.3.0. Later, they run `terraform init` again without any changes. What will happen?

Terraform will fail because the lock file is outdated.

Terraform will upgrade to the latest version allowed by the constraint, such as 2.9.0.

Terraform will use version 2.3.0 as recorded in the lock file.

Terraform will ask the user to confirm the provider version.

What does the output of terraform init indicate about provider installation?

It shows the source code of the provider.

It shows the credentials used to access the provider.

It shows the state of the infrastructure.

It shows the exact version of each provider that was installed.

A user is working in an offline environment and needs to install a specific version of the vSphere provider. They have downloaded the provider binary and placed it in a local directory. What should they do to make Terraform use this local provider?

Run `terraform init -provider-path=/local/directory`.

Place the provider binary in the same directory as the Terraform configuration and run `terraform init`.

Set the `TF_PROVIDER_PATH` environment variable to the local directory.

Configure a filesystem mirror in `.terraformrc` and set the `source` in the `required_providers` block to the local path.

What is the primary purpose of the .terraform.lock.hcl file in a Terraform configuration?

To prevent multiple users from running terraform apply at the same time.

To store the credentials for the cloud provider.

To record the exact provider versions used so that future runs use the same versions.

To store the state of the infrastructure managed by Terraform.

HashiCorp Certified:Terraform Associate

Domain 2Objective 1

2a Install and Version Terraform Providers TERRAFORM-ASSOCIATE-004 Practice Questions (Page 1)

Part of the Terraform fundamentals domain, which makes up ~12% of our current practice bank. HashiCorp does not publish an official question count, but from its 60-minute exam (~25–40 total, ~3–5 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 1–5

1foundation · easy
After changing a provider version constraint in the configuration, which command should you run to update the installed providers?
Select an answer first
2application · medium
A team uses Terraform with a provider constraint of `version = "~> 2.0"`. They run `terraform init` and the lock file records version 2.3.0. Later, they run `terraform init` again without any changes. What will happen?
Select an answer first
3foundation · easy
What does the output of terraform init indicate about provider installation?
Select an answer first
4application · medium
A user is working in an offline environment and needs to install a specific version of the vSphere provider. They have downloaded the provider binary and placed it in a local directory. What should they do to make Terraform use this local provider?
Select an answer first
5foundation · easy
What is the primary purpose of the .terraform.lock.hcl file in a Terraform configuration?
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.