Terraform-Associate-004 Exam Results

This command will upgrade the plugins to the latest acceptable version within the version constraints specified in the configuration. The other commands do not have an -upgrade option.

 To tell Terraform to stop managing a specific resource without destroying it, you can use the terraform state rm command. This command will remove the resource from the Terraform state, which means that Terraform will no longer track or update the corresponding remote object. However, the object will still exist in the remote system and you can later use terraform import to start managing it again in a different configuration or workspace. The syntax for this command is terraform state rm < address > , where  < address >  is the resource address that identifies the resource instance to remove. For example, terraform state rm aws_instance.ubuntu[1] will remove the second instance of the aws_instance resource named ubuntu from the state. References = : Command: state rm : Moving Resources

This is where Terraform cannot load a provider from, as it requires a compiled binary file that implements the provider protocol. You can load a provider from a plugins directory, a provider plugin cache, or the official HashiCorp distribution on releases.hashicorp.com.

Rationale for Correct Answer: Setting the module version (for registry modules) pins the module release Terraform will use. By pinning the version, Terraform will not “update” the module to newer releases during terraform init -upgrade or terraform get -update unless you change the version constraint. This is the standard way to control module updates and keep module code stable across runs.

Analysis of Incorrect Options (Distractors):

B (lifecycle): lifecycle is for resources, not module blocks.

C (count): count controls how many module instances are created; it doesn’t control module source updates.

D (source): source tells Terraform where the module comes from; it doesn’t prevent updates by itself (a VCS/ref pin would be done in the source string, but the module block argument that achieves this in the typical module workflow is version for registry modules).

Key Concept: Module version pinning to control module upgrades.