[Q119-Q143] HashiCorp Terraform-Associate-003 Practice Verified Answers – Pass Your Exams For Sure! [2025]

admin -

September 13, 2025

Rate this post

HashiCorp Terraform-Associate-003 Practice Verified Answers – Pass Your Exams For Sure! [2025]

Valid Way To Pass Terraform Associate’s Terraform-Associate-003 Exam

HashiCorp Terraform-Associate-003 Exam Syllabus Topics:

Topic	Details
Topic 1	Configure and use Terraform providers: In this section, topics covered include understanding Terraform’s plugin-based architecture and configuring providers. It also covers aliasing, sourcing, and versioning functions.
Topic 2	Develop and troubleshoot dynamic configuration: This section deals with topics such as using language features to validate configuration query providers using data sources, computing and interpolating data using HCL functions, and using meta-arguments in configuration.
Topic 3	Manage resource lifecycle: The section covers topics such as Initializing a configuration using terraform init and its options and generating an execution plan using terraform plan and its options. It also covers the configuration changes using Terraform Apply and its options.

QUESTION 119
Which of the following does terraform apply change after you approve the execution plan? (Choose two.)

Cloud infrastructure Most Voted

The .terraform directory

The execution plan

State file

Terraform code

The terraform apply command changes both the cloud infrastructure and the state file after you approve the execution plan. The command creates, updates, or destroys the infrastructure resources to match the configuration. It also updates the state file to reflect the new state of the infrastructure. The .terraform directory, the execution plan, and the Terraform code are not changed by the terraform apply command.
References = Command: apply and Purpose of Terraform State

QUESTION 120
What is the name of the default file where Terraform stores the state?
Type your answer in the field provided. The text field is not case-sensitive and all variations of the correct answer are accepted.

Terraformtfstate
Explanation:
The name of the default file where Terraform stores the state is terraform.tfstate. This file contains a JSON representation of the current state of the infrastructure managed by Terraform. Terraform uses this file to track the metadata and attributes of the resources, and to plan and apply changes. By default, Terraform stores the state file locally in the same directory as the configuration files, but it can also be configured to store the state remotely in a backend. Reference = [Terraform State], [State File Format]

QUESTION 121
What value does the Terraform Cloud private registry provide over the public Terraform Module Registry?

The ability to share modules publicly with any user of Terraform

The ability to restrict modules to members of Terraform Cloud or Enterprise organizations

The ability to tag modules by version or release

The ability to share modules with public Terraform users and members of Terraform Cloud Organizations

The Terraform Cloud private registry provides the ability to restrict modules to members of Terraform Cloud or Enterprise organizations. This allows you to share modules within your organization without exposing them to the public. The private registry also supports importing modules from your private VCS repositories.
The public Terraform Module Registry, on the other hand, publishes modules from public Git repositories and makes them available to any user of Terraform. References = : Private Registry – Terraform Cloud : Terraform Registry – Provider Documentation

QUESTION 122
Which of the following is not a key principle of infrastructure as code?

Self-describing infrastructure

Idempotence

Versioned infrastructure

Golden images

Explanation
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]

QUESTION 123
All modules published on the official Terraform Module Registry have been verified by HasihCorp.

True

False

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.
References:
Terraform Module Registry documentation: Terraform Registry

QUESTION 124
You just upgraded the version of a provider in an existing Terraform project. What do you need to do to install the new provider?

Run terraform refresh.

Run terraform init -upgrade.

Run terraform apply -upgrade.

Upgrade your version of Terraform.

Comprehensive and Detailed in-Depth Explanation: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

QUESTION 125
How could you reference an attribute from the vsphere_datacenter data source for use with the datacenter_id argument within the vsphere_folder resource in the following configuration?

Data.vsphere_datacenter.DC.id

Vsphere_datacenter.dc.id

Data,dc,id

Data.vsphere_datacenter,dc

The correct way to reference an attribute from the vsphere_datacenter data source for use with the datacenter_id argument within the vsphere_folder resource in the following configuration is data.vsphere_datacenter.dc.id. This follows the syntax for accessing data source attributes, which is data.TYPE.NAME.ATTRIBUTE. In this case, the data source type is vsphere_datacenter, the data source name is dc, and the attribute we want to access is id. The other options are incorrect because they either use the wrong syntax, the wrong punctuation, or the wrong case.
References = [Data Source: vsphere_datacenter], [Data Source: vsphere_folder], [Expressions: Data Source References]

QUESTION 126
Which configuration consistency errors does terraform validate report?

Terraform module isn’t the latest version

Differences between local and remote state

Declaring a resource identifier more than once

A mix of spaces and tabs in configuration files

Explanation
Terraform validate reports configuration consistency errors, such as declaring a resource identifier more than once. This means that the same resource type and name combination is used for multiple resource blocks, which is not allowed in Terraform. For example, resource “aws_instance” “example” {…} cannot be used more than once in the same configuration. Terraform validate does not report errors related to module versions, state differences, or formatting issues, as these are not relevant for checking the configuration syntax and structure. References = [Validate Configuration], [Resource Syntax]

QUESTION 127
Running terraform fmt without any flags in a directory with Terraform configuration files check the formatting of those files without changing their contents.

True

False

Running terraform fmt without any flags in a directory with Terraform configuration files will not check the formatting of those files without changing their contents, but will actually rewrite them to a canonical format and style. If you want to check the formatting without making changes, you need to use the -check flag.

QUESTION 128
Which provider authentication method prevents credentials from being stored in the state file?

Using environment variables

Specifying the login credentials in the provider block

Setting credentials as Terraform variables

None of the above

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. Reference = : [Sensitive Values in State] : Authenticate providers with dynamic credentials

QUESTION 129
How can terraform plan aid in the development process?

Initializes your working directory containing your Terraform configuration files

Validates your expectations against the execution plan without permanently modifying state

Formats your Terraform configuration files

Reconciles Terraform’s state against deployed resources and permanently modifies state using the current status of deployed resources

The terraform plan command is used to create an execution plan. It allows you to see what actions Terraform will take to reach the desired state defined in your configuration files. It evaluates the current state and configuration, showing a detailed outline of the resources that will be created, updated, or destroyed. This is a critical step in the development process as it helps you verify that the changes you are about to apply will perform as expected, without actually modifying any state or infrastructure.
Reference:
Terraform documentation on terraform plan: Terraform Plan

QUESTION 130
Which of the following statements about Terraform modules is not true?

Modules can call other modules

A module is a container for one or more resources

Modules must be publicly accessible

You can call the same module multiple times

Explanation
This is not true, as modules can be either public or private, depending on your needs and preferences. You can use the Terraform Registry to publish and consume public modules, or use Terraform Cloud or Terraform Enterprise to host and manage private modules.

QUESTION 131
What command can you run to generateDOT (Graphviz)formatted data to visualize Terraform dependencies?

terraform refresh

terraform graph

terraform output

terraform show

Comprehensive and Detailed in-Depth Explanation:
* terraform graphgeneratesGraphviz DOT formatoutput, which allows visualization ofresource dependenciesin Terraform.
* A (terraform refresh)- Incorrect, as it only updates the state file.
* C (terraform output)- Incorrect, as it only displays Terraform output values.
* D (terraform show)- Incorrect, as it only displays the Terraform state.
Official Terraform Documentation Reference:terraform graph – HashiCorp Documentation

QUESTION 132
You can develop a custom provider to manage its resources using Terraform.

True

False

You can develop a custom provider to manage its resources using Terraform, as Terraform is an extensible tool that allows you to write your own plugins in Go language. You can also publish your custom provider to the Terraform Registry or use it privately.

QUESTION 133
terraform validate confirms thesyntaxof Terraform files.

True

False

* terraform validatechecks for syntax errors and internal consistencyin the configuration files.
* However, itdoes notcheck if resource configurations are valid with the provider.
Official Terraform Documentation Reference:
terraform validate – HashiCorp Documentation

QUESTION 134
Which of the following should you put into the required_providers block?

version >= 3.1

version = “>= 3.1”

version ~> 3.1

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 the configuration can work with any provider version that is 3.1 or higher. References = [Provider Requirements] and [Version Constraints]

QUESTION 135
Before you can use a new backend or HCP Terraform/Terraform Cloud integration, you must first execute terraform init.

True

False

Comprehensive and Detailed in-Depth Explanation:The terraform init command is required before using a new backend or integrating with HCP Terraform/Terraform Cloud.
* terraform init initializes the working directory and sets up the backend, downloading necessary provider plugins and modules.
* If the backend configuration changes, Terraform willrequirere-initialization to apply those changes.
* Without running terraform init, Terraform willfailto use a new backend or remote Terraform Cloud workspace.
Official Terraform Documentation Reference:terraform init – HashiCorp Documentation

QUESTION 136
Which of the following should you put into the required_providers block?

version >= 3.1

version = “>= 3.1”

version ~> 3.1

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 the configuration can work with any provider version that is 3.1 or higher.
References = [Provider Requirements] and [Version Constraints]

QUESTION 137
Which configuration consistency errors does terraform validate report?

Terraform module isn’t the latest version

Differences between local and remote state

Declaring a resource identifier more than once

A mix of spaces and tabs in configuration files

Terraform validate reports configuration consistency errors, such as declaring a resource identifier more than once. This means that the same resource type and name combination is used for multiple resource blocks, which is not allowed in Terraform. For example, resource “aws_instance” “example” {…} cannot be used more than once in the same configuration. Terraform validate does not report errors related to module versions, state differences, or formatting issues, as these are not relevant for checking the configuration syntax and structure. Reference = [Validate Configuration], [Resource Syntax]

QUESTION 138
Which of these is true about Terraform’s plugin-based architecture?

Terraform can only source providers from the internet

Every provider in a configuration has its own state file for its resources

You can create a provider for your API if none exists

All providers are part of the Terraform core binary

Terraform is built on a plugin-based architecture, enabling developers to extend Terraform by writing new plugins or compiling modified versions of existing plugins1. Terraform plugins are executable binaries written in Go that expose an implementation for a specific service, such as a cloud resource, SaaS platform, or API2. If there is no existing provider for your API, you can create one using the Terraform Plugin SDK3 or the Terraform Plugin Framework4.
References =
* 1: Plugin Development – How Terraform Works With Plugins | Terraform | HashiCorp Developer
* 2: Lab: Terraform Plug-in Based Architecture – GitHub
* 3: Terraform Plugin SDK – Terraform by HashiCorp
* 4: HashiCorp Terraform Plugin Framework Now Generally Available

QUESTION 139
You want to define a single input variable to capture configuration values for a server. The values must represent memory as a number, and the server name as a string.
Which variable type could you use for this input?

List

Object

Map

Terraform does not support complex input variables of different types

This is the variable type that you could use for this input, as it can store multiple attributes of different types within a single value. The other options are either invalid or incorrect for this use case.

QUESTION 140
Which Terraform command checks that your configuration syntax is correct?

terraform validate

terraform init

terraform show

terraform fmt

The terraform validate command is used to check that your Terraform configuration files are syntactically valid and internally consistent. It is a useful command for ensuring your Terraform code is error-free before applying any changes to your infrastructure.

QUESTION 141
Only the user that generated a plan may apply it.

True

False

Explanation
Any user with permission to apply a plan can apply it, not only the user that generated it. This allows for collaboration and delegation of tasks among team members.

QUESTION 142
All modules published on the official Terraform Module Registry have been verified by HasihCorp.

True

False

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.
References:
* Terraform Module Registry documentation: Terraform Registry

QUESTION 143
Which of the following is true about terraform apply?(Pick 2 correct responses)

You must pass the output of a terraform plan command to it.

By default, it does not refresh your state file to reflect the current infrastructure configuration.

Depending on provider specification, Terraform may need to destroy and recreate your infrastructure resources.

You cannot target specific resources for the operation.

It only operates on infrastructure defined in the current working directory or workspace.

Comprehensive and Detailed in-Depth Explanation:
* C (#Correct)- If changes require aresource replacement(e.g., changing an immutable attribute like instance type), Terraform willdestroy and recreate the resource.
* E (#Correct)- Terraform only appliesthe configuration in the current directory or workspace.

Loading …