HashiCorp Terraform-Associate-004 Exam - Topic 8 Question 1 Discussion

Actual exam question for HashiCorp's Terraform-Associate-004 exam

Question #: 1
Topic #: 8

You are working on some new application features and you want to spin up a copy of your production deployment to perform some quick tests. In order to avoid having to configure a new state backend, what open source Terraform feature would allow you create multiple states but still be associated with your current code?

ATerraform data sources

BTerraform local values

CTerraform modules

DTerraform workspaces

ENone of the above

Show Suggested Answer

Suggested Answer: D

Terraform workspaces allow you to create multiple states but still be associated with your current code. Workspaces are like ''environments'' (e.g. staging, production) for the same configuration. You can use workspaces to spin up a copy of your production deployment for testing purposes without having to configure a new state backend. Terraform data sources, local values, and modules are not features that allow you to create multiple states.Reference=WorkspacesandHow to Use Terraform Workspaces

by Elenor at Jan 26, 2026, 01:26 PM

Limited Time Offer

25%

Off

Get Premium Terraform-Associate-004 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Abel

3 days ago

Wait, there's an option to do none of the above? What kind of sorcery is this?! Workspaces for the win!

upvoted 0 times

...

Brock

8 days ago

Workspaces all the way! I don't want to deal with configuring a new backend just for some quick tests.

upvoted 0 times

...

Elina

13 days ago

Data sources? Local values? Nah, this is clearly a workspace situation. Easy peasy.

upvoted 0 times

...

Chantell

19 days ago

I was thinking Terraform modules, but workspaces make more sense for this use case. Gotta love that flexibility!

upvoted 0 times

...

Arthur

24 days ago

Terraform workspaces seem like the way to go here. I can create multiple states without having to change my code.

upvoted 0 times

...

Shawnna

29 days ago

I could be wrong, but I thought data sources were for fetching information rather than managing state.

upvoted 0 times

...

Von

1 month ago

I practiced a similar question last week, and I think workspaces allow you to have multiple states without extra configuration.

upvoted 0 times

...

Lenna

2 months ago

I'm not entirely sure, but I feel like modules are more about organizing code rather than managing state.

upvoted 0 times

...

Lezlie

2 months ago

I think this question is about managing different environments in Terraform. I remember something about workspaces being useful for that.

upvoted 0 times

...

Krissy

2 months ago

I feel pretty confident that Terraform workspaces is the right answer here. That's the feature I've used in the past to manage multiple environments without having to set up a new backend each time.

upvoted 0 times

...

Edison

2 months ago

Workspaces sound like they could work, but I'm a little worried about the potential complexity. I might want to look into the other options as well, just to make sure I'm not missing something simpler.

upvoted 0 times

...

Wai

3 months ago

Okay, let me see. I'm pretty sure data sources and local values wouldn't be the right solution for this. And modules are more for organizing code, not managing state. So I'm leaning towards Terraform workspaces as the best option.

upvoted 0 times

...

Christiane

3 months ago

Hmm, I'm not totally sure about this one. I know Terraform has some features for managing multiple states, but I'm not familiar with the specifics. I'll have to think this through carefully.

upvoted 0 times

...

Tommy

3 months ago

I think Terraform workspaces might be the way to go here. That would let me create multiple states without having to set up a whole new backend configuration.

upvoted 0 times

...