Exam Terraform Associate topic 1 question 125 discussion

The registry uses tags to identify module versions. Release tag names must be a semantic version, which can optionally be prefixed with a v . For example, v1. 0.4 and 0.9.

answer is C: Once a module is published, you can release a new version of a module by simply pushing a properly formed Git tag. x.y.z tags for releases. The registry uses tags to identify module versions. Release tag names must be a semantic version, which can optionally be prefixed with a v. For example, v1.0.4 and 0.9.2. To publish a module initially, at least one release tag must be present. Tags that don't look like version numbers are ignored. https://developer.hashicorp.com/terraform/registry/modules/publish

C is the correct answer.

C. The release tags in the associated repo. When publishing a module to the Terraform Module Registry, the module version is typically specified using Git tags in the associated Git repository. Terraform retrieves the module from the registry using the provider's source argument, which includes the module's owner, name, and version. By specifying the version in the source argument of your module, Terraform will download that specific version of the module from the registry.

A module's version is specified using the release tag names. So, the right answer is C.

x.y.z tags for releases. The registry uses tags to identify module versions. Release tag names must be a semantic version, which can optionally be prefixed with a v. For example, v1.0.4 and 0.9.2. To publish a module initially, at least one release tag must be present. Tags that don't look like version numbers are ignored. ANSWER C

https://www.terraform.io/registry/modules/publish

C makes sense to me