Your team uses a module from the public registry with the constraint version = ">= 1.0.0, < 2.0.0". The lock file currently records version 1.5.0. A teammate runs terraform init -upgrade and the lock file is updated to version 1.9.0. What is the most likely reason for this change?

The teammate manually edited the lock file to version 1.9.0.

The module version 1.5.0 was removed from the registry.

The version constraint was changed to allow 1.9.0.

Version 1.9.0 was released after the initial lock file was created, and -upgrade allowed Terraform to select the highest compatible version.

Where must provider version constraints be declared in a Terraform configuration?

In the required_providers block inside the terraform block

In the variables.tf file using the default argument

In the backend block using the version argument

In the provider block using the version argument

What is the primary purpose of the dependency lock file (.terraform.lock.hcl)?

To record the exact versions of providers and modules used in the last successful run

To prevent concurrent access to the state file

To store the version constraints declared in the configuration

To store the state of the infrastructure managed by Terraform

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 3Objective 1

3a TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 3)

Part of the Develop collaborative Terraform workflows domain, which makes up ~16% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~15–26 in this domain), expect 4–7 from this objective — we provide 15 practice questions to prepare you well beyond it. (estimate)

15questions here

3free pages

6concepts

Questions 11–15

11application · medium
You need to allow the Azure provider version 3.0.0 or any later 3.x version, but you want to prevent upgrades to version 4.0.0 or higher. Which version constraint should you use?
Select an answer first
12application · medium
Your configuration specifies the following provider constraint: version = ">= 4.0.0, < 5.0.0". The available provider versions are 3.9.0, 4.0.0, 4.5.0, 4.9.0, and 5.0.0. Which version will Terraform select?
Select an answer first
13expert · hard
Your team uses a module from the public registry with the constraint version = ">= 1.0.0, < 2.0.0". The lock file currently records version 1.5.0. A teammate runs terraform init -upgrade and the lock file is updated to version 1.9.0. What is the most likely reason for this change?
Select an answer first
14foundation · easy
Where must provider version constraints be declared in a Terraform configuration?
Select an answer first
15foundation · easy
What is the primary purpose of the dependency lock file (.terraform.lock.hcl)?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL

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-AUTHORING-AND-OPERATIONS-PROFESSIONAL” is a trademark of its owner, used for identification only.

3a TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 3)

Questions 11–15

You need to allow the Azure provider version 3.0.0 or any later 3.x version, but you want to prevent upgrades to version 4.0.0 or higher. Which version constraint should you use?

Your configuration specifies the following provider constraint: version = ">= 4.0.0, < 5.0.0". The available provider versions are 3.9.0, 4.0.0, 4.5.0, 4.9.0, and 5.0.0. Which version will Terraform select?

Your team uses a module from the public registry with the constraint version = ">= 1.0.0, < 2.0.0". The lock file currently records version 1.5.0. A teammate runs terraform init -upgrade and the lock file is updated to version 1.9.0. What is the most likely reason for this change?

Where must provider version constraints be declared in a Terraform configuration?

What is the primary purpose of the dependency lock file (.terraform.lock.hcl)?

Keep studying — Develop collaborative Terraform workflows