When using a module block to reference a module stored on the public Terraform Module Registry, how do you specify version 1.0.0?

When using a module block to reference a module stored on the public Terraform Module Registry, how do you specify version 1.0.0?

• A. Add 'version = "1.0.0"' attribute
• B. Specify 'id = "1.0.0"' in the block
• C. Write version as a variable
• D. Add versioning notice in the comments

Answer: (A)

When referencing a module stored on the public Terraform Module Registry, including the version attribute in the module block is the correct approach to specify which version to use. By adding the 'version = "1.0.0"' attribute, you are explicitly instructing Terraform to utilize that specific version of the module. This ensures compatibility, as different versions of a module might have different configurations, features, or fixes. Using version control in this manner allows for better management of infrastructure as code, as it prevents unexpected changes or behavior that could arise if a module were to update automatically to a newer version without your knowledge. In contrast, other options do not conform to how module versions are specified in Terraform. For instance, specifying 'id = "1.0.0"' is not a recognized syntax for defining module versions. Using a variable to indicate the version of a module may introduce complexity and may not guarantee that the exact version is utilized. Comments do not affect the execution of Terraform, so adding a versioning notice there wouldn't have any impact on the module reference.

When referencing a module stored on the public Terraform Module Registry, including the version attribute in the module block is the correct approach to specify which version to use. By adding the 'version = "1.0.0"' attribute, you are explicitly instructing Terraform to utilize that specific version of the module. This ensures compatibility, as different versions of a module might have different configurations, features, or fixes.

Using version control in this manner allows for better management of infrastructure as code, as it prevents unexpected changes or behavior that could arise if a module were to update automatically to a newer version without your knowledge.

In contrast, other options do not conform to how module versions are specified in Terraform. For instance, specifying 'id = "1.0.0"' is not a recognized syntax for defining module versions. Using a variable to indicate the version of a module may introduce complexity and may not guarantee that the exact version is utilized. Comments do not affect the execution of Terraform, so adding a versioning notice there wouldn't have any impact on the module reference.