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

Rationale for Correct Answer: Data sources are referenced with: data. < TYPE > . < NAME > . < ATTRIBUTE > .For a vSphere datacenter data source, the correct reference to its id is:data.vsphere_datacenter. < name > .id.✅ Given the options, only A follows the correct data-source addressing pattern and includes the .id attribute.

Analysis of Incorrect Options (Distractors):

B: Incorrect—missing the data. prefix, so it looks like a managed resource reference.

C: Incorrect—missing the attribute (.id).

D: Incorrect—missing the data source type and name.

Key Concept: Correct HCL reference syntax for data sources.

When you use a remote backend that needs authentication, HashiCorp recommends that you:

The terraform state file is locked when a Terraform operation that could write state is in progress. This prevents concurrent state operations that could corrupt the state. The forbidden actions when the state file is locked are those that could write state, such as terraform apply, terraform destroy, terraform refresh, terraform taint, terraform untaint, terraform import, and terraform state *. The terraform validate command is also forbidden, because it requires an initialized working directory with the state file. The allowed actions when the state file is locked are those that only read state, such as terraform plan, terraform show, terraform output, and terraform console. References = [State Locking] and [Command: validate]

The correct syntax to pass a variable from the root module to a child module isservers = var.num_servers. Terraform uses dot notation to reference variables.

Rationale for Correct Answer: Terraform is designed to be idempotent. If the configuration and real infrastructure match the state, a subsequent terraform apply will show no changes and perform no actions.

Analysis of Incorrect Options (Distractors):

A: Terraform does not recreate resources unless the plan requires it (configuration change, forced replacement, drift that requires replacement, etc.).

B: Terraform won’t create duplicates unless the configuration indicates multiple instances (e.g., count, for_each) or a new resource address.

C: The state was already written during the first successful apply; a second apply doesn’t “re-apply to the state file” as a distinct action.

Key Concept: Terraform idempotency and convergence to desired state.

Detailed Explanation:

Rationale for Correct Answer: In Terraform, each “provider” plugin is responsible for interacting with a specific API surface (for example: AWS, AzureRM, Google, Kubernetes). If you want to manage resources across multiple cloud platforms, you typically configure and use the corresponding provider plugins (e.g., aws, azurerm, google). This matches Terraform’s provider model: providers are the integration points to external services.

Analysis of Incorrect Options (Distractors):

B: Incorrect. While a single provider can sometimes manage multiple services within a platform, managing different cloud providers (AWS vs Azure vs GCP) requires their respective provider plugins/configurations.

Key Concept: Providers are Terraform’s integration layer to each infrastructure platform/API.

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.

Detailed Explanation:

Rationale for Correct Answer: Terraform requires provider aliases when you configure the same provider multiple times in one configuration. You must define the second AWS provider with an alias, then explicitly tell the resource to use it with the provider meta-argument:

provider " aws " {

region = " us-east-1 "

}

provider " aws " {

alias = " west "

region = " us-west-2 "

}

resource " aws_instance " " example_us_west_2 " {

provider = aws.west

ami = data.aws_ami.ubuntu.id

instance_type = " t3.micro "

}

This is a core Terraform objective: selecting the correct provider configuration for a resource when multiple instances exist.

Analysis of Incorrect Options (Distractors):

B: Incorrect. Provider blocks do not support the syntax provider " aws " " west " { ... }. Aliasing is done with alias = " west " .

C: Incorrect. You cannot invent a new provider type name like aws_west. The provider remains aws; you differentiate configurations via alias.

D: Incorrect. Terraform will not automatically choose between multiple provider configurations for the same provider; you must disambiguate using aliases and provider = ....

Key Concept: Provider aliases and the provider meta-argument for multi-region (or multi-account) deployments.

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.

Importing Existing Resources: Theterraform importcommand brings resources already deployed in a cloud environment into Terraform’s state file, allowing Terraform to manage them.

Workflow Usage: Importing is vital when managing resources created outside of Terraform or those in place before Terraform adoption.

Refer to Terraform’s import command documentation.

Not all modules published on the official Terraform Module Registry have been verified by HashiCorp. While HashiCorp verifies some modules, there are many community-contributed modules that are not verified. Verified modules have a " Verified " badge indicating that HashiCorp has reviewed them for security and best practices, but the registry also includes unverified modules.

Terraform workspaces allow you to create multiple states but still be associated with your current code. Workspaces are like “environments” (e.g. staging, production) for the same configuration. You can use workspaces to spin up a copy of your production deployment for testing purposes without having to configure a new state backend. Terraform data sources, local values, and modules are not features that allow you to create multiple states. References = Workspaces and How to Use Terraform Workspaces

The key principle of infrastructure as code that is not listed among the options is golden images. Golden images are pre-configured, ready-to-use virtual machine images that contain a specific set of software and configuration. They are often used to create multiple identical instances of the same environment, such as for testing or production. However, golden images are not a principle of infrastructure as code, but rather a technique that can be used with or without infrastructure as code. The other options are all key principles of infrastructure as code, as explained below:

Self-describing infrastructure: This means that the infrastructure is defined in code that describes its desired state, rather than in scripts that describe the steps to create it. This makes the infrastructure easier to understand, maintain, and reproduce.

Idempotence: This means that applying the same infrastructure code multiple times will always result in the same state, regardless of the initial state. This makes the infrastructure consistent and predictable, and avoids errors or conflicts caused by repeated actions.

Versioned infrastructure: This means that the infrastructure code is stored in a version control system, such as Git, that tracks the changes and history of the code. This makes the infrastructure code reusable, auditable, and collaborative, and enables practices such as branching, merging, and rollback. References = [Introduction to Infrastructure as Code with Terraform], [Infrastructure as Code in a Private or Public Cloud]

Rationale for Correct Answer: A parent/root module can only read values from a child module if the child module exports them via an output block. The error indicates vnet_id is not an exported output from module.my_network. Defining output " vnet_id " { value = ... } inside the networking (child) module makes module.my_network.vnet_id valid.

Analysis of Incorrect Options (Distractors):

A: Incorrect—Terraform does not use module. < name > .outputs. < output > ; module outputs are referenced directly as module. < name > . < output > .

B: Incorrect—variables are inputs to a module, not values exported from it.

C: Incorrect—missing the module. prefix and still uses an invalid .outputs path.

Key Concept: Module outputs are the contract for exposing child module values to the root/parent.

Confidentiality: UsingHCP Terraform/Terraform Cloud’s private registrykeeps the module configurations within your organization, ensuring privacy and access control.

Version Constraints: The private registry supportssemantic versioning, allowing you to manage versions of your modules as Terraform does natively.

Browsable Directory: The private registry offers a user interface to browse modules, making it easy for users within the organization to locate and manage modules.

This setup aligns with HashiCorp’s design forprivate registry supportin Terraform, meeting all listed requirements for secure, version-controlled, and searchable module storage.

In Terraform, theresource nameis the second argument in the resource block.

The structure of a resource block is:

resource " provider_resource_type " " resource_name " {

# Configuration settings

}

Here, the provider type isgoogle_compute_instance, and theresource nameis " main " .

The name " test " is simply the value assigned to the name attribute, which is unrelated to the Terraform resource name.

" google " and " compute_instance " are part of the provider and resource type, not the resource name.

Official Terraform Documentation Reference:

Terraform Resource Documentation

Detailed Explanation:

Rationale for Correct Answer:

A: IaC enables a plan/review workflow (for Terraform: terraform plan) where changes can be inspected and approved before applying, reducing accidental outages.

E: Declarative IaC helps reduce configuration drift because desired state is defined in code and Terraform continuously reconciles differences during plans/applies (drift becomes visible and correctable).

Analysis of Incorrect Options (Distractors):

B: Incorrect. Auto-scaling is a capability of specific platforms/services (e.g., AWS ASG), not a guaranteed property of IaC.

C: Incorrect. IaC reduces the chance of mistakes, but it does not make incorrect configurations impossible—bad code can still be applied.

D: Incorrect. Zero-downtime updates require architecture and deployment strategies (blue/green, rolling updates, etc.); IaC alone doesn’t guarantee it.

Key Concept: Reliability improvements from IaC: reviewable change plans and reduced drift through declarative desired state.

The terraform refresh-only command is intended to detect state file drift. This command synchronizes the state file with the actual infrastructure, updating the state to reflect any changes that have occurred outside of Terraform.

From terraform plan -refresh-only:

" Use this to detectdrift, i.e., changes made outside of Terraform. "

It compares actual infrastructure to what ' s recorded in the state file.

In Terraform, the backend configuration, which includes details about where and how state is stored, is specified within the terraform block of your configuration. This block is the correct place to define the backend type and its configuration parameters, such as the location of the state file for a local backend or the bucket details for a remote backend like S3.References = This practice is outlined in Terraform ' s core documentation, which provides examples and guidelines on how to configure various aspects of Terraform ' s behavior, including state backends .