HashiCorp Terraform-Associate-003 Test Engine Practice Test Questions, Exam Dumps [Q106-Q120]

Rate this post

HashiCorp Terraform-Associate-003 Test Engine Practice Test Questions, Exam Dumps

100% Free Terraform-Associate-003 Daily Practice Exam With 195 Questions

Q106. As a member of an operations team that uses infrastructure as code (lac) practices, you are tasked with making a change to an infrastructure stack running in a public cloud. Which pattern would follow laC best practices for making a change?

Make the change via the public cloud API endpoint

Clone the repository containing your infrastructure code and then run the code

Use the public cloud console to make the change after a database record has been approved

Make the change programmatically via the public cloud CLI

Submit a pull request and wait for an approved merge of the proposed changes

You do not need to use different Terraform commands depending on the cloud provider you use. Terraform commands are consistent across different providers, as they operate on the Terraform configuration files and state files, not on the provider APIs directly.

Q107. Which method for sharing Terraform modules fulfills the following criteria:
Keeps the module configurations confidential within your organization.
Supports Terraform’s semantic version constraints.
Provides a browsable directory of your modules.

A Git repository containing your modules.

Public Terraform module registry.

A subfolder within your workspace.

HCP Terraform/Terraform Cloud private registry.

Confidentiality: Using HCP Terraform/Terraform Cloud’s private registry keeps the module configurations within your organization, ensuring privacy and access control.
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 for private registry support in Terraform, meeting all listed requirements for secure, version-controlled, and searchable module storage.

Q108. You want to define multiple data disks as nested blocks inside the resource block for a virtual machine. What Terraform feature would help you define the blocks using the values in a variable?

Local values

Count arguments

Collection functions

Dynamic blocks

Dynamic blocks in Terraform allow you to define multiple nested blocks within a resource based on the values of a variable. This feature is particularly useful for scenarios where the number of nested blocks is not fixed and can change based on variable input.

Q109. Terraform can only manage resource dependencies if you set them explicitly with the depends_on argument.

True

False

Explanation
Terraform can manage resource dependencies implicitly or explicitly. Implicit dependencies are created when a resource references another resource or data source in its arguments. Terraform can infer the dependency from the reference and create or destroy the resources in the correct order. Explicit dependencies are created when you use the depends_on argument to specify that a resource depends on another resource or module.
This is useful when Terraform cannot infer the dependency from the configuration or when you need to create a dependency for some reason outside of Terraform’s scope. References = : Create resource dependencies : Terraform Resource Dependencies Explained

Q110. You used Terraform to create an ephemeral development environment in the cloud and are now ready to destroy all the infrastructure described by your Terraform configuration. To be safe, you would like to first see all the infrastructure that Terraform will delete.
Which command should you use to show all the resources that will be deleted? (Pick the 2 correct responses)

Run terraform destroy. This will output all the resources that will be deleted before prompting for approval.

Run terraform show -destroy.

Run terraform state rm *.

Running terraform destroy will show all resources that will be deleted before prompting for approval. You can also run terraform plan -destroy to simulate the destruction without actually applying it, which is useful for reviewing the planned changes.
References:
Terraform Destroy

Q111. What does terraform import do?

Imports existing resources into the state file

Imports all infrastructure from a given cloud provider

Imports a new Terraform module

Imports clean copies of tainted resources

None of the above

The terraform import command is used to import existing infrastructure into your Terraform state. This command takes the existing resource and associates it with a resource defined in your Terraform configuration, updating the state file accordingly. It does not generate configuration for the resource, only the state.

Q112. What does state looking accomplish?

Prevent accidental Prevent accident deletion of the state file

Blocks Terraform commands from modifying, the state file

Copies the state file from memory to disk

Encrypts any credentials stored within the state file

Explanation
This is what state locking accomplishes, by preventing other users from modifying the state file while a Terraform operation is in progress. This prevents conflicts and data loss.

Q113. You are writing a child Terraform module that provisions an AWS instance. You want to reference the IP address returned by the child module in the root configuration. You name the instance resource “main’.
Which of these is the correct way to define the output value?
A)
B)
C)
D)

Option A

Option B

Option C

Option D

Q114. How can a ticket-based system slow down infrastructure provisioning and limit the ability to scale? Choose two correct answers.

End-users have to request infrastructure changes

Ticket based systems generate a full audit trail of the request and fulfillment process

Users can access catalog of approved resources from drop down list in a request form

The more resources your organization needs, the more tickets your infrastructure team has to process

Explanation
These are some of the ways that a ticket-based system can slow down infrastructure provisioning and limit the ability to scale, as they introduce delays, bottlenecks, and manual interventions in the process of creating and modifying infrastructure.

Q115. Module variable assignments are inherited from the parent module and you do not need to explicitly set them.

True

False

Explanation
Module variable assignments are not inherited from the parent module and you need to explicitly set them using the source argument. This allows you to customize the behavior of each module instance.

Q116. How can you trigger a run in a Terraform Cloud workspace that is connected to a Version Control System (VCS) repository?

Only Terraform Cloud organization owners can set workspace variables on VCS connected workspaces

Commit a change to the VCS working directory and branch that the Terraform Cloud workspace is connected to

Only Terraform Cloud organization owners can approve plans in VCS connected workspaces

Only members of a VCS organization can open a pull request against repositories that are connected to Terraform Cloud workspaces

Explanation
This will trigger a run in the Terraform Cloud workspace, which will perform a plan and apply operation on the infrastructure defined by the Terraform configuration files in the VCS repository.

Q117. When should you use the force-unlock command?

You have a high priority change

Automatic unlocking failed

apply failed due to a state lock

You see a status message that you cannot acquire the lock

You should use the force-unlock command when automatic unlocking failed. Terraform will lock your state for all operations that could write state, such as plan, apply, or destroy. This prevents others from acquiring the lock and potentially corrupting your state. State locking happens automatically on all operations that could write state and you won’t see any message that it is happening. If state locking fails, Terraform will not continue. You can disable state locking for most commands with the -lock flag but it is not recommended. If acquiring the lock is taking longer than expected, Terraform will output a status message. If Terraform doesn’t output a message, state locking is still occurring if your backend supports it. Terraform has a force-unlock command to manually unlock the state if unlocking failed. Be very careful with this command. If you unlock the state when someone else is holding the lock it could cause multiple writers. Force unlock should only be used to unlock your own lock in the situation where automatic unlocking failed. To protect you, the force-unlock command requires a unique lock ID. Terraform will output this lock ID if unlocking fails. This lock ID acts as a nonce, ensuring that locks and unlocks target the correct lock. The other situations are not valid reasons to use the force-unlock command. You should not use the force-unlock command if you have a high priority change, if apply failed due to a state lock, or if you see a status message that you cannot acquire the lock. These situations indicate that someone else is holding the lock and you should wait for them to finish their operation or contact them to resolve the issue. Using the force-unlock command in these cases could result in data loss or inconsistency. Reference = [State Locking], [Command: force-unlock]

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

Q119. Which of the following module source paths does not specify a remote module?

Source = “module/consul”

Source = ”githhub.comicrop/example”

Source =”[email protected]:hasicrop/example.git”

Source = ”hasicrop/consul/aws”

The module source path that does not specify a remote module is source = “module/consul”. This specifies a local module, which is a module that is stored in a subdirectory of the current working directory. The other options are all examples of remote modules, which are modules that are stored outside of the current working directory and can be accessed by various protocols, such as Git, HTTP, or the Terraform Registry. Remote modules are useful for sharing and reusing code across different configurations and environments.
References = [Module Sources], [Local Paths], [Terraform Registry], [Generic Git Repository], [GitHub]

Q120. You should run terraform fnt to rewrite all Terraform configurations within the current working directory to conform to Terraform-style conventions.

True

False

Explanation
You should run terraform fmt to rewrite all Terraform configurations within the current working directory to conform to Terraform-style conventions. This command applies a subset of the Terraform language style conventions, along with other minor adjustments for readability. It is recommended to use this command to ensure consistency of style across different Terraform codebases. The command is optional, opinionated, and has no customization options, but it can help you and your team understand the code more quickly and easily. References = : Command: fmt : Using Terraform fmt Command to Format Your Terraform Code

Loading …

HashiCorp Terraform-Associate-003 Exam Syllabus Topics:

Topic	Details
Topic 1	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.
Topic 2	Collaborate on infrastructure as code using HCP Terraform: In this section, the topics covered include analyzing the HCP Terraform run workflow, the role of HCP Terraform workspaces and their configuration options, and the management of provider credentials in HCP Terraform.
Topic 3	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 4	Develop collaborative Terraform workflows: In this section, candidates are tested for their skills related to managing the Terraform binary, providers, and modules using version constraints and setting up remote states. It also covers the utilization of the Terraform workflow in automation.
Topic 5	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.