Free HashiCorp Terraform-Associate-004 Practice Exam with Questions & Answers | Set: 7

Terraform providers are not always installed from the Internet. There are other ways to install provider plugins, such as from a local mirror or cache, from a local filesystem directory, or from a network filesystem. These methods can be useful for offline or air-gapped environments, or for customizing the installation process. You can configure the provider installation methods using the provider_installation block in the CLI configuration file.

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).

This command will initialize the new backend and prompt you to migrate the existing state file to the new location3. The other commands are not relevant for this task.

This is the Terraform style convention for indenting a nesting level compared to the one above it. The other options are not consistent with the Terraform style guide.

The error messageindicates an authentication issue (403 - Access Denied), which requiresdebugging Terraform logs.

Setting TF_LOG=DEBUG enablesdetailed logs, providing insights into API requests, state loading, and authentication errors.

Terraformdoes not log errors in /var/log/terraform.log or syslog, making optionsC and D incorrect.

A (terraform login)is only relevant forTerraform Cloud, but this error appears to be related toprovider authentication.

Official Terraform Documentation Reference:

Debugging Terraform

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]

Detailed Explanation:

Rationale for Correct Answer: A local value in Terraform allows you to define reusable expressions within a module. By combining the random_id and a variable into a local value, you can reference it multiple times without repeating the expression. This improves readability and maintainability, which aligns with Terraform best practices for configuration design.

Example:

locals {

combined_name = " ${random_id.example.hex}-${var.name} "

}

You can then reuse local.combined_name throughout your configuration.

Analysis of Incorrect Options (Distractors):

A. Use a data source. Incorrect because data sources are used to fetch information from existing infrastructure, not to define reusable expressions.

B. Use a module. Incorrect because modules are used for grouping and reusing infrastructure components, not for simple expression reuse.

D. Add an output value. Incorrect because outputs are used to expose values outside a module, not for internal reuse within the same configuration.

Key Concept: Local values ( locals ) are used to simplify and reuse expressions within a Terraform configuration.

Rationale for Correct Answer: terraform plan -destroy does not destroy anything. It only creates a plan that proposes destroying all managed resources. Actual destruction happens only when you run terraform destroy or terraform apply with an approved destroy plan.

Analysis of Incorrect Options (Distractors):

A: Does trigger destruction (interactive approval by default).

B: Incorrect because terraform plan -destroy does not perform destruction.

D: Does trigger destruction and skips the interactive approval prompt.

Key Concept: Difference between planning a destroy and executing a destroy.

Rationale for Correct Answer: terraform apply -replace=ADDRESS forces Terraform to replace the specified resource during the next apply, meaning it will plan to destroy and then recreate it (or create-before-destroy if the resource supports it and the graph/lifecycle allows). This is used when a resource is unhealthy, drifted in a way that’s hard to correct, or you want a fresh instance without changing configuration.

Analysis of Incorrect Options (Distractors):

A: Incorrect—-replace is not “destroy only”; it’s destroy + recreate.

B: Incorrect—ignoring changes is done with lifecycle ignore_changes, not -replace.

D: Incorrect—destroying everything is terraform destroy (or apply with all resources removed), not -replace.

Key Concept: Forcing resource replacement using -replace in the apply workflow.

The reason why the apply fails after adding a new provider to the configuration and immediately running terraform apply in the CD using the local backend is because Terraform needs to install the necessary plugins first. Terraform providers are plugins that Terraform uses to interact with various cloud services and other APIs. Each provider has a source address that determines where to downloadit from. When Terraform encounters a new provider in the configuration, it needs to run terraform init first to install the provider plugins in a local directory. Without the plugins, Terraform cannot communicate with the provider and perform the desired actions. References = [Provider Requirements], [Provider Installation]