A configuration uses module version `1.0.0` with a constraint of `~> 1.0`. The maintainer publishes version `1.1.0`. What happens when a user runs `terraform init -upgrade`?

Terraform keeps version `1.0.0` because the lock file is not updated

Terraform downloads version `2.0.0` because it is the latest

Terraform fails because the version constraint is too restrictive

Terraform downloads version `1.1.0` because it satisfies the constraint

A module maintainer needs to rename an input variable that is used by many consumers. What is the recommended strategy to manage this breaking change?

Remove the variable and hardcode the value in the module

Add a new variable with the desired name and deprecate the old one, keeping both functional for a transition period

Immediately rename the variable and publish a new version

Change the variable type to accept both old and new names

You are upgrading a module reference in your Terraform configuration from version `1.0.0` to `2.0.0`. The module's changelog states that the `azurerm_storage_account` resource was replaced with `azurerm_storage_account_v2` and the `account_tier` variable was removed. After updating the source reference and running `terraform plan`, you see that the plan shows the storage account being destroyed and recreated. What is the most appropriate next step?

Downgrade back to version `1.0.0` and create a feature request to keep the old resource available.

Update your configuration to remove the `account_tier` variable and adjust any outputs or dependencies, then run `terraform plan` again.

Run `terraform apply` to accept the replacement, then update any references to the removed variable in your configuration.

Use `terraform state mv` to rename the resource in state from the old name to the new name, avoiding recreation.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 4Objective 3

4c TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 5)

Part of the Create, maintain, and use Terraform modules domain, which makes up ~13% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~12–21 in this domain), expect 3–5 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

6concepts

Questions 21–23

21foundation · easy
A configuration uses module version `1.0.0` with a constraint of `~> 1.0`. The maintainer publishes version `1.1.0`. What happens when a user runs `terraform init -upgrade`?
Select an answer first
22foundation · easy
A module maintainer needs to rename an input variable that is used by many consumers. What is the recommended strategy to manage this breaking change?
Select an answer first
23expert · hard
You are upgrading a module reference in your Terraform configuration from version `1.0.0` to `2.0.0`. The module's changelog states that the `azurerm_storage_account` resource was replaced with `azurerm_storage_account_v2` and the `account_tier` variable was removed. After updating the source reference and running `terraform plan`, you see that the plan shows the storage account being destroyed and recreated. What is the most appropriate next step?
Select an answer first

Finished these 3 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.

4c TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 5)

Questions 21–23

A configuration uses module version `1.0.0` with a constraint of `~> 1.0`. The maintainer publishes version `1.1.0`. What happens when a user runs `terraform init -upgrade`?

A module maintainer needs to rename an input variable that is used by many consumers. What is the recommended strategy to manage this breaking change?

Keep studying — Create, maintain, and use Terraform modules