HashiCorp Terraform Associate (004) Question 216
Single answer8c Describe how to organize and use HCP Terraform workspaces and projectsA platform team is onboarding HCP Terraform for three application teams: Payments, Analytics, and Search. Each team manages multiple environments (dev, staging, prod) and needs its own set of Terraform workspaces. Leadership also wants a way to group related workspaces for visibility and governance without changing how Terraform state is isolated per environment. Which approach best meets these requirements?
- A
Create one HCP Terraform project per application team, and place separate workspaces for each environment inside the appropriate project.
- B
Create one HCP Terraform workspace per application team, and use Terraform workspaces inside the CLI to separate dev, staging, and prod states.
- C
Create one HCP Terraform organization for each application team, because projects cannot contain multiple workspaces.
- D
Create a single HCP Terraform project for all teams, and use variable sets alone to represent Payments, Analytics, and Search environments.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use HCP Terraform projects to group related workspaces and use separate HCP Terraform workspaces for each environment. Projects provide organizational structure inside an organization, while workspaces remain the unit for Terraform runs, state management, variables, and many access-control patterns. A common real-world design is one project per team or application area, with multiple workspaces under each project for dev, staging, and prod. This aligns with HashiCorp guidance that projects are for organizing workspaces and that separate workspaces are commonly used to isolate environments. A frequent exam trap is confusing Terraform CLI workspaces with HCP Terraform workspaces; in HCP Terraform, environment isolation is generally handled with distinct HCP Terraform workspaces rather than relying on CLI workspace switching.
- A. Correct.
Correct. In HCP Terraform, projects are used to organize related workspaces within an organization. This is a good fit for grouping resources by team or application domain, such as Payments, Analytics, and Search. Separate HCP Terraform workspaces should still be used for each environment so that runs, state, variables, and permissions can remain isolated at the workspace level. This matches the requirement to group related workspaces for visibility and governance without changing state isolation.
- B. Incorrect.
Incorrect. This mixes up HCP Terraform workspaces with Terraform CLI workspaces. In HCP Terraform, the common best practice is to use separate HCP Terraform workspaces for distinct environments like dev, staging, and prod. Terraform CLI workspaces are not the primary mechanism for isolating environments in HCP Terraform-backed operational workflows, and using a single HCP Terraform workspace for all environments would reduce separation of runs, variables, and permissions.
- C. Incorrect.
Incorrect. Organizations are top-level administrative boundaries in HCP Terraform and are typically used for broader separation, not for each internal app team by default. Projects absolutely can contain multiple workspaces, so this statement is factually wrong. Creating separate organizations for each team would add unnecessary administrative overhead and is not required to achieve the requested grouping.
- D. Incorrect.
Incorrect. A single project for all teams may be possible, but it does not best satisfy the requirement to group related workspaces by application team for visibility and governance. Variable sets help share common variables across workspaces, but they do not replace projects as an organizational construct and do not represent environments or application groupings on their own.