5d Manage Module Versions TERRAFORM-ASSOCIATE-004 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   A team uses a Terraform module from the public registry. Why is it important to pin the module to a specific version rather than always using the latest version?

   • ATo make the module source argument shorter and easier to read in the configuration.
   • BTo guarantee that the module works with the exact version of Terraform being used.
   • CTo ensure that the infrastructure configuration remains reproducible and that upgrades happen only when the team explicitly changes the version constraint.
   • DTo prevent Terraform from downloading any module code from the registry, which improves security.
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A team manages a production environment using a module pinned to version 3.0.0. They need to upgrade to version 3.1.0, which introduces a new required variable. The team wants to minimize downtime and ensure the upgrade is reversible. What is the recommended approach?

   • AUpdate the version constraint to 3.1.0, add the new variable, run terraform plan, and apply if the plan is acceptable.
   • BRun terraform apply with the new version without updating the variable, and rely on Terraform to use a default.
   • CUse a version constraint of ">= 3.0.0, < 4.0.0" and run terraform init -upgrade.
   • DDelete the existing infrastructure and recreate it with the new module version.
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A team is upgrading a module from version 4.0.0 to 5.0.0. The module's changelog indicates that a resource attribute was renamed. After updating the version constraint and running terraform plan, the plan shows that Terraform wants to replace the resource instead of updating it in place. What is the most likely reason?

   • AThe renamed attribute is an immutable argument, so Terraform must replace the resource.
   • BThe module author used a different provider version in the new module release.
   • CTerraform does not support attribute renames and always replaces resources.
   • DThe team forgot to run terraform init -upgrade.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   To reference a specific published version of a module from the Terraform Registry, what must be included in the module block?

   • AThe `version` argument with the desired version number.
   • BThe `source` argument must include the version number.
   • CThe `ref` argument with the Git commit hash.
   • DThe `tag` argument with the release tag name.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A developer is upgrading a module from version 2.0.0 to 2.1.0. After updating the version constraint and running terraform init, they run terraform plan. The plan shows no changes to resources. What does this indicate?

   • AThe module version constraint is still pointing to 2.0.0.
   • BThe module upgrade was successful and the new version's configuration is identical in effect to the old version.
   • CTerraform is unable to detect changes between module versions.
   • DThe developer forgot to run terraform init, so the old version is still being used.
   Reveal Solution Discussion Select an answer first