Free Practice Questions for HashiCorp Terraform-Associate-004 Exam

Detailed Explanation:

Rationale for Correct Answer:Changing count changes the desired number of resource instances. To reconcile real infrastructure with the updated configuration, you run terraform apply (typically after reviewing the plan). Terraform will create/destroy instances as needed to match the new count value.

Analysis of Incorrect Options (Distractors):

A: Incorrect. terraform init is required when you add/change providers, modules, or backend configuration—not for simple variable value changes.

B: Incorrect. Outputs do not change infrastructure; they only display derived values.

C: Incorrect. You generally should not edit state to reflect intended changes; you apply configuration changes and let Terraform update state.

Key Concept:Terraform workflow: update configuration → plan/apply to converge infrastructure to desired state.

Theversion argumentin a module ensures Terraform uses aspecific versionof a module, preventing unintended updates.

A (source)– Specifies the module source butdoes not control versioning.

B (count)– Controls how many instances of a resource/module exist,not updates.

D (lifecycle)– Controls how resources behavebut does not control module versioning.

Official Terraform Documentation Reference:

Module Version Constraints

The -replace flag is used with the terraform apply command when there is a need to explicitly force Terraform to destroy and then recreate a specific resource during the next apply. This can be necessary in situations where a simple update is insufficient or when a resource must be re-provisioned to pick up certain changes.

Changing the Terraform backend after performing the initial terraform apply is technically possible but strongly discouraged. This is because changing backends can lead to complexities in state management, requiring manual intervention such as state migration to ensure consistency. Terraform ' s documentation and best practices advise planning the backend configuration carefully before applying Terraform configurations to avoid such changes.References = This guidance is consistent with Terraform ' s official documentation, which recommends careful consideration and planning of backend configurations to avoid the need for changes.

Terraformdownloads modules and providersinto the .terraform directory inside the working directory.

A (/tmp/)– Incorrect; modules arenot stored temporarily.

C (In memory)– Incorrect; modules persist on disk.

D (Not cached)– Incorrect; Terraformdoes cache modulesfor efficiency.

Official Terraform Documentation Reference:

Terraform Module Caching

The correct answer is B because Terraform modules have clear input and output boundaries. A child module’s input variables are scoped to that child module and are not automatically exposed back to the parent module. The parent module can pass values into a child module by setting arguments in the module block, but it cannot directly access the child module’s variable namespace. Terraform does not support references such as module.child.var.example. When a child module needs to share information with its caller, the child module must define output values. The parent module can then reference those outputs using syntax such as module.child.output_name. This module interface keeps configurations reusable, predictable, and encapsulated, which is a core Terraform module design principle.

Rationale for Correct Answer: terraform state rm < address > removes a resource from Terraform state without destroying the real infrastructure. After removal, Terraform “forgets” it and will no longer manage it (unless it’s re-imported). That matches the requirement: keep the resource, stop managing it.

Analysis of Incorrect Options (Distractors):

A: Removing the resource block causes Terraform to plan to destroy the resource (because it’s in state but no longer in config), which is the opposite of “keep it.”

B: Changing count can cause Terraform to destroy instances that no longer have an address (depending on indexing), and it doesn’t explicitly “stop managing” a specific existing instance safely.

D: moved blocks are for renaming/refactoring addresses while keeping management; they do not stop managing a resource.

Key Concept: Detaching resources from Terraform management using state subcommands (terraform state rm).

The correct answer is C because local state files are not reliable for shared automation environments such as CI/CD pipelines. A local backend stores state on the machine where Terraform runs, so another pipeline worker usually cannot access that file. Moving Configuration A to a remote backend, such as HCP Terraform, Amazon S3, Azure Storage, or Google Cloud Storage, makes the state centrally available to authorized Terraform runs. Configuration B can then use the terraform_remote_state data source to read Configuration A’s outputs from that remote backend. Option A creates manual value passing and can drift from actual state. Option B fails when the file is not on the pipeline machine. Option D may work technically, but it removes useful separation between network and compute configurations.

terraform validate does not confirm that your infrastructure matches the Terraform state file. It only checks whether the configuration files in a directory are syntactically valid and internally consistent3. To confirm that your infrastructure matches the Terraform state file, you need to use terraform plan or terraform apply with the -refresh-only option.

A module can declare a variable with a default value without requiring the caller to define it. This allows the module to provide a sensible default behavior that can be customized by the caller if needed. References = [Module Variables]