Terraform-Associate-004 HashiCorp Certified: Terraform Associate (004) (HCTA0-004) Free Practice Exam Questions (2026 Updated)

Rationale for Correct Answer: terraform plan -refresh-only refreshes (reconciles) the state with the real infrastructure only for the purpose of the plan output. It does not persist (write) those updates to the state file. To actually update the stored state, you must run terraform apply -refresh-only (or a normal terraform apply). This matches the Terraform CLI objective: plan previews changes; apply makes changes (including writing state).

Analysis of Incorrect Options (Distractors):

A (True): Incorrect because terraform plan does not write state; it only calculates and displays what would change.

Key Concept: The plan vs apply workflow and when Terraform writes state.

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.

HCP Terraform variable sets are specifically designed to define reusable Terraform or environment variables and assign them to multiple workspaces or projects. HashiCorp documentation explicitly identifies provider credentials as a typical variable-set use case: rather than entering the same credential variables independently in every workspace, administrators can create one variable set and apply it to the required workspaces. VCS integration connects workspaces to source-control repositories and can trigger Terraform runs, but it does not provide centralized credential sharing. The terraform_remote_state data source is used to consume root-module output values from another Terraform state and is unrelated to credential distribution. Therefore, A is the correct answer. For current production environments, HashiCorp also recommends dynamic provider credentials where supported because they reduce the security risks associated with long-lived static credentials.

Terraform providers are not part of the Terraform core binary. Providers are distributed separately from Terraform itself and have their own release cadence and version numbers. Providers are plugins that Terraform uses to interact with various APIs, such as cloud providers, SaaS providers, and other services. You can find and install providers from the Terraform Registry, which hosts providers for most major infrastructure platforms. You can also load providers from a local mirror or cache, or develop your own custom providers. To use a provider in your Terraform configuration, you need to declare it in the provider requirements block and optionally configure its settings in the provider block. References = : Providers - Configuration Language | Terraform : Terraform Registry - Providers Overview | Terraform

 This is the command that can add existing resources into Terraform state, by matching them with the corresponding configuration blocks in your files. 

The correct answer is A because Terraform logging is controlled primarily by environment variables. TF_LOG_PATH only tells Terraform where to write the log file; it does not enable logging or choose the log verbosity. To generate detailed logs, you must set TF_LOG. The TRACE level is the most verbose logging level and includes very detailed operational information, including debug-level messages and provider/plugin communication details. Common TF_LOG values include TRACE, DEBUG, INFO, WARN, and ERROR. There is no valid log argument inside the terraform block for enabling runtime logs. Updating the Terraform CLI configuration file is not the documented way to enable standard Terraform logging. The terraform output command only displays output values from state and is unrelated to diagnostic logging.

The Terraform binary version and provider versions do not have to match each other in a single configuration. Terraform allows you to specify provider version constraints in the configuration’s terraform block, which can be different from the Terraform binary version1. Terraform will use the newest version of the provider that meets the configuration’s version constraints2. You can also use the dependency lock file to ensure Terraform is using the correct provider version3. References =

•1: Providers - Configuration Language | Terraform | HashiCorp Developer

•2: Multiple provider versions with Terraform - Stack Overflow

•3: Lock and upgrade provider versions | Terraform - HashiCorp Developer

Detailed Explanation:

Rationale for Correct Answer: The import block declaratively tells Terraform to associate an existing infrastructure object with a Terraform resource address. After the configuration is applied, Terraform imports the existing resource and updates Terraform state so that Terraform can manage it.

Analysis of Incorrect Options (Distractors):

A: Moving resources between state addresses or state files is a state-management operation; it is not the purpose of an import block.

B: The import block does not merge Terraform state files.

C: Modules are downloaded during initialization, not by an import block.

Key Concept: Bringing existing infrastructure under Terraform management by importing it into state.

Sentinel is a policy-as-code framework that integrates with Terraform Cloud to enforce security, compliance, and governance rules. You can enforce rules such as approved AMIs and ensure security best practices. Policies are written in the Sentinel language, not HCL.

Terraform modules are referenced by specifying a source location. This location can be a URL or a file path. However, specifying query parameters such as ?version=vl.6.0 directly within the source path is not a valid or supported method for specifying a module version in Terraform. Instead, version constraints are specified using the version argument within the module block, not as part of the source string.References = This clarification is based on Terraform ' s official documentation regarding module usage, which outlines the correct methods for specifying module sources and versions.

The terraform import command is not part of any other Terraform workflow. It must be explicitly invoked by the user with the appropriate arguments, such as the resource address and the ID of the existing infrastructure to import. References = [Importing Infrastructure]

To import the contents of a local file as a string in Terraform, you can use the built-in file function. By specifying file( " id_rsa.pub " ), Terraform reads the contents of the id_rsa.pub file and uses it as a string within your Terraform configuration. This function is particularly useful for scenarios where you need to include file data directly into your configuration, such as including an SSH public key for provisioning cloud instances.References = This information is a standard part of Terraform ' s functionality with built-in functions, as outlined in Terraform ' s official documentation and commonly used in various Terraform configurations.

Detailed Explanation:

Rationale for Correct Answer:

A is correct because Terraform may replace (destroy and recreate) resources when changes cannot be applied in-place. This behavior depends on the provider and resource type (e.g., immutable infrastructure changes).

B is correct because terraform apply operates on the configuration in the current working directory and uses the currently selected workspace, which determines the state being modified.

Analysis of Incorrect Options (Distractors):

C. You must pass the output of a terraform plan command to it. Incorrect because passing a saved plan file is optional. Running terraform apply without a plan will generate and apply a plan automatically.

D. By default, it does not refresh your state file. Incorrect because Terraform does refresh state by default before applying changes (unless explicitly disabled).

E. You cannot target specific resources. Incorrect because you can use the -target flag to apply changes to specific resources.

Key Concept:Behavior of terraform apply, including execution scope, state refresh, and resource lifecycle (create/update/replace).

Rationale for Correct Answer: A Terraform configuration supports a single cloud block (similar to a single backend configuration). The cloud block defines where Terraform runs (HCP Terraform / Terraform Enterprise) and how the workspace is associated. You cannot connect one configuration to two separate Cloud/Enterprise instances simultaneously using multiple cloud blocks.

Analysis of Incorrect Options (Distractors):

A (True): Incorrect—Terraform does not allow multiple cloud blocks; the configuration can target only one Cloud/Enterprise context at a time.

Key Concept: cloud block constraints and workspace association with HCP Terraform/Terraform Enterprise.

This is not a responsibility of a Terraform provider, as it does not make sense grammatically or logically. A Terraform provider is responsible for exposing resources and data sources based on an API, managing actions to take based on resource differences, and understanding API interactions with some service.

Rationale for Correct Answer: depends_on explicitly adds a dependency edge in Terraform’s graph. By adding depends_on = [azurerm_role_assignment.kv_access] to the web app resource, you force Terraform to create the role assignment first, even if Terraform can’t infer the dependency from attribute references.

Analysis of Incorrect Options (Distractors):

B: create_before_destroy is a lifecycle setting relevant to replacement behavior, not initial create ordering between independent resources.

C: File/block order does not control creation order; Terraform uses its dependency graph.

D: count controls quantity, not ordering.

Key Concept: Dependency graph and explicit dependencies via depends_on.

Detailed Explanation:

Rationale for Correct Answer: Terraform uses providers, which are plugins that allow Terraform to interact with cloud platforms, SaaS platforms, and other APIs. Providers define the resource types and data sources Terraform can manage for a particular platform.

Analysis of Incorrect Options (Distractors):

A: Terraform does not generally provision infrastructure by invoking each vendor ' s CLI tool.

B: Terraform automates infrastructure through provider integrations rather than operating vendors ' graphical user interfaces.

D: Terraform providers typically communicate with the service ' s existing API; HashiCorp does not create replacement APIs for each cloud vendor.

Key Concept: Terraform ' s provider architecture abstracts interactions with different infrastructure platforms and APIs.

Rationale for Correct Answer: Terraform uses a declarative approach: you define the desired end state of infrastructure in configuration files that can be version-controlled and repeatedly applied. Terraform then computes an execution plan to reach that state. This is a key distinction from ad-hoc API calls or hand-written scripts that typically manage infrastructure in a more imperative and less state-aware way.

Analysis of Incorrect Options (Distractors):

B: Incorrect because Terraform is not “merely a wrapper.” It provides a workflow (state, diff/plan, dependency graph, drift detection) that fundamentally changes how infrastructure is managed.

C: Incorrect because Terraform does not replace provider APIs; providers still use the underlying cloud/service APIs.

D: Incorrect because Terraform is primarily declarative, not imperative scripting to force a specific order (ordering is derived from dependencies).

Key Concept: Declarative desired-state configuration, plan/apply workflow, and version-controlled IaC.

These are features of Terraform Cloud, which is a hosted service that provides a web-based UI, remote state storage, remote operations, collaboration features, and more for managing your Terraform infrastructure.