A module maintainer has updated a module and wants to publish version `1.2.0` to a private Terraform registry. What is the required step to make this version available to consumers?

Tag the module's source repository with the version `v1.2.0`

Upload the module code to a file share

Create a new branch in the repository named `1.2.0`

Update the module's README file with the new version number

A configuration currently uses module version `1.0.0`. The maintainer has published version `1.1.0` with new features. What must a consumer do to use the new version?

Delete the `.terraform` directory and re-run `terraform init`

Update the `version` argument in the module block to `1.1.0`

Change the module source to a different registry

Run `terraform init -upgrade` without changing the configuration

A configuration upgrades a module from version `1.0.0` to `2.0.0`. The new version changes an output name. What is the likely impact on the Terraform state and plan?

The state is deleted and recreated from scratch

The state is unchanged, but the plan may show changes if the new module configuration differs

The plan will fail because the output name changed

The state is automatically migrated to match the new module version

Your team maintains a Terraform module that is used by multiple projects. You need to remove a variable that has been deprecated for several releases. The module is currently at version `3.2.0`. What is the most appropriate way to remove the variable?

Remove the variable and publish a patch version `3.2.1`.

Publish version `4.0.0` with the variable removed, and document the removal in the changelog.

Keep the variable but make it optional with a default value.

Remove the variable in the next minor version, `3.3.0`, since it has been deprecated.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 4Objective 3

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

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 11–15

11foundation · easy
A module maintainer has updated a module and wants to publish version `1.2.0` to a private Terraform registry. What is the required step to make this version available to consumers?
Select an answer first
12application · medium
You have published version `1.0.0` of a module to your private registry. You later make a backward-compatible change by adding a new optional variable. According to semantic versioning, what version should you publish next?
Select an answer first
13foundation · easy
A configuration currently uses module version `1.0.0`. The maintainer has published version `1.1.0` with new features. What must a consumer do to use the new version?
Select an answer first
14foundation · easy
A configuration upgrades a module from version `1.0.0` to `2.0.0`. The new version changes an output name. What is the likely impact on the Terraform state and plan?
Select an answer first
15expert · hard
Your team maintains a Terraform module that is used by multiple projects. You need to remove a variable that has been deprecated for several releases. The module is currently at version `3.2.0`. What is the most appropriate way to remove the variable?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back 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.