HashiCorp Terraform Associate (004) Question 203
Single answer8 HCP TerraformA platform team is migrating local Terraform workflows to HCP Terraform. They want every plan and apply to run remotely in HCP Terraform, use a shared and encrypted state backend, and allow developers to continue using the Terraform CLI from their laptops without manually pushing configuration through the UI. Which approach best meets these requirements with the least operational overhead?
- A
Configure each workspace to use the local backend and ask developers to upload state files to HCP Terraform after each apply.
- B
Add a cloud block to the Terraform configuration that targets the HCP Terraform organization and workspace, then run Terraform commands from the CLI using the remote workflow.
- C
Store the state in an external S3 bucket and use HCP Terraform only as a dashboard for viewing run history.
- D
Use Terraform Enterprise agents on every developer laptop so plans run locally but state is copied to HCP Terraform after completion.
Show answer and explanation
Correct answer: B
Explanation
The best answer is to use the CLI-driven remote workflow with HCP Terraform by defining a cloud block that points to the correct organization and workspace. In this model, users continue to work from the Terraform CLI, but plan and apply operations execute remotely in HCP Terraform. This provides centralized, encrypted state management and consistent execution without requiring manual uploads or a separate storage backend. This aligns with HashiCorp guidance for HCP Terraform remote operations and workspaces. Relevant documentation includes Terraform language configuration for the cloud block and HCP Terraform workflow documentation describing CLI-driven runs, remote execution, and managed state.
- A. Incorrect.
This is incorrect. A local backend keeps state on the user's machine unless separately moved, which does not provide the shared, managed remote execution model the scenario requires. Manually uploading state is error-prone and defeats the purpose of HCP Terraform's managed state and remote runs.
- B. Correct.
This is correct. Using the Terraform cloud block to connect the configuration to an HCP Terraform organization and workspace enables the CLI-driven remote workflow. Developers can still run Terraform commands locally, but HCP Terraform performs the remote plan and apply, manages encrypted state, and centralizes execution with minimal extra process overhead.
- C. Incorrect.
This is incorrect. HCP Terraform is more than a dashboard; it provides remote execution, workspace management, variables, policy integration, and managed state. Using S3 for state and HCP Terraform only for visibility does not satisfy the requirement that every plan and apply run remotely in HCP Terraform.
- D. Incorrect.
This is incorrect. HCP Terraform agents are used to enable HCP Terraform runs to access private network resources, not to turn each laptop into a local execution node. The scenario does not require private connectivity, and copying state after local execution would be a brittle workaround rather than a best-practice HCP Terraform workflow.