A developer wants to run `terraform plan` locally against a workspace in HCP Terraform. They have the Terraform CLI installed and are authenticated. What must they do to ensure the plan runs remotely and uses the workspace's remote state?

Create a `terraform.tfstate` file in the local directory.

Set the environment variable `TF_WORKSPACE` to the workspace name.

Run `terraform init` in a directory that contains a `backend "remote"` block configured with the workspace name.

Run `terraform workspace select` to choose the remote workspace.

Which step is required when configuring a VCS integration in HCP Terraform?

Uploading the Terraform configuration files directly to HCP Terraform via the UI.

Providing the repository URL and authentication credentials for the VCS provider.

Creating a new repository in the VCS provider from within HCP Terraform.

Setting up a VPN connection between HCP Terraform and the VCS provider's data center.

Where is Terraform state stored when using HCP Terraform?

In the local directory of the machine running Terraform.

In a remote backend managed by HCP Terraform.

In the version control repository alongside the configuration files.

In a database managed by the cloud provider.

What is a benefit of integrating HCP Terraform with a CI/CD pipeline?

It eliminates the need for any testing of infrastructure changes.

It requires all infrastructure changes to be made manually by an operator.

It allows infrastructure changes to be applied without any review or approval.

Infrastructure changes can be tested and deployed automatically alongside application code.

A company uses HCP Terraform with a CI/CD pipeline that runs `terraform plan` in parallel for multiple feature branches. They occasionally see 'Error: Error acquiring the state lock' in the pipeline logs. They want to avoid these errors without sacrificing parallel plans. What is the best approach?

Use separate workspaces for each feature branch, each with its own state.

Set the workspace's execution mode to 'local' to bypass remote locking.

Disable the state lock in the backend configuration.

Use a single workspace and rely on HCP Terraform's queue to serialize runs.

HashiCorp Certified:Terraform Associate

Domain 8Objective 4

8d Configure and Use HCP Terraform Integration TERRAFORM-ASSOCIATE-004 Practice Questions (Page 7)

Part of the HCP Terraform domain, which makes up ~13% of our current practice bank. HashiCorp does not publish an official question count, but from its 60-minute exam (~25–40 total, ~3–5 in this domain), expect 1–1 from this objective — we provide 35 practice questions to prepare you well beyond it. (estimate)

35questions here

7free pages

8concepts

Questions 31–35

31application · medium
A developer wants to run `terraform plan` locally against a workspace in HCP Terraform. They have the Terraform CLI installed and are authenticated. What must they do to ensure the plan runs remotely and uses the workspace's remote state?
Select an answer first
32foundation · easy
Which step is required when configuring a VCS integration in HCP Terraform?
Select an answer first
33foundation · easy
Where is Terraform state stored when using HCP Terraform?
Select an answer first
34foundation · easy
What is a benefit of integrating HCP Terraform with a CI/CD pipeline?
Select an answer first
35expert · hard
A company uses HCP Terraform with a CI/CD pipeline that runs `terraform plan` in parallel for multiple feature branches. They occasionally see 'Error: Error acquiring the state lock' in the pipeline logs. They want to avoid these errors without sacrificing parallel plans. What is the best approach?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to TERRAFORM-ASSOCIATE-004

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “TERRAFORM-ASSOCIATE-004” is a trademark of its owner, used for identification only.