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

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.

Changes invoked by terraform apply take effect once the resource provider has fulfilled the request, not after Terraform has updated the state file or immediately. The state file is only a reflection of the real resources, not a source of truth.

It is not a best practice to store secret data in the same version control repository as your Terraform configuration, as it could expose your sensitive information to unauthorized parties or compromise your security. You should use environment variables, vaults, or other mechanisms to store and provide secret data to Terraform.

When upgrading a provider,you must run terraform init -upgrade to install the new version.

Thisdownloads the latest provider versionand updates the local dependency cache.

terraform refresh(A)only updates the state file but doesnotupgrade providers.

terraform apply -upgrade(C)isnot a valid command.

terraform version can be upgraded separately, but(D)does not install a new provider version.

Official Terraform Documentation Reference:

Upgrading Providers in Terraform

The two steps that are required to provision new infrastructure in the Terraform workflow are init and apply. The terraform init command initializes a working directory containing Terraform configuration files. It downloads and installs the provider plugins that are needed for the configuration, and prepares the backend for storing the state. The terraform apply command applies the changes required to reach the desired state of the configuration, as described by the resource definitions in the configuration files. It shows a plan of the proposed changes and asks for confirmation before making any changes to the infrastructure. References = [The Core Terraform Workflow], [Initialize a Terraform working directory with init] , [Apply Terraform Configuration with apply]

Rationale for Correct Answer: The pessimistic constraint operator ~ > allows updates that do not change the leftmost specified digits beyond what’s declared. With ~ > 11.0, Terraform allows any version that is > = 11.0 but < 12.0 (i.e., any 11.x release). This pins to the major version while allowing minor/patch updates.

Analysis of Incorrect Options (Distractors):

A: Incorrect—this excludes exactly 11.0 and doesn’t express the upper bound that ~ > imposes.

B: Incorrect—missing the upper bound; ~ > always implies an upper limit.

D: Incorrect— > = 11.0.0 and < 11.1.0 corresponds to ~ > 11.0.0, not ~ > 11.0.

Key Concept: Module version constraints using the pessimistic (~ > ) operator.

The required_providers block is used to specify the provider versions that the configuration can work with. The version argument accepts a version constraint string, which must be enclosed in double quotes. The version constraint string can use operators such as  > =, ~ > , =, etc. to specify the minimum, maximum, or exact version of the provider. For example, version = " > = 3.1 "  means that theconfiguration can work with any provider version that is 3.1 or higher. References = [Provider Requirements] and [Version Constraints]

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: Data sources are referenced using the address format:data. < DATA_SOURCE_TYPE > . < NAME > . < ATTRIBUTE > Here, the type is aws_ami, the name is web, and the attribute is id, so the correct reference is data.aws_ami.web.id.

Analysis of Incorrect Options (Distractors):

A (aws_ami.web.id): Incorrect because it omits the required data. prefix. This looks like a managed resource reference, not a data source.

B (web.id): Incorrect because Terraform references must include the full address (type and name); web alone is ambiguous.

D (data.web.id): Incorrect because it omits the data source type (aws_ami).

Key Concept: Terraform addressing and attribute references for data sources.

Detailed Explanation:

Rationale for Correct Answer: The .terraform directory is created by terraform init and is used to store downloaded provider plugins , module code , and other initialization artifacts (such as backend-related data and dependency selections used by the working directory). This directory is typically not committed to version control.

Analysis of Incorrect Options (Distractors):

A: Incorrect. State is usually stored as terraform.tfstate in the working directory for local state, or remotely in a backend (not inside .terraform as the primary location).

B: Incorrect. Terraform doesn’t store “converted API calls” in .terraform; it computes provider actions during plan/apply.

C: Incorrect. Provider credentials and .tfvars files are not stored in .terraform by design; secrets should be handled via variables, env vars, Vault, or HCP Terraform sensitive variables.

Key Concept: .terraform contains init-time artifacts : providers, modules, and metadata needed for the working directory.

Rationale for Correct Answer (C):

Credentials should not be hardcoded in Terraform files. Best practice is to configure them via environment variables or secret managers.

Analysis of Incorrect Options:

A: Shared servers introduce risk and drift.

B: Storing secrets in config/version control is insecure.

D: Incorrect since option C is valid.

Key Concept:

Separation of credentials from code is a Terraform security best practice.

The default “local” Terraform backend stores the state file in a local file named terraform.tfstate, which can be used to track and manage the state of your infrastructure3.

Not all standard backend types support state locking and remote operations like plan, apply, and destroy. For example, the local backend does not support remote operations and state locking. State locking is a feature that ensures that no two users can make changes to the state file at the same time, which is crucial for preventing race conditions. Remote operations allow running Terraform commands on a remote server, which is supported by some backends like remote or consul, but not all.

None of the above methods prevent credentials from being stored in the state file. Terraform stores the provider configuration in the state file, which may include sensitive information such as credentials. This is a potential security risk and should be avoided if possible. To prevent credentials from being stored in the state file, you can use one of the following methods:

Use environment variables to pass credentials to the provider. This way, the credentials are not part of the provider configuration and are not stored in the state file. However, this method may not work for some providers that require credentials to be set in the provider block.

Use dynamic credentials to authenticate with your cloud provider. This way, Terraform Cloud or Enterprise will request temporary credentials from your cloud provider for each run and use them to provision your resources. The credentials are not stored in the state file and are revoked after the run is completed. This method is supported for AWS, Google Cloud Platform, Azure, and Vault. References = : [Sensitive Values in State] : Authenticate providers with dynamic credentials

The terraform state rm commandremovesa resource from Terraform’s state file butdoes not destroythe resource in the actual infrastructure. It only removes Terraform’s knowledge of the resource, meaning Terraform will no longer manage it.

If you run terraform state rm on a resource, Terraform will forget that the resource exists.

However, the resource will still exist in the cloud or infrastructure provider.

If you later run terraform apply, Terraform may try torecreatethe resource because it is no longer present in its state file.

Official Terraform Documentation Reference:

terraform state rm - HashiCorp Documentation

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

Rationale for Correct Answer (B):

IaC best practice is to manage infrastructure through version-controlled code. Changes should be reviewed and approved (via PRs), ensuring collaboration, traceability, and automation.

Analysis of Incorrect Options:

A, D, E: Making direct/manual changes bypasses IaC practices and causes drift.

C: Running code without PR review skips collaboration and approval.

Key Concept:

Infrastructure as Code emphasizes version control + peer review + automation.

You can install third party plugins using terraform init, as long as you specify the plugin directory in your configuration or as a command-line argument. You can also use the terraform providers mirror command to create a local mirror of providers from any source.