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

Questions 1–5

1. 1application · medium

   A platform team publishes a networking module to the private Terraform Registry. They want consumers to automatically receive patch releases (e.g., 1.2.4 → 1.2.5) but NOT minor or major upgrades, which may introduce breaking changes. Which version constraint should the team document for consumers to use in their module source blocks?

   • Aversion = "= 1.2.4"
   • Bversion = "~> 1.2"
   • Cversion = "~> 1.2.0"
   • Dversion = ">= 1.2.0, < 2.0.0"
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Before upgrading a module to a new version, what should a Terraform practitioner do to understand the impact on existing infrastructure?

   • ACheck the module's README only, without running any commands.
   • BDelete the state file and re-import all resources.
   • CRun `terraform plan` after updating the version constraint to review the proposed changes.
   • DRun `terraform apply` immediately to see what happens.
   Reveal Solution Discussion Select an answer first
4. 3expert · hard

   A team publishes a module to the public Terraform Registry. They accidentally release version 2.0.0 with a critical bug. They want to prevent new consumers from using this version while allowing existing consumers who already use it to continue. What is the best approach?

   • APublish version 2.0.1 with the fix and document that 2.0.0 should be avoided.
   • BDelete version 2.0.0 from the registry.
   • CYank version 2.0.0 so it cannot be used.
   • DOverwrite version 2.0.0 with the fixed code.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   What is the primary benefit of using versioned modules in a Terraform configuration?

   • AThey reduce the number of resources that Terraform needs to manage.
   • BThey allow multiple teams to share the same module code without conflicts.
   • CThey automatically fix bugs in the module without requiring a configuration update.
   • DThey ensure that the same module version is used across all environments, making deployments predictable and auditable.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A company uses a module with version = ">= 1.0.0, < 2.0.0" in all environments. They want to ensure that a specific environment (staging) uses version 1.5.0 while production uses the latest 1.x. What is the best way to achieve this?

   • AUse a constraint of "~> 1.5" in staging and ">= 1.0.0, < 2.0.0" in production.
   • BUse the lock file to pin staging to 1.5.0 and production to the latest.
   • CUse a separate branch of the configuration for staging with a pinned version.
   • DUse a variable for the version constraint and set it to "1.5.0" in staging and ">= 1.0.0, < 2.0.0" in production.
   Reveal Solution Discussion Select an answer first